Our Adeptia Solution makes it easy to integrate EDI messages with SAP IDoc and BAPI. There are just 2 steps needed to integrate an EDI to SAP. Below is a step by step depiction of SAP EDI integration. In this SAP EDI integration step by step guide, EDI 856 (a shipment Notice/manifest) is mapped to the SAP IDoc DELVRY03 document.

First, 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. With Adeptia’s SAP Adapter, you can search for any IDoc automatically, and select the correct one needed for mapping. Apply the data mapping rules to convert the EDI to IDoc. You’ll only need to do this once since the mapping can be used in any future 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 are some relevant screenshots:

The second (and 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 SAP EDI transaction process overview process where an incoming EDI file is being sent to SAP/XI server. The Mapping service created in step 1 is embedded as a second activity in the flow. The process picks up new EDI messages, converts them to IDoc, and delivers them to the SAP server.

You can check the status of each transaction using the run-time transactional logs.

EDI integration with SAP Integration is included in our Adeptia Solution. You can easily drive SAP EDI transactions using Adeptia Connect. You can explore the benefits of our solution by taking a free demo of our software. Or, you can just keep banging your head against the wall trying to get your EDI integration to SAP up and running by constructing a huge kluge…the choice is yours!