Configuring IDOC Runtime

Posted on Aug. 18, 2010 at 11.38 AM - Kuala Lumpur, Malaysia

Another question that commonly asked by PI developers is: "How do we configure PI for IDOC integration scenario?". This blog is going to list down basic configuration steps which are required at each SAP PI component, as well as at the back end system.

Configuration required at the SAP back end system:

1. Create logical system name
2. Assign logical system name to the respective client
3. Create RFC Destination <INTEGRATION_SERVER_ABAP> Type ABAP to SAP PI. This is ONLY required if you have not created one for sending IDOC to integration server.
4. Create outbound port using transaction WE21. We do not need to create inbound port, as it is automatically available.
5. Create partner profile using transaction WE20, or create distribution model using transaction BD64 and generate partner profile from it.

Configuration required at the SAP PI system (ABAP stack):

1. Create logical system name
2. Assign logical system name to integration server client (normally it's 001)
3. Create RFC Destination <BACKEND_ABAP> Type ABAP to SAP back end. This is required for SAP PI to extract IDOC metadata from the SAP back end system.
4. Create port to SAP back end system using transaction IDX1
5. Import IDOC metadata using transaction IDX2 from SAP back end system.

Configuration required at the SAP PI system (Java stack):

1. Make sure in SLD, that the logical system name for the business system is maintained
2. Import IDOC metada from the SAP backend system to Enterprise Service Repository (ESR)
3. Make sure that logical system name is updated to the 'imported' business system at integration builder (Communication component->Adapter specific Identifiers)

Life is beautiful! Let's make it meaningful and colorful!