Autodesk Inventor to SAP S/4HANA Cloud Integration

Send

Bringing SAP up to date

Open the assembly and send it to SAP S/4HANA from the Inventor ribbon, all levels. INV2ERP reads the iProperties of the assembly and everything below it, applies the company rules, and brings the products, the material BOM and its BOM items up to date.

• The result dialog shows per item what happened to the BOM header, the product and the BOM items.
• In the demo two parts had new descriptions in Inventor. Those two, bore and crank, were Updated; everything else was Update skipped because SAP already had the same values.

Result in SAP

The material BOM for plant 4410

In Maintain Bill of Material the assembly has its material BOM for plant 4410 with every component as a stock item, with its quantity and unit. SAP has no BOM versions like Business Central or Dynamics 365; each BOM item carries the date it is valid from instead.

• The products carry their descriptions from Inventor, including the two that just changed.
• Sub-assemblies such as the piston assembly get a material BOM of their own.

Check in Inventor

Inventor next to SAP, line by line

Show ERP Item Details reads the product from SAP while the model is open: product type, base unit, industry sector, description, language, division, product group and plant. The ERP data pane lists the assembly tree with the Inventor values next to the SAP product and BOM values, and every line that agrees gets a green check.

• After the send, the cap screw's description was changed in Inventor. The cell turns red until the next send, so the difference is visible before a buyer orders from an old description.
• Source date and ERP date pick the day to compare against.

Rules and AI

Product type rule in plain words

The rule for this company: parts with screw, ring or pin in the description are bought in and become trading goods (HAWA), every assembly is a finished product (FERT), everything else is semi-finished (HALB). Typed into the AI Macro Chat as a sentence, the AI looks up the fields in Inventor and SAP, writes the rule into the macro, compiles it and runs a preview on the open assembly.

• The preview shows the cap screw as HAWA, both assemblies as FERT and the rest as HALB.
• Conrod Bearing stays HALB because the rule matches whole words only, and the AI says so in its answer.
• Nothing has been sent to SAP; the new rule waits for Save and the next send.

Questions

Checking quantities with a question

Ask whether the component quantities of the assembly match SAP, and the assistant reads the BOM in Inventor and the BOM items in SAP. Here it found BOM 00000349 for ENGINE_ASSEM in plant 4410 with the same eight lines and the same quantities, and listed them with a check per line.

Search

Looking up products in SAP

Asked which parts already exist in SAP and what product type they have today, the assistant queried the product service and answered in one table: all nine exist, all still ERSA (spare parts), the fixed value from the old settings. A send with the new rule would update them rather than create anything.

• The chat works with your own key for Claude, OpenAI, Azure OpenAI or a compatible model, with a ChatGPT sign-in, with a coding agent such as Claude or Gemini, or with your own assistant connected through the MCP connector.
• The AI proposes changes; the mapping, the macro and SAP stay as they are until you approve.