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.

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.?

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.

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

Problem in creating Receiver Agreement using Integration Directory API

Hello Experts,
We are developing a scenario where we are creating "REceiver Agreement" through Integration Directory API.
This requires certain parameters like Sender component, Interface, Communication Channel & Namespace to be set in the code.The required Communication Channel & Components already exist in Integration Directory .
Our concern is that we are not able to retreive this Communication Channel's ID through the code in order to set it as a parameter for Receiver Agreement generation.
Can anybody pls advice??
Thanks in advance,
Suraj.

Hi Stefan,
We tried using query on communication channel, but could not do it as we could not get a method which accepts name of communication channel as parameter.
We used "CommunicationChannelQueryIn" related methods in the API.
But still could not retreive the Communication Channel ID of an existing Communication Channel.
Please help.

Dynamic MailAdapter Receiver Agreement using S/Mime

Hi,
I need some help at an specific problem with the SAP XI Mail Adapter.
First a little scenario description:
In our business there are 10 Email addresses and we have 250 businesspartners.
We want to send Emails in a secure way (S/Mime), but we wouldnt configure hundreds of Receiver agreements to specify the exact Certificates which must be used to send an signed and encrypted Mail form A to B.
See
http://s5.directupload.net/file/d/1336/xgadwfu5_jpg.htm
Note:
Schlüsselspeicher = Keystore
Schlüsselspeichereintrag = Certificate-Alias
Signierte Mail-Zertifikate hinzufügen = Add Certifiacate to Mail.
Verschlüsselungsalgorithmus = encryption Algorithm
And now my Question :
Is there any possibility to dynamically set the Configuration settings marked in the picture with a red arrow ?

Any Ideas like an own Adapter, Adapter Modulte, Dynamic Configuration ?

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

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

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

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

Multi Mapping using condition & Dynamic Receiver determination – Used XSLT Mapping

Dear Experts,
     I am struggling to identify an error on the Technical Routing. Firstly according to my scenario, I receive an XML file with multiple PO's and I have to split the file to 2 different target messages. and also according to the source payload I have to send the file to 2 different receivers. first receiver is ABAP Proxy to the back end system and the 2nd one is to a file location. I have used XSLT to split the message into 2 target message type and I have used a XSLT mapping for receiver determination. Does any one have any idea of what I am doing wrong.
Note: some time I will only be able to fill in on target message.
I have attached my XSLT message split mapping with this post, please let me know if you have further question.
Your help is more appreciated.
Advance Thanks,
Pradeep
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:sap="http://www.sap.com/sapxsl" version="1.0">
<xsl:variable name="vFlag"/>
<xsl:variable name="vPONUM" select="POTRACKING/Lines[1]/PONumber"/>
<xsl:template match="/">
    <ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">
      <ns0:Message1>
        <ns1:MT_Tracking xmlns:ns1="http://www.findel-education.co.uk/axapta">
          <xsl:for-each select="POTRACKING/Lines">
            <sap:call-external class="ZCL_VNAP_OBJECTS" method="CHECK_PO_EXIST">
              <sap:callvalue param="IP_EBELN" select="string(PONumber)"/>
              <sap:callvariable name="vFlag" param="EP_BOLEAN" type="string"/>
            </sap:call-external>
            <xsl:if test="$vFlag = 0">
              <Lines>
                <DDate>
                  <xsl:value-of select="DespatchDate"/>
                </DDate>
                <PONumber>
                  <xsl:value-of select="PONumber"/>
                </PONumber>
                <POLine>
                  <xsl:value-of select="POLine"/>
                </POLine>
                <QTY>
                  <xsl:value-of select="Quantity"/>
                </QTY>
                <VendorMaterial>
                  <xsl:value-of select="VendorMaterialNumber"/>
                </VendorMaterial>
                <AccountRef>
                  <xsl:value-of select="AccountReference"/>
                </AccountRef>
                <ConsignNumber>
                  <xsl:value-of select="ConsignmentNumber"/>
                </ConsignNumber>
                <CarrierURL>
                  <xsl:value-of select="CarrierURL"/>
                </CarrierURL>
                <ConsignURL>
                  <xsl:value-of select="ConsignmentURL"/>
                </ConsignURL>
              </Lines>
            </xsl:if>
          </xsl:for-each>
        </ns1:MT_Tracking>
      </ns0:Message1>
      <ns0:Message2>
        <ns2:MT_Tracking xmlns:ns2="http://www.findel-education.co.uk/ecc/ax/po/ftp">
          <xsl:for-each select="POTRACKING/Lines">
            <sap:call-external class="ZCL_VNAP_OBJECTS" method="CHECK_PO_EXIST">
              <sap:callvalue param="IP_EBELN" select="string(PONumber)"/>
              <sap:callvariable name="vFlag" param="EP_BOLEAN" type="string"/>
            </sap:call-external>
            <xsl:if test="$vFlag = 1">
              <Lines>
                <DDate>
                  <xsl:value-of select="DespatchDate"/>
                </DDate>
                <PONumber>
                  <xsl:value-of select="PONumber"/>
                </PONumber>
                <POLine>
                  <xsl:value-of select="POLine"/>
                </POLine>
                <QTY>
                  <xsl:value-of select="Quantity"/>
                </QTY>
                <VendorMaterial>
                  <xsl:value-of select="VendorMaterialNumber"/>
                </VendorMaterial>
                <AccountRef>
                  <xsl:value-of select="AccountReference"/>
                </AccountRef>
                <ConsignNumber>
                  <xsl:value-of select="ConsignmentNumber"/>
                </ConsignNumber>
                <CarrierURL>
                  <xsl:value-of select="CarrierURL"/>
                </CarrierURL>
                <ConsignURL>
                  <xsl:value-of select="ConsignmentURL"/>
                </ConsignURL>
              </Lines>
            </xsl:if>
          </xsl:for-each>
        </ns2:MT_Tracking>
      </ns0:Message2>
    </ns0:Messages>
</xsl:template>
</xsl:stylesheet>

Hi Hareesh,
Please find my determination in the XSLT below, I am using enhanced receiver determination.
<xsl:transform xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:sap="http://www.sap.com/sapxsl" xmlns:p1="http://sap.com/xi/XI/System" xmlns:ns="urn:sap-com:document:sap:idoc:messages" version="1.0">
<xsl:variable name="vFlag"/>
<xsl:variable name="vAX" select="0"/>
<xsl:variable name="vSAP" select="0"/>
<xsl:variable name="vBoth" select="0"/>

<xsl:template match="/">
    <xsl:for-each select="POTRACKING/Lines">
      <sap:call-external class="ZCL_VNAP_OBJECTS" method="CHECK_PO_EXIST">
        <sap:callvalue param="IP_EBELN" select="string(PONumber)"/>
        <sap:callvariable name="vFlag" param="EP_BOLEAN" type="string"/>
      </sap:call-external>
      <xsl:choose>
        <xsl:when test="$vFlag = 0">
          
          <xsl:variable name="vAX" select="$vAX + 1"/>
        </xsl:when>
        <xsl:when test="$vFlag = 1">
          
          <xsl:variable name="vSAP" select="$vSAP + 1"/>
        </xsl:when>
      </xsl:choose>
    </xsl:for-each>
    <xsl:if test="$vSAP > 0">
      <xsl:if test="$vAX > 0">
        <xsl:variable name="vBoth" select="$vBoth + 1"/>
        <xsl:variable name="vSAP" select="0"/>
        <xsl:variable name="vAX" select="0"/>
      </xsl:if>
    </xsl:if>
    <xsl:if test="$vBoth > 0">
      <p1:Receivers>
        <Receiver>
          <Service>
            <xsl:text>BS_AXAPTA_TST</xsl:text>
          </Service>
        </Receiver>
        <Receiver>
          <Service>
            <xsl:text>BS_ECQCLNT300</xsl:text>
          </Service>
        </Receiver>
      </p1:Receivers>
    </xsl:if>
    <xsl:if test="$vAX > 0">
      <p1:Receivers>
        <Receiver>
          <Service>
            <xsl:text>BS_AXAPTA_TST</xsl:text>
          </Service>
        </Receiver>
      </p1:Receivers>
    </xsl:if>
    <xsl:if test="$vSAP > 0">
      <p1:Receivers>
        <Receiver>
          <Service>
            <xsl:text>BS_ECQCLNT300</xsl:text>
          </Service>
        </Receiver>
      </p1:Receivers>
    </xsl:if>
</xsl:template>
</xsl:transform>

Receiver determintation using Abap Mapping

Hi,
I configured a scenario in which I'm using extended receiver determination to determine the receiver of an incoming message. (The reason for this is that there is only one XI system and two ECC systems - DEV and QAS. By means of the setting in a customizing table it can be determined whether the message is sent to DEV or QAS. The message can't be sent to both systems because it is a synchronous interface). The receiver determination calls an Interface Mapping which has target interface Receiver Determination. I made an Abap Mapping program in which the customize table is read and the output message is formed as follows (according to the structure of the Receivers message):
      lrf_output_document = lrf_ixml_factory->create_document( ).
      lrf_receivers = lrf_output_document->create_simple_element( name = 'Receivers'
                                                                  parent = lrf_output_document ).
      lrf_receiver = lrf_output_document->create_simple_element( name = 'Receiver'
                                                                  parent = lrf_receivers ).
      lrf_element   = lrf_output_document->create_simple_element( name = 'Party'
                                                                  value = ' '
                                                                  parent = lrf_receiver ).
      lrf_element->set_attribute( name = 'agency'
                                             value = ' ' ).
      lrf_element->set_attribute( name = 'scheme'
                                            value = ' ' ).
      lrf_element   = lrf_output_document->create_simple_element( name = 'Service'
                                                    value = 'DEV'
                                                    parent = lrf_receiver ).
To fill the RESULT field a stream factory is instantiated and a XSTRING is created. When I send a message to the system, the receiver determination dumps: Error when parsing receiver listLength of XML document 129 Error when parsing receiver listLength of XML Document 129 System expected the element 'Receivers'
Looks like the XSTRING has not got the right structure and can not be parsed into the Receivers message. However, when I create a CSTRING, the message looks OK. I also changed the encoding (Codepage 4103).
When I replace the Abap mapping with a message mapping, the receiver determination works OK. However, in that case it is not possible to read the customizing table. I really need the Abap mapping.
Has anyone ever filled the Receivers massage by means of Abap mapping. Any feedback will be appreciated!

Hi,
there is a easier way - totally based on my blogs
create an abap mapping that will feed the dynamicconfiguration in ABAP (with z "Z" namespace) - similar thing shown in my blog
/people/michal.krawczyk2/blog/2007/04/26/xipi-throwing-generic-exceptions-from-any-type-of-mapping
and you don't need to create the XML in ABAP mapping just parse it, fill DC and send the same source to the target
(so you don't change the XML)
then add a message mapping to your interface mapping in which you will only use dynamicconfig value
to populate the receiver segment
nice and clean way
Regards,
Michal Krawczyk

HEADER MAPPING in RECEIVER AGREEMENT use.?

Similar Messages

Maybe you are looking for