SOLIDWORKS PDM to SAP S/4HANA Cloud Integration

Send

Send to SAP S/4HANA, all levels

Right-click the top assembly in the vault view and choose ERP Integrator, Send to SAP S/4HANA all levels. The add-in reads the file cards and the complete bill of materials, applies your rules and brings SAP up to date. This assembly had been sent before, so the dialog shows which products were updated (bore and crank had changed in the vault) and which were already current.

• Columns for Create/Update BOM Header, Create/Update Item and Create BOM lines, one row per item.
• Unchanged products and BOMs read Update skipped instead of being written again.

Result in SAP

Material BOM under a change number

In SAP the products carry their descriptions from the vault. The material BOM for ENGINE-ASSY lists the eight components as stock items, with component quantity and unit EA, item numbers 0001 to 0008, all valid from the send date under one engineering change number: the same structure as the assembly in the vault.

Check in PDM

The SAP product on the Item Details tab

Select a file and the Item Details tab reads the SAP product live: product type, base unit, industry sector, description, division, product group and plant. You find out whether an item already exists in SAP before anyone creates a second one.

• Add property and Delete Row choose the attributes shown; Save Settings keeps them.
• A configuration picker is there for files with more than one configuration.

Compare

Vault BOM next to the SAP material BOM

The ERP Data tab puts the vault BOM next to the SAP product and material BOM data, BOM number, item number and change number included, with a green check on every line that agrees.

• Changes made in the vault since the last transfer stand out before the next send.
• With BOM versioning in SAP, the vault BOM can be compared with an earlier ERP BOM as well.

Rules and AI

Trading goods, finished and semi-finished by rule

The rule in the video: parts with screw, ring or pin in the description are bought in, so they become trading goods (HAWA); every assembly is a finished product (FERT); everything else is semi-finished (HALB). The assistant first confirmed that ProductType is a writable field on the SAP product and that all three values fit, then asked for approval before it replaced the item mappings, wrote the rule and compiled it.

Preview

Check the product types before the send

Preview Data shows each product as it would go to SAP: ENGINE-ASSY and PISTON-ASSY as FERT, the cap screw as HAWA, the rest as HALB. Conrod Bearing stays HALB because only whole words count, so the ring inside bearing does not match.

Nothing has been sent at this point; SAP changes only when you save the rule and send.

Questions and search

Where-used and existence in SAP

Ask "Which files in this vault use conrod.sldprt, and which already exist in SAP S/4HANA?" The assistant ran a where-used search in the vault, queried SAP and answered in one table: the assembly and its drawing exist in SAP, the five other drawings do not. It also noted that conrod.sldprt itself is still Under Editing, version 2, so it is not in a released state.

• Asked whether the component quantities match SAP, it compared the vault BOM with the live material BOM: all eight components match.
• The chat runs on the AI you pick: an API key for Claude, OpenAI, Azure OpenAI or a compatible endpoint, a ChatGPT sign-in, a coding agent such as Claude or Gemini, or your own assistant over the MCP connector.