Header Mapping

[Former Member]

Hi all,

I am new to XI and I've been trying to get the following to work: - basically, 2 different R/3s (46C), 1 XI (7.0) and a third-party marketplace. R/3 sends & receives IDOCs thru and from the only XI_1 which communicates with Marketplace (MarketPlace Adapter) via xCBL documents. XI_1 does the transformation from IDOC to xCBL and back.

Routing to the marketplace is done via DDIDs whilst IDOCs will use the Customer number or Vendor numbers (ALE#KU ALE#LI). R/3_A & R/3_B is configured as business systems. Documents used are PO, CO, POR/SO & Invoice.

R/3_A <-IDOC-> XI_1 <-xCBL-> Marketplace <-xCBL-> XI_1 <-IDOC-> R/3_B

R/3_A actually has more than one Customer number (KU). Right now, I am using header mapping (receiver agreement) via a proxy party for R/3_A to put in the ALE#KU info. However, I do not know how to handle for more than 1 ALE#KU cause XI will complain of duplicates.

Also, since R/3_A is a business system, I cannot setup the same receiver agreement eventhough I want to put in a separate header mapping.

Please advise.

Thanks,

WCP

Message was edited by:

Chun Poh Wong

[Former Member · Accepted solution]

Chun Poh Wong,

Have a look at the Receiver Determination options where you can configure the receiver based on a condition. Receiver Determination url

http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm

Standard Receiver Determination url - refer to the section on defining conditions

http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm

Regards,

Mike

[Former Member]

Chun Poh Wong

Please refer to the following url for information on the Integration Builder

http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm

You can then drill down to the <b>Design Time</b> and <b>Configuration Time</b> components

Design Time will provide information on BPMs, Integration Processes, Mappings (transformations) etc

Also refer to the example scenarios in the Design: Integration Builder

<b>Software component</b> SAP BASIS

<b>Software component version</b> SAP BASIS 6.40

<b>Namespace</b> http://sap.com/xi/XI/System/Patterns

<b>Integration Scenarios and Integration Processes</b>

<b>Integration Processes</b> Now you can review the different patterns

Regards,

Mike

[Former Member]

OK, now I have a different issue. Header mapping (according to Help) cannot be used for Marketplace Adapter.

Since the R/3_B bus. sys. does not contain DDID, I need a workaround to map the header with a party that does contain the DDID before sending the document out to the marketplace.

Is there any way to do this? I was suggested to use BPM to extract the DDID from the intermediate party but I am not familiar with BPM.

Thanks very much,

WCP

[bhavesh_kantilal]

Set the Sender Partner Name (SNDPRN) Sender Partner Type (SNDPRT ) in the Idoc control record in the mapping and in the Idoc adapter select option Take Sender from Payload.

This will allow you to post multiple Idoc's using same Idoc adapter to R3 with different partners.

Regards

Bhavesh