Header Mapping in Receiver Agreement

[Former Member]

Hi Friends,

Can anybody explain very clearly what is the real use of <b>Header Mapping in Receiver Agreement.</b>

Please explain : What is Header Mapping?

WHy we need to use Header Mapping

& When we need to use Header Mapping

Kindly answer for the above 3 questions step by step.

[Former Member]

Hi,

As mentioned in above replies, Header Mapping in Receiver Agreement is used for replacing internal names of Business Partners with neutral names.

Well, this, in general terms, means that you could provide a different name than that of Business Service, Party etc. already used in configuration.

For example, in case of posting idocs, you could change the name of sender service to Business Partner name in receiver agreement header mapping. Thus an ALE Logical System name could be provided in header mapping which ensures proper posting of idoc.

Thanks,

Bhavish

[Former Member]

Business partners involved in cross-company processes do not generally publish the names of their internal business systems (and integration processes), but instead mask them using business services or Party names. Business services represent the internal system landscape externally.

To mask parts of the system landscape by using a Party name or business service, partner defines a header mapping. The header mapping ensures that the name of a business service (and not the business system or integration process service) is written in the header of the outbound message.The configuration of B2B processes typically demands high message security requirements.

Pravesh

[former_member335553]

refer this thread for an example

http://help.sap.com/saphelp_nw04/helpdata/en/b2/1f17419b24f06fe10000000a1550b0/frameset.htm

[former_member335553]

Hi

//**In the header mapping you can map the values of the following key fields of the receiver agreement to other values: sender and receiver party, sender and receiver service. The address fields (sender, receiver) in the message header are then transformed correspondingly during outbound processing

Help link answers all ur questions

http://help.sap.com/saphelp_nw04/helpdata/en/5d/112d20f6ce6c46ba66afb98d278fbd/content.htm