Identifier tab in Communication Channel

[Former Member]

Hi,

When do we populate "Identifier tab in Communication Channel"

Thnx

Raj

[Former Member · Accepted solution]

Check this document...

https://websmp104.sap-ag.de/~sapdownload/011000358700003604082004E/HowTo_IDOC_XI_Scenarios.pdf

it talks about different scenarios when sedning IDOCs, the scenario where the partner type is "LS" or "KU" has makes use of the entries in the Identifiers tab in the IDOC adapter...

[sam_raju]

Hi Raj,

The Identifers in Communication channel are used to uniquely identify communication Parties(B2B).

These are used mainly in the B2B Scenarios. You can find more information on this topic in the help.sap.com webiste.

But Let me give you an example to explain this.

In case of A2A Scenarios, Business Systems are used for A2A communication with Business System defined in SLD. The Idoc Adapter builds the Idoc control record during runtime by retrieving the information from SLD for the Business system.

In case of B2B scenarios for exchanging messages with your external partners(Vendors, Customers, Bank etc.), you have to use Business Service instead of Business system. In addition, you have to define Parties with Unique identifiers like DUNS Number etc.

Here you also need to define alternative identifier that uniquley identifies these parties in the backend R/3.

The syntax would be

Agency=SR5_100(Business System for backend R/3) Schema=ALE#LI#LF (Where LI is the Partner Role in R/3

LF is the Partner function in R/3)

Name= 0000100000 (Partner Number same as in the R/3 Partner Profile)

The "Identifier" Tab is used to specify the Agency and Schema as mentioned above( Agency=SR5_100, Schema=ALE#LI#LF). With this information in Identifier Tab, the Idoc Adapter builds the control record based on the information from the Party definition during runtime.

Hope this helps.

Regards,

Sam Raju

[sam_raju]

Hi Raj,

The Identifers in Communication channel are used to uniquely identify communication Parties(B2B).

These are used mainly in the B2B Scenarios. You can find more information on this topic in the help.sap.com webiste.

But Let me give you an example to explain this.

In case of A2A Scenarios, Business Systems are used for A2A communication with Business System defined in SLD. The Idoc Adapter builds the Idoc control record during runtime by retrieving the information from SLD for the Business system.

In case of B2B scenarios for exchanging messages with your external partners(Vendors, Customers, Bank etc.), you have to use Business Service instead of Business system. In addition, you have to define Parties with Unique identifiers like DUNS Number etc.

Here you also need to define alternative identifier that uniquley identifies these parties in the backend R/3.

The syntax would be

Agency=SR5_100(Business System for backend R/3) Schema=ALE#LI#LF (Where LI is the Partner Role in R/3

LF is the Partner function in R/3)

Name= 0000100000 (Partner Number same as in the R/3 Partner Profile)

The "Identifier" Tab is used to specify the Agency and Schema as mentioned above( Agency=SR5_100, Schema=ALE#LI#LF). With this information in Identifier Tab, the Idoc Adapter builds the control record based on the information from the Party definition during runtime.

Hope this helps.

Regards,

Sam Raju