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.

Similar Messages

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

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.

When we will use HEADER MAPPINGS in RECEIVER AGREEMENTS?

Hi,
HEADER MAPPINGS appeared when we create RECEIVER AGREEMENTS,So when we will use this option.

Hi Ramana,
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.
chk this link
http://help.sap.com/saphelp_nw04/helpdata/en/b2/1f17419b24f06fe10000000a1550b0/frameset.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c09b775e-e56e-2910-1187-d8eba09c7a4a
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660
Regrads
Sampath

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!!!!

Receiver agreement

Hi all,
what is the use of HEADER MAPPING in receiver agreement>?

hi keerthi,
Header mapping
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.
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 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
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
pls refer following link also
http://help.sap.com/saphelp_nw04/helpdata/en/5d/112d20f6ce6c46ba66afb98d278fbd/content.htm
Regards,
Mandeep Virk
Reward if helpful

Hard to understand 'header mapping' and 'principal propagation' in soap

when i use soap adapter i meet two interesting field, 'header mapping' and 'principal propagation '
so does any one of you may tell me
what does it mean by header mapping in receiver agreement?
what does it mean by principal propagation properies in sender agreement ?
Thanks a lot!!!
Jeff

Hi,
Please, familiarize yourself with this doc: [How To Use the J2EE SOAP Adapter|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40611dd6-e66e-2910-f383-e80fb44f9cd4]. Especially, the chapter 4.4.
Regards,
Jakub

Receiver agreement - IDOC

hi all.
i have a simple question.
Why i must define a sender service at header mapping in receiver agreement??
if the sender service is not defined, i get the error, cannnot conver sender service to an ALE logical system.
Rgds
RP

You don't need to define your system META4 as an ABAP System.
You can create it as a Business System (3rd Party) in your SLD or as a Business Service in your ID depending you need.
What adpaters are you using ?
If you use IDOC for R/3 you can choose from where the sender is taken :
http://help.sap.com/saphelp_nw70/helpdata/en/96/791c42375d5033e10000000a155106/frameset.htm
Regards,
Chris

Receiver Agreement : Header Mapping

Hi,
Does anyone know how to retreive the information contained in the Header Mapping of the Receiver Agreement? I want to be able to extract the information using Java and plug it in a field when the mapping is executed.
Thanks
Steeve

Hi,
Thanks but that wasn't exacly my question.There is a section in the receiver Agreement where it is written Header Mapping. Undern it, there are 4 check box (sender party, sender service, receiver party and receiver service). I Added information in the one marked receiver service but I can't retreive it with Java. I keep getting the one I defined in the service field under receiver.
I don't know if I explained it better this time.
Thanks,
Steeve

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,
<i>MESCOD
MESCFT
TEST
EXPRSS
STD
STDVRS
STDMES
SNDSAD
SNDLAD
RCVSAD
RCVLAD
REFINT
REFGRP
REFMES
STATUS
DIRECT
OUTMOD
CREDAT
CRETIM</i>
Take sender from payload and take receiver from payload, are used to change the value of SNPRN and RCVPRN.
Regards,
Bhavesh

SAP PI Party setup IDoc - HTTP: no receiver agreement found

Hi,
We have setup SAP IDoc -> SAP PI --> HTTP with 2 parties, as described in the the 'HOW..TO Sample IDoc - XI scenario's' case 7:
For the clarity of the example, the sender at our side is 'AAA', and the receiver side is 'BBB'.
1. Sender Party
Agency -
Scheme -
Name
http://sap/com/xi/XI -
XIParty -
PA_AAA
BS_BBB    -
ALE#LI -
0000100581
2. Receiver Party
Agency -
Scheme -
Name
http://sap/com/xi/XI -
XIParty -
PA_BBB
AD2_200 (SAP system) -
ALE#KU -
DE217560
The other components in XI are as follows:
3. Business component: PA_BBB | BS_BBB (party and Business System)
4. Receiver determination: sender AD2_200, receiver party: PA_BBB, receiver component: BS_BBB
5. Receiver agreement: sender AD2_200, receiver party: PA_BBB, receiver component: BS_BBB
    Header mapping: sender comm party: PA_AAA, receiver comm party: PA_BBB
6. Communication channel (HTTP): CC_HTTP_RCV_BBB
    Identifiers: sender agency: BS_BBB ALE#LI, receiver agency: BS_BBB ALE#KU
When we send an IDoc with SNDPRN=AD2_200, RCVPRN=DE217560, RCVPRT=KU, SAPXI doesn't seem to find receiver determination, iinterface determination and receiver agreement
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Start with given receiver PA_BBB -</Trace>
<Trace level="2" type="T">Using Receiver Determination 00000000000000000000000000000000</Trace>
<Trace level="1" type="T">No Relation found - accept given Receivers.</Trace>
<SAP:AdditionalText>No receiver agreement found for , AD2_200, PA_BBB, , urn:sap- com:document:sap:idoc:messages,
Can someone explain why these parties have to be indicated in all these different places (the party descriptions, the receiver agreement, the communication channel), and why the receive determination with receiver party PA_BBB is not found, although it is created and refreshed in the cache ?
Regards,
Jan Macken

I am also facing same issue when using 2 parties. Could you please let me know if you got solution for this?

Integrated Configuration- Problem occurred in receiver agreement for sender

Hi , I am using AAE in PI 7.1 and it is proxy to file scenrios.
When Ia m doing testing in Integration Directory in test configuration its giving me this error .
Problem occurred in receiver agreement for sender -<ECCBUSINESSSYSTEM> to receiver -BS_D_EPS,http://abc.com/sap/pi/HR/Qualifications.Qualifications_Async_Out: No receiver agreement found for , -<ECCBUSINESSSYSTEM> , BS_D_EPS, http://abc.com/sap/pi/HR/Qualifications, Qualifications_Async_Out
( here it should take interface Qualifications_Async_In, but logs says it is pointing to outbound interface)
here when I am going in to trace logs then it seems that are not able to understand the receiver interface . rather then it is taking sender inface in logs..
In trace logs . I am getting
Receiver Determination
<Not found>
<Trace level="1" type="B">CL_RD_PLSRV-ENTER_PLSRV</Trace>
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N </Trace>
<Trace level="1" type="T"> Cache Content is up to date </Trace>
<Trace level="2" type="T">Start with given receiver - BS_D_EPS </Trace>
<Trace level="2" type="T">Using Receiver Determination 00000000000000000000000000000000 </Trace>
<Trace level="1" type="T">No Relation found - accept given Receivers. </Trace>
<Trace level="2" type="T">...extracting Receiver from Header: BS_D_EPS </Trace>
<Trace level="2" type="T">Classic Receiver Determination via Rules. </Trace>
<Trace level="3" type="T">...create rule engine </Trace>
<Trace level="2" type="T">No Receiver found behaviour: 0 </Trace>
<Trace level="2" type="T">Number of Receivers:1 </Trace>
<Trace level="1" type="E">CL_RD_PLSRV-ENTER_PLSRV</Trace>
Interface Determination
<Not found>
<Trace level="1" type="B">CL_ID_PLSRV-ENTER_PLSRV</Trace>
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N </Trace>
<Trace level="1" type="T"> Cache Content is up to date </Trace>
<Trace level="1" type="T">...There is no Interface Determination configured for receiver party and receiver service BS_D_EPS </Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) BS_D_EPS Qualifications_Async_Out </Trace>
<Trace level="2" type="T">...valid InbIf without Condition: Qualifications_Async_Out </Trace>
<Trace level="2" type="T">Number of receiving Interfaces:1 </Trace>
<Trace level="1" type="E">CL_ID_PLSRV-ENTER_PLSRV</Trace>
Operation Mapping
<Not found>
<Trace level="1" type="B">CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV</Trace>
<Trace level="2" type="T">......attachment XI_Context not found </Trace>
<Trace level="3" type="T">Mapping already defined in interface determination </Trace>
<Trace level="1" type="T">No mapping configured </Trace>
<Trace level="1" type="E">CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV</Trace>
I have developed the other integrated configuration scenario and this is working fine .
please let me know how can I troubleshoot it

I am using sender as Soap and receiver as File adapter.
here the problem is that while going for interface deteremination and receiver agreement it is calling to Outbound interface .
It should call the inbound interface. I put all the details correctly and deleted all the objects and crated again for both Ir and Id..
I put the name of inbound interface in configuration but while executing its calling outbound interface.

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

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 <b>same</b> 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

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

Header Mapping in Receiver agreement.?

Similar Messages

Maybe you are looking for