Sample CIDX Scenario in SAP PI

[Former Member]

This documents explains how to develop objects in Integration directory for Chemical Industry Standard Scenarios in SAP PI.

Consider a scenario where seller wnats to send Invoice ChemXML to buyer. Here we use ChemXML transaction E81 for Invoice.

In this example, PI receives INVOIC01 IDOCs from SAP ECC and sends ChemXMLs to CIDX complaint system.

We need not to create objects in Enterprise Service Builder as we have predefined objects and mappings in CIDX and CIDX ERP software components.

Below screenshots are from Integration Directory.

For Outbound (from PI perspective), we have to create a party for Seller and specify the DUNS number. We will use this in header mapping of outbound CIDX message.

DUNS number is a unique 9-digit number that is used to identify a Party in the exchange of CIDX business documents. This is available to organizations by registering with Dun and Bradstreet.

Seller Party:

    We will use this Seller party in header mapping.

    Enter the DUNS number of Seller under Identifiers tab.

Buyer Party: CIDX complaint system in this example.

  Enter the DUNS number of buyer under Identifiers tab.

Buyer Communication Component:

 

Seller Communication Component :

  In this example, SAP ECC business system is our sender communication component.

Sender Communication Channel:

  There is no need to create a sender communication channel as our sender is SAP ECC.

Receiver Communication Channel:

   Sender Agreement:

    No need to create sender agreement as PI receiving IDOCs from SAP ECC.

  Receiver Agreement:

   In the header mapping, specify the seller communication component. This actually doesn't present in PI objects but we have to enter this here for service header mapping. Follow the CIDX communication component naming convension while entering the name here.

Receiver Determination:

Interface Determination: