The user selects a standard or supplier part in PARTdataManager and wants to export it .

Via $CADENAS_SETUP/ erpcustom.cfg in the section [ADDTODB] determined, which scripts shall be called up one after another. In the case of a SAP integration you will find "X=...\erp\ erp_sap_mm.vbs". The script erp_sap_mm.vbs is loaded and the function 'execute' is called up. This effects the creation of the IO file and writes all data, which are available in PARTsolutions for the respective part (in the scheme above depicted as green text).

Afterwards the SAP interface 'sapcadenassrv.exe' is called up (also by erp_sap_mm.vbs). The path to that place is also defined under $CADENAS_SETUP/erpcustom.cfg; namely under section [VARS] in the key INTERFACEEXE=.... SAP specific settings are made in 'sapcadenassrv.ini', 'saplogon.ini' and 'saprfc.ini'. These are registration information, IP address SAP server, variable mapping, etc. The documentation on this is found in the .ini files.

The SAP mask (normally the transaction MM01) is started and the user can apply a new material master.

After saving of the new material master the SAP interface effects that the new information is written into the IO file (in the above scheme depicted in red). After this the SAP interface is finished.

The script erp_sap_mm.vbs gets the control over the computer operation again. The information in the IO file is read and inserted in the link database. Thereby a mapping is performed, which can be freely defined under $CADENAS_SETUP/erpcustom.cfg, section [MAPPING].