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

Similar Messages

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

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

How can I include the Header Information....for a File to IDOC Scenario

Hi,
I made a File to IDOC Scenario with DEBMDM06 for MDM>XI>SAP R/3. The Header Information in the XML File which is at the XI end is Missing. For that reason In Tcode SXMB_MONI we are getting an Error that "HEADER Information Missing: Message should Start with EDI_DC40" i.e the Header Information.
My Question is that whether we can do some changes in the Message mapping Step in the Integration Repository. I HardCoded the Few mandatory Fields that were there but it Again gave me the Same Error as above.
Can you please Suggest some Solution for this. Since the data is Coming in from MDM part the Header information is not there but It actually Important as it has got all the Port Information.
Kindly Inform me some Solutions.
Thanks & Regards
Somnath

Hi Suraj,
Thanks for ur Reply, but Since we are Doing a File to IDOC Scenario the IDOC DEBMDM is on the Right Side in Message Mapping and as U know it is Mandatory to Map an IDOC on the Right Part. EDI_DC40 is coming as it is there in the IDOC but our XML File Does not have that. If we Don't Map then it Becomes RED, which is an Error.
Furthermore in the Receiver Agreement we have put the Necessary Details such as Sender Service and Receiver Service along with the IDOC Communication Channels.
Can U give as a Better Insight on this Note how to check the Header Part as it is mandatory to MAP.We also tried to HARDCODE it by putting those Values and Mapping them to a Constant but it is Giving the Same Error.
Thanks and Regards
Somnath

File to IDOC scenario : Error with mapping due to Context handling

Hi Experts.
I have a file to IDOC scenario which need your advice.
Source File structure as follows:
Control_Header <1:1>
Invoice_Header <1:unbounded)
Invoice_Line <1:unbounded)
Trailer <1:1>
Payload as follows capture from SXMB_MONI
- <Control_Header>
 <Key>999</Key>
 <TransactionID>RCTV</TransactionID>
</Control_Header>
- <Invoice_Header>
 <Key>000</Key>
 <BusinessUnit>HDB05</BusinessUnit>
 <InvoiceNo>64471</InvoiceNo>
</Invoice_Header>
- <Invoice_Line>
 <Key>001</Key>
 <UnitPrice>7.00000</UnitPrice>
 <Quantity>1.0000</Quantity>
 <GSTAmount>0.49</GSTAmount>
 <GSTRate>0.07</GSTRate>
</Invoice_Line>
- <Invoice_Line>
 <Key>001</Key>
 <UnitPrice>8.00000</UnitPrice>
 <Quantity>1.0000</Quantity>
 <GSTAmount>0.56</GSTAmount>
 <GSTRate>0.07</GSTRate>
</Invoice_Line>
- <Invoice_Header>
 <Key>000</Key>
 <BusinessUnit>HDB21</BusinessUnit>
 <InvoiceNo>6Y0575</InvoiceNo>
</Invoice_Header>
- <Invoice_Line>
 <Key>001</Key>
 <UnitPrice>49.50000</UnitPrice>
 <Quantity>1.0000</Quantity>
 <GSTAmount>3.47</GSTAmount>
 <GSTRate>0.07</GSTRate>
</Invoice_Line>
- <Trailer>
 <Key>TRL</Key>
 <TransactionID>RCTV</TransactionID>
 <TotalFeedLine>96</TotalFeedLine>
 <HashTotalValue>212.00</HashTotalValue>
</Trailer>
</ns:MT_EINVOICE>
Mapping as follow:
 IDOC
<Control_Header> -> <Control_Header>
<Invoice_Header> --> <Header_Invoice>
<Invoice_Line> ---> removeContext --> <Line_Invoice> this is the child node of <Header_Invoice>
<Trailer> -
> <Trailer>
The result of the using the above Payload get the following result which not wht I seek
<Control_Header>
<Header_Invoice>
 <Line_Invoice>
 <Line_Invoice>
 <Line_Invoice> *** This belong to the Invoice_Line of the second <Header_Invoice> at the payload
<Header_Invoice>
 <Line_Invoice> *** THis segment is empty
<Trailer>
I required the Line_Invoice to belong to the child of the second <Header_Invoice>, I have tried using
removecontext with splitVaue and collaspeContext but to no avail.
May I know what is my mistake on the mapping of the Invoice_Line to Line_Invoice>
Rgds
FNG

Hello,
There should be something that could correlate the Invoice_Header/Key and Invoice_Line/Key. In your example, both are the same for the first and data set. If the sample looks like the one below, it is possible to sort things by correlating the Invoice_Header key and Invoice_Line key
<Invoice_Header>
<Key>000<Key>
</Invoice_Header>
<Invoice_Line>
<Key>000<Key>
</Invoice_Line>
<Invoice_Line>
<Key>000<Key>
</Invoice_Line>
<Invoice_Header>
<Key>001<Key>
</Invoice_Header>
<Invoice_Line>
<Key>001<Key>
</Invoice_Line>
An example mapping could look like this
For Header
Invoice_Header --> Header_Invoice
For Line
/InvoiceLine/Key --> removeContext --> splitByValue:valueChanged --> Invoice_Line
The subfields of the invoice line would also follow a similar logic, you just need to use formatByExample --> splitByValue:eachValue so that the context levels are the same.
Hope this helps,
Mark

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 File to IDoc

Hi all,
When do we go for Header mappin in File - IDoc scenario? How we can configure these steps in XI?
regards,
Anjaneya

Hi Swamy,
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
Regards

Doubt in fields - message mapping (file 2 idoc scenario)

while doing message mapping in file 2 idoc scenario, i could not able find the values for some field names
( i am following this wiki help
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC& )
cremas04 idoc
vendorNo LIFNR
vendor name Name1
Pur_org ? ( I could not able locate field with the similar desc in idoc MT side)
Company code ?
Acc_Grp ?
Search term MCOD1
Address ADRNR
City ORT01
Pin_code PSLTZ
could you help me out with this?
Message was edited by: praba
praba

hi,
I got the answer.

Mapping of Control records in file to idoc scenario

Hi,
In the mapping part of file to idoc scenario is it necessary to provide the exact control record details
or will it pick what ever is mentioned ? Can any one please explain regarding the same?
Many Thanks,
Sharath

hi,
in case of apply control records from payload
It is indeed very simple to do it and the feature is available from SP10. I have seen lot of posts on the forum for the same and that is the reason for this blog. We can manipulate the control record in the mapping editor and map the EDI_DC40 segment of Idoc as required. Most of the times we need to map only SNDPRN, RCVPRN, SNDPRT, RCVPRT for posting Idocs with appropriate partner profiles in SAP R/3 destination systems. We can disable the rest of the fields as shown below. We need to manually change the control record of idoc for populating partner profiles in the control records while dealing with non-sap sender system, which will be used by receiver SAP system for posting idocs with appropriate ALE configurations.
check this blog
/people/sravya.talanki2/blog/2005/12/02/manipulating-idoc-control-records-from-payload
regards
chandra

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

Mapping issue in jdbc to idoc scenario

Hi
we have a jdbc to idoc scenario , we need to repeat the segment given below which has only two fields FLDGRP and FLDVAL,
both filed_Group and fieldgroup1 is coming simultaneously . when field group =BATCH, batch=FLDVAL and fieldgroup1=CUST cust_code=FLDVAL
mapping is as follows :
E1WXX01 (segment name) occurance 0:9999999999
fieldgroup----
> FLDGRP
batch----
>FLDVAL
fieldgroup1----
>FLDGRP(same filed as above )
cust_code----
>FLDVAL(same filed as above)
pl sugggest how to map using graphical mapping
rgds
arun

I see the problem here... hmmm.. It is simple
You need to just duplicate the E1WXX01 segment by right clicking and pressing Duplicate Subtree.
Once you do duplication of segment then you will have two segments of E1WXX01.
In first segment map
> fieldgroup----
> FLDGRP
> batch----
>FLDVAL
and in second segment of E1WXX0, map
> fieldgroup1----
>FLDGRP
> cust_code----
>FLDVAL
Regards,
sarvesh

Header mapping while using IDoc as receiver communication

Hi All,
Can any one brief me with header mapping while configuring receiver determination when IDoc is used for receiver communication.
Thanks,
Govindu.

Hi,
To change the Partner Type( SNDPRT and RCVPRT ), you use Header mapping in the receiver agreement.
If you use APPLY CONTROL RECORD FROM PAYLOAD, the following values are filled from tha payload,
MESCOD
MESCFT
TEST
EXPRSS
STD
STDVRS
STDMES
SNDSAD
SNDLAD
RCVSAD
RCVLAD
REFINT
REFGRP
REFMES
STATUS
DIRECT
OUTMOD
CREDAT
CRETIM
Take sender from payload and take receiver from payload, are used to change the value of SNPRN and RCVPRN.
Regards,
Bhavesh

IDoc to IDoc Scenario - Correct Interface Mapping configuration

Hello All,
i have to configure an Interface Mapping for an IDoc to IDoc scenario.
IDoc Type for sending and receiving already imported and located under Imported Objectes\IDocs in respective Software Component Version.
Now, how is the correct configuration? Add the sending respectively receiving IDoc Type directly to Source Interface/Target Interface under Display Interface Mapping or create first a sending Message Interface and a receiving Message Interface and add the IDoc type under configuration Message Types. Then add the Message Interface to the Interface Mapping.
The selection for direct import of the IDoc structure under the Interface Mapping (Source Interface/Target Interface) is possible.
Many Thanks in advanced!
Jochen

hi,
for IDOCs (if you don't use a BPM)
you don't need any message interface
so if you have already created a message mapping
you can put the IDOCs directly to your interface mapping
then click on read interfaces
and select your message mapping program
if you want to learn more about IDOCs and XI
have a look at my book:
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi">Mastering IDoc Business Scenarios with SAP XI</a>
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Mapping Error with Sender JDBC- Idoc scenario

Hi Guru's,
I've got a simple asyncronous sender JDBC to Idoc scenario, and I encounter a strange problem with the mapping.
When I test the mapping it works fine, but when I run the scenario, only the first element (a constant) of the Idoc gets mapped, and mapping stops with no errors.
Does someone know where to find the error?
Thanks,
Karst

Hi Karst,
There might be several reasons that you do not see the IDOC structures are not created/mapped:
1. Most of the IDOC structures are optional (minOccrs = 0), so you have to make sure the structure itself (not just the fields within that structure) is mapped to something that does exist in the source data.
2. Make sure your JDBC generated source data does have the right namespace as you used in your mapping. I once had a similar problem, but finally found the source data generated in run time is slightly different from the one used in mapping in terms of namespace.
3. Test your mapping with the source data generated in runtime (you can copy it from SXMB_MONI). Then you may be able to find the problem.
Hope this helps.
Hart

Header Mapping in Idoc scenarios

Similar Messages

Maybe you are looking for