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

Similar Messages

  • Is it possible to attach two receiver agreement in the same Service?

    when i configure the receiver determination
    there is one receiver service and one inbound interface
    but i want to send it out with two different agreements
    it seems that i cannot use the two agreement
    except i have two service.
    Is there some advice to handle this?
    Thank you in advance

    <i>there is sender service A, and the receiver service B, but i have two receiver agreements
    in the receiver determination, i only can choose one receiver agreement
    which i want to use the two at the same time </i>
    >>
    A is sender and B is receiver. Then why do you need 2 receiver agreements ?
    there will be one sender agreement for your sender A
    there will only be one recv. agreement. ie a combination of sender service + your inbound interface + your receiver service while you create the recv. agreement for your recv. B

  • No Receiver agreement found for Sender

    Hello,
    I have a scenario like this : sending an IDoc from R/3 4.6c to R/3 4.7 through XI 3.0.
    I am struck up with the follwoing Error in SXMB_MONI
    "outbound binding exception: No outbound binding found for , R46, , ENT, urn:sap-com:document:sap:idoc:messages, ORDERS.ORDERS04"
    The Complete TRACE is as follows:
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Technical Routing
      -->
    - <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
      <Trace level="1" type="B" name="IDX_INBOUND_XMB" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">ALE-AUDIT-IDoc-Inbound Handling</Trace>
      <Trace level="1" type="T">IDoc-Inbound-Handling</Trace>
      <Trace level="1" type="T">Syntax-Check-Flag X</Trace>
      <Trace level="1" type="T">IDoc-Tunnel-Flag X</Trace>
      <Trace level="1" type="T">Queueid</Trace>
    - <Trace level="1" type="B" name="IDX_IDOC_TO_XML">
      <Trace level="1" type="T">Get the Metadata for port SAPR46</Trace>
      <Trace level="1" type="T">Convert Segment-Definitions to Types</Trace>
      <Trace level="1" type="T">Make Syntax check of actual Idoc</Trace>
      </Trace>
      <Trace level="1" type="T">Set Receiver Routing-object</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-SET_IDOC" />
      <Trace level="1" type="T">Exit Function IDX_INBOUND_XMB</Trace>
    - <Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-GETBLOBDATA">
      <Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-ITAB_TO_BINARY" />
      </Trace>
      <Trace level="1" type="T">COMMIT is expected by application !</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
      <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
      <Trace level="1" type="T">****************************************************</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">XMB entry processing</Trace>
      <Trace level="1" type="T">system-ID = XI3</Trace>
      <Trace level="1" type="T">client = 800</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = SMART01</Trace>
      <Trace level="1" type="Timestamp">2004-12-27T20:08:46Z CET</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">****************************************************</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Message-GUID = F0EAB201EEA5F74A814EF22C32394FD0</Trace>
      <Trace level="1" type="T">PLNAME = CENTRAL</Trace>
      <Trace level="1" type="T">QOS = EO</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
      <Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
      <Trace level="1" type="T">Queue name : XBTI0009</Trace>
      <Trace level="1" type="T">Generated prefixed queue name = XBTI0009</Trace>
      <Trace level="1" type="T">Schedule message in qRFC environment</Trace>
      <Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Going to persist message</Trace>
      <Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
      <Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
      <Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
      <Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
      <Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
      <Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
      <Trace level="1" type="T">system-ID = XI3</Trace>
      <Trace level="1" type="T">client = 800</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = SMART01</Trace>
      <Trace level="1" type="Timestamp">2004-12-27T20:08:46Z CET</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
      <Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
    - <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
      <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>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
    - <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
      <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>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
      <Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />
    - <!--  ************************************
      -->
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
      <Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">number of receivers: 1</Trace>
      <Trace level="1" type="T">Single-receiver split case</Trace>
      <Trace level="1" type="T">Post-split internal queue name = XBTO____0000</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Persisting single message for post-split handling</Trace>
      <Trace level="1" type="T" />
      <Trace level="1" type="T">Going to persist message + call qRFC now...</Trace>
      <Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
      <Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
      <Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
      <Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
      <Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
      <Trace level="1" type="T">system-ID = XI3</Trace>
      <Trace level="1" type="T">client = 800</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = SMART01</Trace>
      <Trace level="1" type="Timestamp">2004-12-27T20:08:46Z CET</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
      <Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
      <Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>
    - <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
    - <!--  ************************************
      -->
    - <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV">
      <Trace level="1" type="T">No mapping required</Trace>
      </Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
      <Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-GETBLOBDATA" />
      <Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
    - <!--  ************************************
      -->
    - <Trace level="1" type="B" name="CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV">
      <Trace level="1" type="T">processing the outbound binding</Trace>
      <Trace level="1" type="T">search outbound bindings</Trace>
      <Trace level="1" type="T">outbound binding exception: No outbound binding found for , R46, , ENT, urn:sap-com:document:sap:idoc:messages, ORDERS.ORDERS04</Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
      <Trace level="1" type="System_Error">Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      </SAP:Trace>
    I have made neccesary Configurations for the Receiver agreement in the Configuration Directory...
    Anybody could please help me out...
    Regards,
    Romit Arun Shankar

    Hi Frank,
    Many Thanks for your reply.The problem got sorted out and the IDoc(ORDERS04) which i send in SAP 4.6c gets into SAP 4.7 AS ORDERS04 but i have a new problem now....
    I didnt use any mappings until now...but now i have to have the segment E1EDK14 filled up for Sales organisation, Distribution Channel, Division details as well as the material number. These segments will not be filled up when a PO is sent from the source system.These segments has to be filled only in the XI system...Is it ? or is there any other solution for it....
    Now how we can have this segment E1EDK14 which can occur any number of times with constant values for SORG,DV,DC in the mapping process....
    Waiting for ur replies....
    Bye,
    Romit Shankar Arun.
    For this

  • "No receiver agreement found" for BPM ???

    Hi everybody
    I think this could be an issue in the cache. I have a ccBPM and when I am sending the message who starts the BPM to the Integration Engine I got the following error:
    <SAP:Stack>No receiver agreement found for sender -BS_SQL_Database to receiver -IP_ScanningStatus_01,http://xxxx.com/common/scanning.MI_JDBC_Response_Asyn_ABS</SAP:Stack>
    IP_ScanningStatus_01 is an integration process and you do not need a receiver agreement ("not required" in receiver determination) to send a message to an integration process. Two weeks ago the process work and the very strange is, that in sxi_cache it shows the 31.07.2006 as last change/activation, but I did an activation yesterday. A full cache refresh did not change anything and the status of the cache is "up to date". We are on SP14 (:-<)
    Regards Oliver

    Hi Udo
    yes, that is exacly my problem.
    I deleted the corresponding processes in the repository and in the configuration. I recreated the process in the repository under the same name and after that I tried to import the porces in the configuration under the same name, but now I got the following error:
    Unable to transport object Integration Process IP_ScanningStatus_01 | http://xxxx.com/common/scanning (CE_ONESAP_ACETATE_MFG_xx, 1.0 of celanese.com) of type RepBProcess from application REPOSITORY on system REPOSITORY. Detailed information: Attempt to serialize the generic part of object Integration Process IP_ScanningStatus_01 | http://xxx.com/common/scanning failed(serialization problem)
    Any Ideas?
    How can I delete the old process out of cache?
    Regards Oliver

  • No receiver agreement found.

    Hi Experts,
    I am doing one scenario i.e idoc to file .
    I am getting an error that is "no receiver agreement found" in sxmb_moni, but i did the test configuration in ID which is working fine.
    can any one help on this.

    Hi,
    Check the following.
    1. Any cache problems in the ABAP stack and java stack.
    2. Check your receiver whether it is case sensistive.
    3. Check the receiver determination pipeline step in soap header whether the sap receiver anything filled in or blank. If blank, definitely there is an error in your config.
    Since you have tested it in ID, I would assume it would be cache problem.
    Regards
    Krish

  • Error in AEX Itegrated Configuration Testing "No receiver agreement found."

    Hi,
              I am working on PI 7.3, doing a File to Idoc by using the AEX(Advance Adapter Engine Extended). While doing the configuration testing i am getting the below error "
    Problem occurred in receiver agreement for sender -BC_XXXXXXX to receiver -BS_XX5_100,urn:XXXX.com:POC:MasterData:Article:ECC:Sender.SI_OA_POC: No receiver agreement found for , BC_xxxxx, , BS_xx5_100, urn:xxxx.com:POC:MasterData:Article:ECC:Sender, SI_OA_POC."
            I gone through the SDN but not got usefull links. I tryied to recreating whole scenario, Cache refresh, but no luck. Can you pls let me know where is the problem. Do i need to do any additional configuration other than creating RFC in Java stack for AEX?
    Thanks & Regards,
    Dev

    Hi RK,
            Thanks for your reply.
                  Yes i have created the Idoc_AAE channel and assigned this channel in my Outbound Processing tab.
    What do you mean by java channel in Inbound Processing? My sender is File so i created File channel and assigned in the Inbound processing tab.
    @ Raghu,
                I have created the Receiver channel. I no need to create Receiver agreement because i am using the ICO so if i give the Receiver and Inbound interface details that is enough. And one more thing i am doing testing in ID Test confiuration.
    Thanks ,
    Dev

  • No Receiver Agreement found - IDOC RCVPRN = Party

    Hello,
    I have created all the receiver agreements required and they are in the configuration scenario. 
    I have a receiver determination that is using the IDOC vendor number (RCVPRN) to determine the party for delivering purchase orders and another RD with the same config for delivering po changes. 
    In tests my POs are sending successfully and my PO Changes are failing even though they use the same party setup/config.  In SXMB_MONI I can see that the receiver determination for the POs are creating the correct party:
    PO Results:
    <SAP:Party agency="http://sap.com/xi/XI" scheme="XIParty">Ventura</SAP:Party>
    But the PO Changes seem unable to connect the vendor number to the party:
    PO Change Results:
    <SAP:Party agency="http://sap.com/xi/XI" scheme="XIParty">0000557129</SAP:Party>
    In the sample above the party Ventura is set up under the party identifiers as follows:
    Agency:
    http://sap.com/xi/XI
    http://stc.com/pi/SAPR3
    Scheme:
    XIParty
    Vendor
    Name:
    Ventura
    0000557129
    How is it that PI 7.10 is getting the same value in RCVPRN and assigning the Party correctly in one case and incorrectly in another?
    Any ideas?
    Thanks,
    Matt

    Sometimes you just need to walk a way for a day or two...  I rechecked the standard configurations over and over.  But I didn't review the Party Extended selection.  In the Receiver Determination I chose to use RCVPRN to identify the Party but upon further investigation I realized I was using the wrong scheme and agency on the Party extension.
    So my party had the following:
    Agency:
    http://sap.com/xi/XI
    http://stc.com/pi/SAPR3
    Scheme:
    XIParty
    Vendor
    Name:
    Ventura
    0000557129
    My Receiver Determination was not using http://stc.com/pi/SAPR3 Vendor 0000557129 to determine the Party it was attempting to use http://sap.com/xi/SI XIParty Ventura.  So it was unable to find a matchinig party using the Vendor Numbers.
    Thanks for all the help.
    Matt

  • Error in BPM (No receiver agreement found from sender to bpm)

    Hi all
    In a simple bpm scenario, I am getting a error that No receiver agreement found for sender service to bpm integration process.
    What might be the reason?

    your configuration should like this.
    say u are doing File to File using BPM
    File to BPM
    then BPM to File.
    so u need to create RD where sender is fileservice  and receiver is BPM.
    second u hav to create another RD where BPM is sender and Fileserviceis receiver.
    So there should be
    one Sender Ag
    two RD
    two ID
    one RA.
    Thanks
    Farooq.

  • IDOC to FTP File - Error : SAP:Stack No receiver agreement found for send

    Hello Friends,
    I need to configure a senario Idoc to FTP File, Í did required settings in R3 and in PI... , did mapping and configuratino in PI... and when I send my idoc I got error msg in monitor
    <SAP:Stack>No receiver agreement found for sender ,BMG_ASN_File_Component to receiver ,GTN_224,http://adis-bmg.de/asn,SI_BMG_ASN</SAP:Stack>
    I search the fourm but did not got my answer, me just a bit confused...
    In my senario I have having followings:
    1. Bussiness System ( RFT : sender R3 system).  ( I have define a party and make a connection under Idoc Partner )
    2. Bussiness Component ( ZTEST_COMP as on Reciever side is File Server, so I define the reciver as bussiness component )
    3. Communicatin Channel
        File with protocol FTP having communicatin component as my Bussiness Component ( reciver ). there I defied the required info for FTP
    4. Reciever Determination
        Sender:
        - RFT
        - Idoc-Interface
        - urn:sap-com:document:sap:idoc:messages
       Reciever
        communication party  = space
        communicatin component = ZTEST_COMP
        Configure Reciever:
       There I again define the communication component as  ( ZTEST_COMP)
    5. Interface Determination
        -RFT
        - Idoc-Interface
        - urn:sap-com:document:sap:idoc:messages
       Reviever:
        ZTEST_COMP
    and define the mapping which I did in design ( although I have seen some threads where mentioned we dont need maaping in this case ) ?
    6. Reciver agrement
    sender:
    - RFT
    Reviver:
    - ZTEST_COMP
    - SI interface ( SI_BMG_ASN )
    - http://test-etc.de/asn
    and included my CC for file .....
    Now when I send Idoc I got error msg that Reciver is not found : am I dong something wrong ?  do I have to defien a bussiness system instead of Bussiness Component ?
    Pls suggest...

    ( I have define a party and make a connection under Idoc Partner
    Do you really need a party in your communication? Should it not be a partly-less communication.
    In the receiver agreement ensure that you have included the inbound message interface.
    communication party = space
    No need to give any space.
    In the Interface Determination i hope that you have included the receiver meessage interface and then the corresponding Interface Mapping.
    If still not works then make some dummy changes and again activate....correspondingly check the cache status of the ID-objects
    Regards,
    Abhishek.

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

  • Sender and receiver agreement not cerated

    Hi .
    I am creating configuration scenario in ID by importing the integration scenario which i created in the IR.
    I crated communication channel template also and i added it to the integration scenario in connections.
    Query 1?
    do i have to create Communication channels also.....even After creating communication channel template (because it is not seen the ID below communication channel )
    Query 2 ?
    once i transfer this integration scenario from IR to ID and cerate the configuration scenario (sender and receiver agreements are not getting created automatically)peace tell me what is the reason???.
    and how can i resolve this...
    thanks
    shakif

    Hi Mohamed,
    <b>Query 1?</b>
    <i>do i have to create Communication channels also.....even After creating communication channel template</i>
    Yes You have to create as it's just a template that u created in IR. But u can use the same for creating CC.
    Check this link for what's the Diff. B/w CCT in IR and CC in ID
    Re: Communication Channels
    <b>Query 2 ?</b>
    <i>once i transfer this integration scenario from IR to ID and cerate the configuration scenario</i>
    Yes. it will create automatically.
    Just check my posting in Wiki for simple File to IDOC scenario might be u missing something
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/fileToIDOC&
    and check my reply in this thread
    Re: Doubt in transfering integration scenario from IR
    Regards
    Sachin

  • Problem when creating receiver agreement for File to IDOC scenario

    I have done the following :
    1. Created two business systems one for the file system and other for the R3 system and also I created two communication channel, one as sender communication channel and one as receiver communication channel.
    2. Created the receiver determination
    3. Created the interface determination
    4. Created the sender agrement
    5. Now when I was trying to create the receiver agreement I want to assign the receiver communication channel i have created to the receiver agreement but the F4 help gives me no records and I am thus stuck at this point.
    Please suggest me how to proceed forward from here.

    Hi ,
    <i>5. Now when I was trying to create the receiver agreement I want to assign the receiver communication channel i have created to the receiver agreement but the F4 help gives me no records and I am thus stuck at this point.</i>
    Make sure that your created communication channel for reciever is under the respective reciever business system and give the same while creating the reciver agrement.
    sekhar

  • Configuration Error in PI 7.1 Receiver Agreement

    Hi,
    I am facing a problem while testing my interface throught RWB, I am getting below error.
    Error while sending message: com.sap.engine.interfaces.messaging.api.exception.ConfigException: ConfigException in XI protocol handler. Failed to determine a receiver agreement for the given message. Root cause: com.sap.aii.af.service.cpa.impl.exception.CPALookupException: Couldn't retrieve outbound binding for the given P/S/A values:
    I have checked the configuration in ID and its showing green. Also i have tried to re configure complete scenario but still facing same problem.
    point will be rewarded for solution.

    Hi
    Check the Configuration once again .
    Check the Receiver Determination and  Recever agreement .
    Or Else . Test the ID using Test Configuration in tools.

  • 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

  • AS2: Where to specify certificates and keys: CC or Receiver Agreement

    Hello,
    when configuring a AS2 scenario (Proxy - AS2 Receiver) I am wondering about configuration details for certificates.
    In the AS2 receiver configuration channel I can enter:
    SSL Certificates
    Server Certificate (Keystore)
    Private Key for Client Authentification
    In receiver agreement I can enter:
    AS2 Sender Configuration
    Signing Key
    AS2 Receiver Configuration
    EncryptionCertificate
    So I am not sure what to configure where? I am right that transport level security is done in the communication channel, and message level security in the receiver agreement?
    If I use SSL without client authentification in combination with Digital Signature I have to enter Server Certificate of parter in communication channel and Signing Key in Receiver Agreement, right?
    Sorry, maybe this was a little bit confusing.

    Hi,
    you need to configure certificates in receiver agreement.  I did it quite long back.. You need to enter some alias name of certificates over there.
    Once you open the Receiver agreement, you can easily figure it out.
    Thanks
    Inder

Maybe you are looking for

  • Can't see pictures in full screen mode

    This is my new Mac Computer. Some of the pictures can not be viewed except as thumbnails. (When I try to see in full screen mode, there is a quick 1 second view,then a grey screen with an I in the middle and a dotted line surrounding it. There is no

  • Anywhere else I can get the file?

    I purchased the OSX Mountain Lion but suffering in problem. Seems like my internet connection got some problems with App store. Everytime I download I got only 77.2MB file. And couldn't install.... Just wondering is there anywhere else I could get th

  • Layer Mask to hide certain area of  image

    Hi All, I would be grateful if anyone could help me to figure out how to mask only 1 polygon with cat heads because my cat image is so big until it appears on other polygons. Attached below is my screen shot for better understanding. Any tips and hel

  • PO Header Text --- Length more than 132.

    Dear Experts, I hv to read header text (me23n) of po where terms and conditions are defined. I hv used READ_TEXt FM which return the internal table L_LINES. Because I hv to display label also i.e. Header Note  (label) for example , the pr qty is 1000

  • How to embed Typekit code in Muse pages?

    How to embed Typekit code in Muse pages?