In this post, “SAP PO for Beginners Part – 12 – Interface Development – B2B EDI Inbound to XML Proxy to ECC,” we will discuss and convert EDI format inbound documents to XML and pass them to an ABAP proxy by developing an interface from scratch.
In short, below is the content we will be elaborate in this tutorial: Interface Development – B2B EDI Inbound to XML Proxy to ECC
- Overview
- Scenario
- Objects involved in Interface Development
- Build Enterprise Service Repository Objects
- Build Communication Channels
- Build Integrated Configuration (ICO)
- Testing the Interface
1. Overview:
Assume there is a business requirement where the vendor will place invoice records in SFTP in EDI format, which SAP PO needs to pick up and process. The EDI messages are then communicated to the EDI separator connector to split bulk EDI messages into single transaction sets, as one EDI document can contain multiple sales orders, invoices, delivery notifications, etc., which completes one ICO. Subsequently, it will be passed to another ICO of the sender EDI separator channel, which will convert individual EDI messages to XML. This process is detailed in SAP PO for Beginners Part – 12 – Interface Development – B2B EDI Inbound to XML Proxy to ECC.
2. Scenario:
3. Objects involved in Interface Development:
As said, there are 2 ICOs to be created. For first ICO, we will pick the document from SFTP, so the shipper correspondence channel is of connector type SFTP (not going to cover the SFTP channel config, as I take care of it in past areas) and the recipient correspondence channel will be of connector type EDI Separator.
For second ICO, the shipper correspondence channel would be of connector type EDI Separator and the collector correspondence channel will be of connector type Cleanser with message convention as XI 3.0.
In second ICO, we will import message planning, in light of the fact that through shipper EDI connector, the EDI record will be changed over completely to XML and passed to message planning for getting the ideal construction to pass the information to ECC through ABAP Intermediary.
We should make information objects for the inbound XML information. In this model we won’t make information type and message type, rather we are utilizing the Outer Definitions given by the merchant. Outside Definitions are like pre-characterized field structures which you can simply import and use it in Message planning.
4. Build ESR Objects:
Prior to continuing with the formation of Correspondence channels, we should begin with the result structure creation.
External Definitions:
Click on Make NEW – > Outside Definitions
Select the class as XSD from the dropdown and import the XSD document.
For getting the import XSD document, explore to the underneath way:
http://:/b2bic (For this to be accessible, B2B add on should be introduced by Premise group)
Select the choice, EDI Content Administrator and select the dropdown in the arrangement ANSI X12 and pick XSD Generator.
For producing XSD record, pick the suitable exchange set as 810 and adaptation to 5040 (for our situation). Once finished, click on START.
Framework will produce the xsd record, save it and import it in outer definition as displayed beneath.
External Definition:
Click on SAVE & ACTIVATE.
Service Interface:
Create two service interfaces.
The file is passed from SFTP to P – Outbound Service Interface – 1
PI to ECC – Inbound Service Interface – 2
Choose the Mode as ASYNCHRONOUS
Outbound Service Interface:
Inbound Service Interface:
Message Mapping:
Import a similar outside definition into source and target area, as we will be passing the information for all intents and purposes to ECC.
Operation Mapping:
Import both the outbound and inbound assistance interfaces. Once imported, click on READ Tasks button which would peruse the outside definitions put away in assistance interfaces.
When done, select the sort of planning and import the message planning made.
Click on SAVE & ACTIVATE.
ESR Items creation done. We should begin with the Joining Items advancement.
5. Build Communication Channels:
FIRST ICO:
Sender Communication Channel:
Open the Reconciliation Catalog – > Snap on Make New symbol and pick Correspondence Channel.
Give the channel a reasonable channel name and tap on Make. Pick Connector type as SFTP and pick Shipper Radio button.
Click on SAVE and Actuate.
Receiver Communication Channel:
Click and Make New – > Correspondence Channel – > Pick Collector radio button and connector type as EDI Separator with Message Convention as Electronic Report Exchange.
Note: For getting the EDI Separator connector which wouldn’t be in standard PO 7.5 establishment, B2B add on establishment should be finished.
- BASIS team installs B2B cockpit
- Make sure NWA-> Components Info, b2b components are installed
- Download and extract ZIP files of B2B Cockpit/toolkit/EDI mapping runtime
- Import toolkit/mapping kit extracted files in ID
- For installing EDI runtime content, there will be many .b2b seed file, import the required file. For e.g.: for EDI ANSI X12 format, required runtime is *X12.b2b file
- http://<host>:<port>/b2bic -> EDI content Manager. Select required format and choose to import in dropdown
- Verify imported components by selecting format -> Editor > Message Editor
- Verify in ID whether EDI adapter is visible
- If these B2B adapters are still not available, request BASIS team to register the adapters using JSPM
Click on SAVE & ACTIVATE.
SECOND ICO:
Sender Communication Channel:
Open the Combination Catalog – > Snap on Make New symbol and pick Correspondence Channel.
Give the channel a reasonable channel name and tap on Make. Pick Connector type as EDI Separator and pick Shipper Radio button.
Source EDI separator will change over individual EDI messages to XML. For changing over the EDI design payload to XML, add the underneath module in the source channel.
Under module tab,
localejbs/X12ConverterModule – Nearby Venture Bean – 1
This ought to be the first and afterward the SAP call connector ought to come. Request is significant.
Since it is a receipt record of EDI 810, we want to determine the exchange set identifier code as 810 and rest all as *.
Click on SAVE & ACTIVATE.
Receiver Communication Channel:
Open the Coordination Catalog – > Snap on Make New symbol and pick Correspondence Channel.
Give the channel a reasonable channel name and tap on Make. Pick Connector type as Cleanser with message convention as XI 3.0 and pick Collector Radio button.
Click on SAVE and Initiate.
6. Build Integrated Configuration (ICO):
Click on NEW – > Coordinated Setup (make ICOs).
Give the Coordinated setup name and namespace. It ought to be indistinguishable from the ESR Outbound Help Point of interaction name and namespace.
Import the shipper divert and in next tab, select the business part under which the collector correspondence channel is made.
Import the Activity planning (for first ICO, no activity planning exists) from ESR. Activity planning will consequently show in the event that you have offered right Support Connection point name and namespace while characterizing Coordinated design name and namespace.
Import the recipient correspondence channel.
Click on SAVE and Initiate.
That is finished. We have made EDI to intermediary interface without any preparation. We should test it.
7. Testing the Interface:
SFTP, I have transferred an example EDI 810 document.
first ICO, no planning happens. In the event that EDI document contains various receipt sets, it will be parted separately.
second ICO source channel, the module we added for change to XML.
Also, planned to the ECC structure through message planning and went to ECC through intermediary.
SXI_MONITOR:
We have successfully developed and tested the Interface Development – B2B EDI Inbound to XML Proxy to ECC interface. Hope you found it helpful. If you have any doubts, questions, or suggestions for us, please feel free to leave your comments below.
YOU MAY BE INTERESTED IN:
Do all ABAPers know Fixed Point Arithmetic?
Understanding IDoc Status in SAP SD: A Comprehensive Guide
WhatsApp us