Autodesk Vault to SAP Business One Integration

Send

Send to SAP Business One, all levels

Select the assembly in Vault, right-click and choose AV2ERP > Send to SAP Business One all levels. AV2ERP reads the item and its complete bill of materials from Vault, applies your rules and creates everything in SAP Business One: the items, the bills of materials and every line on them.

• One row per Vault item, with what happened to the item and to its bill of materials lines.
• Anything SAP Business One rejects is listed with its message on the Failed action list tab.
• Send by right-click, or from a workflow state change in Vault.

Result in SAP Business One

Item master data and the bill of materials

The items are in the SAP Business One item master data with their titles from Vault. The bill of materials of the engine assembly lists all eight components with their quantities: the same structure as in Vault.

• The Vault number becomes the item number.
• The sub-assembly gets its own bill of materials in the same send.

Check in Vault

Live SAP Business One data inside Vault

Nobody has to leave Vault to check. The ERP Item Details tab shows the item live from SAP Business One, and the ERP Data tab puts Vault and SAP Business One side by side, with a green check on every line that agrees.

In the demo the cap screw's quantity has since changed in Vault to three, while SAP Business One still has two, so exactly that cell is red, and its tooltip shows both values.

As of a date

Compare the bill of materials as of a date

Bills of materials change over time, so the ERP Data tab can compare them as of a date. SAP Business One keeps one current bill of materials, so Vault's structure on the date you pick is compared with today's rows in SAP Business One; the tab says so next to the date.

On 30 September, before the quantity changed, everything matched. On today's date the changed line stands out in red again.

Set up once

Field mapping and fixed values

What goes where is set up once: which Vault property fills which SAP Business One field, and fixed values such as the item group. The connection to the Service Layer is stored with the settings.

• Change a mapping in the settings; no code and no new release.
• When a fixed value is not enough, a macro decides per item, as in the next step.

Rules and AI

Your company rules in plain words

Describe a rule in plain words: screws, rings and pins are bought, everything else is made. The AI looks up what it needs in Vault and SAP Business One, asks for your approval before it changes the field mapping, writes the rule into the macro, checks that it compiles and previews the result on the real assembly.

• Preview: the cap screw is set to Buy, every other item to Make.
• Nothing has been saved or sent at that point; saving and sending stay your decision.

Questions and search

Ask Vault and SAP Business One in plain words

Asked whether the component quantities match SAP Business One, the assistant reads the bill of materials in Vault and the live rows in SAP Business One and answers: seven components match, only the cap screw differs, three in Vault and two in SAP Business One.

It searches for you too: the Vault items with Engine in the title and whether they exist in SAP Business One, in one table, or whether any Vault jobs failed in the last seven days.

The assistant 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 through the MCP connector. Whatever it proposes, nothing is changed until you approve it.