Adeptia Solution makes it easy for developers to integrate EDI messages with SAP IDoc and BAPI.
There are 2 simple steps to integrate an EDI to SAP, in this example we will summarize the steps on how to map EDI 856 (Shipment Notice/Manifest) to SAP IDoc DELVRY03 document.
Create a Mapping service between the inbound EDI to SAP IDoc. Adeptia’s graphical data mapper shows the specific EDI message schema and the IDoc schema. Adeptia’s SAP Adapter allows user to search for any IDoc automatically and select the particular IDoc that is needed for the mapping. Developer would then apply the mapping rules to convert the EDI to IDoc. This is a one-time effort since the mapping can be used in any orchestration where EDI 856 needs to be converted into SAP DELVRY03.
At run-time when the orchestration executes this mapping service, the EDI data will be converted to IDoc.
Here's an example of the EDI to IDoc mapping.
Final step is to design an orchestration that allows inbound EDI files to be delivered to SAP using the Adeptia SAP Adapter. Here’s a sample process where an incoming EDI file is being sent to SAP PI/XI server. The Mapping service created in step 1 is embedded as a second activity in the flow. Process picks up new EDI message and converts it to IDoc and delivers it to the SAP server.
Run-time transactional logs are available to check the status of each transaction.
Adeptia EDI and SAP Integration services are included in the Adeptia Solution.