Header Mapping

Hey folks
I would like to know the significance of Header mapping in B2B scenarios ? and is it mandatory for B2B ?
I want to know why do we really need it.
Thnx

Hi
Sorry for confusing reply.
In the header mapping you can map the values of 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.
The header mapping is important when configuring cross-company processes in which the business partners want to replace the names of their internal business systems with neutral representatives (party, business service).
If you want to replace the internal name of a sender business system in the outbound message with a neutral name of a party and service, specify the fields for Sender Party and Sender Service in the header mapping.
You can do the following in the header mapping:
●      Specify fixed values
●      Define that the conversion of the field values is to be determined dynamically from the message payload
Header mappings are only supported by the following receiver adapters at runtime:
-          IDoc Adapter
-          Plain HTTP adapter
-          RNIF Adapter 2.0
-          RNIF Adapter 1.1
-          CIDX Adapter
I tried to use SAP words here to make you understand. Does this workout
Thanks
Gaurav

Similar Messages

Need help in header mapping!!

Hi, because we have an third party system i think i have to use header mapping in receiver agreement!
For outgoing IDocs everything works fine, incoming aren't be transfered to target system.
I have:
ThirdParty: EDI
BusinessService: EDI_Test
Business System: Q01CLNT010
Incoming receiver agreement looks like this:
Sender
Party: EDI
Service: EDI_Test
Receiver
Service: Q01CLNT010
Interface: DELINS.DELFOR02
Namespace: urn:sap-com:document:sap:idoc:messages
Header Mapping (like i thought)
Sender-Party: EDI
Sender-Servcie: EDI_Test
Reciever Party:
Reciever Service: Q01CLNT010
The incoming IDoc has follwoing parameters in header Segment:
- <EDI_DC40 SEGMENT="1">
<TABNAM>EDI_DC40</TABNAM>
<MANDT>100</MANDT>
<DIRECT>1</DIRECT>
<IDOCTYP>DELFOR02</IDOCTYP>
<MESTYP>DELINS</MESTYP>
<STD>V</STD>
<STDVRS>096001</STDVRS>
<STDMES>DELINS</STDMES>
<SNDPOR>EDI</SNDPOR> [like port in we21]
<SNDPRT>LS</SNDPRT>
<SNDPRN>EDI</SNDPRN>
<RCVPRT>LS</RCVPRT>
<RCVPFC>LF</RCVPFC>
<RCVPRN>30396</RCVPRN>
<CREDAT>20071204</CREDAT>
<CRETIM>130428</CRETIM>
<REFMES>DELFOR02</REFMES>
</EDI_DC40>
can somebody give me a hand on this?!
br

Hi guys,
because of help approach i wrote what i have done yet. But first i explain what is working.
We have an EDIServer in our Landscape which sends EDI-Calls. This Calls are triggered from R/3 via XI to EDIServer. This outgoing communication runs. (plz don't ask why we still use EDIServer because of EDI-Adapter for XI)
I configured this scenario with party!
But now i want to get calls from EDIServer. So i have to work with send IDocs from EDIServer which this previously tronsforemed from EDI-Format in IDoc-Format.
So i simply thought i configure scenario the other way round by using the party again. But this does not work out. However, i explain my IB Rep Objects:
Receiver Determination:
Sender
Party: EDI
Service: EDI_Test
Interface: DELINS.DELFOR02
Receiver
Party: *
Service: *
Interface Determination:
Sender
Party: EDI
Service: EDI_Test
Interface: DELINS.DELFOR02
Namespace: urn:sap-com:document:sap:idoc:messages
Receiver
Party: *
Service: *
Sender Agreement:
Sender
Party: EDI
Service: EDI_Test
Interface: DELINS.DELFOR02
Namespace: urn:sap-com:document:sap:idoc:messages
Receiver
Party:
Service:
Receiver Agreement
Sender
Party: EDI
Service: EDI_Test
Receiver
Party:
Service: Q01
Interface:DELINS.DELFOR02
Namespace:urn:sap-com:document:sap:idoc:messages
--> do i need header mapping here?!
What do i need to do to make this scenario run?!
br - i highly appreciate ur previous help!!!!

Error: Could not read Header Mapping in Receiver Agreement

Dear SAP experts,
Newly installed SAP G7A PI 7.1(Acceptance box) was already released to customer.
We are doing an initial test (BAT phase), wherein, our end-to-end scenario is, from a EP Portal application ---> G7A PI 7.1 --> Trading Partner via AS2 protocol.
G7A PI is connected to Trading Partner via AS2 protocol.
Currently, our EP Portal application is in-active at the moment, that's why we used 'manual XI submitter', to send a message from G7A PI itself going to Trading Partner.
The message was success in the Integration engine of G7A PI, and the output message was produced.
As the message reached the Adapter Engine layer of G7A PI, we encountered a specific error,
Delivering the message to the application using connection AS2_http://seeburger.com/xi failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: javax.resource.ResourceException: Fatal exception: com.seeburger.xi.connector.queue.TaskBuildException: Could not create CPAObjectMapper: InvocationTargetException caused by Could not read Header Mapping in Receiver Agreement: while trying to invoke the method com.sap.aii.af.service.cpa.Party.getParty() of an object returned from com.sap.aii.af.service.cpa.NormalizationManager.getXIParty(java.lang.String, java.lang.String, java.lang.String), Could not create CPAObjectMapper: InvocationTargetException caused by Could not read Header Mapping in Receiver Agreement: while trying to invoke the method com.sap.aii.af.service.cpa.Party.getParty() of an object returned from com.sap.aii.af.service.cpa.NormalizationManager.getXIParty(java.lang.String, java.lang.String, java.lang.String)
Basically, "Could not create CPAObjectMapper - InvocationTargetException caused by Could not read Header Mapping in Receiver Agreement"
I am thinking, one of the possible cause is that we used manual XI submitter, in G7A PI, instead of the utilizing the actual Sending system (EP Portal application).
Or possible cause is that the AS2 adapter in G7A is not yet stable, thus causing the issue.
We've already done successful connection when we're in GDD PI (Development box) during our SIT phase.
Objects in G7A were mirror of GDD PI.
Kindly advise for your inputs.
Thanks!
Gerberto

Hi,
It seems that the cause of the error is the unstable performance of the PI box, since, this was newly installed and there were patches that were not yet added.
Thanks for the support!
Gerberto

Use of Header Mapping

Hi,
I want know about Header Mapping When it required and what is it. In what condition we will use that.
Thanks,
Seshu

Hi,
The header mapping is made available in the receiver agreement. It is required in the IDoc adapter, for example, because the IDoc adapter does not know any communication parties.
After header mapping, the adapter must also convert the address to an external protocol.
The following fields can be specified and replaced for outbound processing:
·        Sender party
·        Sender service
·        Receiver party
·        Receiver service
Regards
Bhanu
Intelligroup

Reg:HEADER MAPPING

I really want to know the use of HEADER MAPPING IN IDOC based scenarios : for what purpose do we need to specify the fields
sender service:
sender party:
receiver service:
receiver party:
in header mapping,if header mapping is not specified do IDOC based scenarios works?

HI,
You need not specify the header mapping in IDOC based scenarios. If its idoc to file then you have maintain adpater specific identifiers in your business system. If its file to idoc then too header mapping is not necessary.
Follow these links.
https://wiki.sdn.sap.com/wiki/display/XI/FileToIDOC
https://wiki.sdn.sap.com/wiki/display/profile/2007/05/11/FileToIDOC
https://wiki.sdn.sap.com/wiki/display/profile/2007/05/11/FileToIDOC-Part2+%28Configuration%29
https://wiki.sdn.sap.com/wiki/display/profile/2007/05/11/FileToIDOC-Part3%28StepsrequiredinXIandR3%29
https://wiki.sdn.sap.com/wiki/display/XI/StepbyStepProcedureofIDOCtoFileScenariousingBPM
Regards,
Merrilly

Header Mapping & Value Mapping in XI

Hi All,
I Request you to send me the documentation with screen shots about Header mapping and Value mapping.
I am very thankful to you in advance.
Regards,
Nagarjuna.

hi,
For these basic questions Search SCN.You will get many links.
this will be helpful
ValueMapping using the Graphical Mapping Tool
regards,
ujjwal kumar

Sending IDoc Batches to SAP: Issue with Header Mapping for SNDPRN

We are sending batched IDocs from XI to SAP. We need the individual IDocs to reflect different SNDPRN values. Our mapping creates the different IDoc EDI_DC40 record correctly with different SNDPRN values. However, XI wipes out the SNDPRN values in the payload. When we define Header mapping to get the Sender Party as the XPath to the SNDPRN in the payload, then the header mapping errors out because the XPath returns multiple values.
I wanted to know if anyone has successfully implemented sending IDoc batches to SAP from XI with different SNDPRN values.
Your feedback is appreciated.
Jay Malla
Licensed To Code
Genentech SAP XI Team

Hello,
I have the same problem. I want XI send an IDOC with the SNDPOR, SNDPRT and the SNDPRN that are in the EDIDC40.
I find this in sap.help : 
Mapping
The IDoc adapter does not make any special demands on mapping. The IDoc adapter must simply be provided with an IDoc XML structure at the Integration Server outbound channel. This either already exists or must be generated by using a mapping.
If the IDoc XML structure contains a control record, it is deleted and created again by the IDoc adapter. If you want to include additional values in the control record, you must select the Apply Control Record Values from Payload checkbox in the parameters in the communication channel and provide a corresponding mapping for the values.
You can include the values from the following fields in your IDoc control record:
MESCOD, MESFCT
TEST
EXPRESS
STD, STDVRS, STDMES
SNDSAD, SNDLAD
RCVSAD, RCVLAD
REFINT, REFGRP, REFMES
http://help.sap.com/saphelp_nw04/helpdata/en/b9/c5b13bbeb0cb37e10000000a11402f/frameset.htm
Perhaps we must use party configuration but I don't know how do this !
Regards,
Chris

Content Objects or XPATH in Header mapping..!! How to provide??

Hi All,
Iam doing B2B scenarios where i need to pass the Party name by based on the content of the message in the header mapping.
I think we can do by using Content Objects or XPATH in Header mapping, but the structure is not displaying in the Content Objects or XPATH in Header map in order to provide the condition.
I need to do anything else to see the structure over there?
Waiting for your replys.
Thanks&Regards
Seema.

Hi,
If you get the following msg while selecting the BS in Receiver Determination
"Message interface does not exist in any software components installed on this business system"
1) Open ID-----Double click on Business system that which u are using in the scenario
2) Check whether you are able to see the SWC in the Othere attributes TAB
3) If it is not there means goto SLD----Open the Technical System of R/3 by choosing Web as ABAp type
4) Click on Installed Products TAB
5) Click on Add New product and add your Product of the SWC whcih you are using for developement and Save it
6) Then goto Business systems TAB in the same Technical systems window and click on the Business System appears in the window.
7) Click on Installed products and Check the check box of your Product and then finally save that.
Now you should be able to see the SWC in the Othere attributes TAB in ID
Regards
Seshagiri

Difference in idoc adapter header mapping between SP14 and SP19

Hi All,
i have a very strange problem.......i have 2 XI systems : XI-sandbox and XI-dev.....
XI-sandbox is on XI3.0 SP19 whereas XI-dev is on XI3.0 SP14...........
I have a file->XI->idoc scenario which is same on both XI-sandbox and XI-dev....
in receiver idoc adapter, i am using header mapping for sender service and in the sender service i am using XPATH of a field of control rec of idoc.........
this scenario works fine on XI-sandbox which is on SP19 and the idocs are sent to SAP R/3 sandbox...........but this scenario on XI-dev gives error in SXMB_MONI in XI-dev of Call adapter - "No party conversion found".........
So my question is that is there any difference in idoc adapter header mapping between SP14 and SP19.........
Thanks,
Rajeev Gupta
Message was edited by:
RAJEEV GUPTA

>so i cant use apply control rec values from payload.........
rajeev,
I know this has nothing to do with the original problem but please do bear.
If I undertood you posts correct, the Sender Partner Name is set in the Idoc Control record in the field SNDPRN in the mapping using some mapping logic.
Now, this is the partner name with which the idoc is to be posted to thge R3 system.
if yes, then like I have pointed above, using "Take Sender From Payload" in the Receivcer Idoc Adapter is a better option as pointed in the SAP help as well.
As you are already populating the idoc control ecord with SNDPRN just make the SNDPRT as LS and then select "Take Sender from Payload" in the receiver Idoc adapter and the Sender Partner Name will not be taken from SDNPRN just as you want.
This is different from "Apply Control Records From Payload" .
Regards
Bhavesh
PS : you can ignore this reply if the situatios is too late to make this change and thanks for the patience.

IDOC Acknowledgement and Header Mapping

Dear all,
I've got the following scenario:
SAP 4.6C is sending many different IDOCs to XI 3.0 (SP14).
On XI side there are several integration processes, business systems and business services receiving the IDOCs.
I want to create IDOC acknowledgements and send them back to SAP system.
For one integration process I was able to successfully create and send back an acknowledgement by following the steps described in the very good blog:
/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
Now I want that every integration process/business system/business service is sending back an acknowledgement with the same logical system name (meaning "this acknowledgement is coming from XI").
As it is not possible to enter the same logical system name for more than one process I created a receiver agreement with:
Sender Service = the integration process
Receiver Service = the SAP 4.6C business system
Receiver Interface = ALEAUD.ALEAUD01
Receiver Communication Channel = IDOC receiver channel called "Ack_IDOC_Receiver", existing in SAP 4.6C business system and pointing to this system
Additionally I created a header mapping in this receiver agreement where I set the Sender Service to the business system of the XI system.
Unfortunately the tests showed to me that obviously the header mapping (maybe even the whole receiver agreement) is being ignored completely as no Acknowledgement IDOC will be created. Instead I get the error message "Unable to convert sender service to an ALE logical system".
I also played around a bit with the options "Apply Control Record Values from Payload" and "Pass Sender value from Payload" but this didn't make any difference.
Why is the header mapping not replacing the sender service in the acknowledgement message?
Best regards,
Tobias

Tobias,
we have the same Problem.
we´re sending with Receiving Partner "12345" and the IDoc in the target System is filled with the standard SAP Value maybe the one configured in the SDL.
We have configured our IDOC_REceiver with a mark on "Apply Control Record Value from payload".
If you have a look at the SAP Helpfile you will find out that some header fields are not be changeable and get the value from sap.
like IDOC-Number, Receiving Partner and maybe the sender service ???
Regards,
Gordon

Header Mapping in Receiver agreement.?

Hi All,
When we do B2B scenarios using AS2 adapters.
1. Is it mandatory to use Header Mapping in Receiver agreement.?
2. If yes, is it enough if we provide Party Names? or we need to provide Business system or Business service names as well?
3. What is the purpose of this Header Mapping?
Kindly share your answers.
Regards
Deepthi.
Edited by: deepthi reddy on Jan 31, 2008 6:49 AM

Hi Deepthi,
1) Is it mandatory to use Header Mapping in Receiver agreement?
https://www.sdn.sap.com/irj/sdn/forums
2)What is the purpose of this Header Mapping?
The header mapping is important when configuring cross- company processes in which the business partners want to replace the names of their internal business systems with neutral representatives (party, business service).
Example
if you are doing a file to IDoc scenario, now while mapping the data to IDoc in mapping if you map the IDoc segment called EDI_DC40 with all required data then you have to user the Header mapping in the agreement so that whatever data you have mapped will be picked from payload. And if you do not use this header mapping then then XI will take care of it.
You can do the following in the header mapping:
● Specify fixed values
● Define that the conversion of the field values is to be determined dynamically from the message payload
To specify the header mapping for an address field, select the check box for the field name (for example, sender service) and choose Display List of Permitted Values (This graphic is explained in the accompanying text).
There are different editors for specifying the party and service:
● Use the party editor to specify a party
● Use the service editor to specify a service
Caution
Header mappings are only supported by the following receiver adapters at runtime:
IDoc Adapter
Plain HTTP adapter
RNIF Adapter 2.0
RNIF Adapter 1.1
CIDX Adapter
3)If yes, is it enough if we provide Party Names? or we need to provide Business system or Business service names as well?
http://help.sap.com/saphelp_nw04/helpdata/en/5d/112d20f6ce6c46ba66afb98d278fbd/frameset.htm
Regards
Azeez khan.

HEADER MAPPING in RECEIVER AGREEMENT use.?

Hi folks,
Can anyone explain me about the HEADER MAPPING in RECEIVER AGREEMENT. In which cases we go for this header mapping.
Give me an example if possible or any links regarding this.
Thanks in advance
Srinivas Reddy.

Dear Srinivas,
Go through the following link and you may get some idea on this.
http://help.sap.com/saphelp_nw70/helpdata/en/b2/1f17419b24f06fe10000000a1550b0/content.htm
Regards,
JP.

Header Mapping in Idoc scenarios

What is the use of Header Mapping in IDOC based scenarios?

Hi,
Header maping can be used to determine the destination in the interface based upon any particular field .If the field is populated with the value then that value can be used for receiver determination to send message for example you have one file that can be mapped to any one pf the multiple IDOCs then based upon the header value you can determine the destination or the IDOC goin to be used
Ckeck this link this will help you a lot
reg:HEADER MAPPING
Check these links also
Header Mapping in File to IDoc
Header mapping while using IDoc as receiver communication
Thanks
Vikranth
Edited by: Khimavath Vikranth on May 28, 2008 9:30 PM

Header Mapping Doubt

Hi All,
I have gone through this URL and i couldnt get clear my self
http://help.sap.com/saphelp_nw04s/helpdata/en/b2/1f17419b24f06fe10000000a1550b0/frameset.htm
In which case we will apply the Header Mapping concept and can any one give me clear Exapmle
Let us assume my Inetrface is File--Idoc
Regards

Hello Suman,
This may answer your question,
The header mapping is important when configuring cross-company processes in which the business partners want to replace the names of their internal business systems with neutral representatives (party, business service).
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. Business services represent the internal system landscape externally.

Header mapping ...how it is done step by step

Hi Masters,
Actually i have lot of confusion in header mapping .... so can u please help me that what is header mapping ... how and where it is implemented .. if it is step by step with example then it will be very much helpful for me............
Thanks in advance,
jp

Hi,
The header mapping is made available in the receiver agreement. It is required in the IDoc adapter, for example, because the IDoc adapter does not know any communication parties.
After header mapping, the adapter must also convert the address to an external protocol.
http://help.sap.com/saphelp_nw2004s/helpdata/en/b2/1f17419b24f06fe10000000a1550b0/content.htm
Adapter-Specific Message Attributes in the Message Header Use -
http://help.sap.com/saphelp_nw04s/helpdata/en/43/0a7d1be4e622f3e10000000a1553f7/content.htm
Header info - Access of XI Message Header Information
Regards
Khanna

Header Mapping

Similar Messages

Maybe you are looking for