Missing receiver agreement for incoming IDoc

Hi guys,
I transfer IDoc's from a SAP-system to XI to start a ccBPM-process
For that I don't need a receiver agreement.
But why I get always the error message "No receiver agreement found for sender -<SAP-SYSTEM> to receiver -<integration process>" ?
For other IDoc which coming from the same system but starting another process everything is working fine!!!
I don't understand that.
Could somebody help me please? Thanks very much in advance.
Regards, Thomas

Hi,
please can you check in transaction SXI_CACHE if the return code for the IP is 0.
Also, for the Interface that are working is it the same scenario SAP to IP with IDocs on the Outbound?
Regards
Vijaya

Similar Messages

No receiver agreement for the sender "xyz" to receiver "abc" found

in SXMB_MONI i am getting the following error message when the data has been sent from the IDOC
No receiver agreement for the sender "xyz" to receiver "abc" found
I have specified 3 receiver agreements and a Default receiver (in configured receivers)
so in any case, it should pick it as the receiver
but, still I am getting the above error message
any one faced same kind of issue?
regards,
nikhil.

Hi Nikhil,
Correct me if I understood it wrongly.
You need to copy the IDOC xml data and copy it for testing. XSD is the definition for your XML data.
You should not copy the XSD as the input to the Mapping program.
Follow this steps:
- Go to your Mapping Program
- Click on Test tab
- Click on the SRC tab and copy your XML data here not XSD.
Thanks
Srini
Thanks
Srini

Why we r not Creating Sender Agreement For HTTP & IDOc Adapter at Sender .

Hi Buddy's,
Why we r not Creating Sender Agreement For HTTP & IDOc Adapter at Sender .And why we create receiver agreements at receiver side bt not sender agreement at sender side.
Wat Is GLOBAL Container ?, where it will Occur & wat is the functionality of that.

Kumar,
1) XI integrattion server - IS expects the messages in XML format. If you see the HTTP request you will see that we pass all the info contained in the Sender areement in the the HTTP request itself , namely - Message interface, message type and the namespace (along with login parameters). For IDOCs the the IDOC- XML are are sent to the IS (through IDOC port configuration at the source system.
2) When send a message to XI the sender knows that XI system parameters, but when at the reciver end there could be any any system that is reciving the IDOc/HTTTp message. you specify those message through a commumication channel and this channel is associated to a receiver agreement.
3) A Global container is like a place holder for variables. You can set a variable here and access it throughout your mapping and hence the name.
A good example for a gloabal container is a counter to countthe number of records in te target side.
Regards,
Arvind ravindran

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.

I Am not receiving notification for incoming sms

Please help, i am not receiving notification for incoming sms on my curve 8520

Have you tried the proverbial battery pull? If yes then resend your service books.
~diffused
Z10, OS Version 10.2.1.3253
Verizon

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

Getting Receiver Agreement issue in IDOC to File scenario

Hi Gurus,
 Need your help. I'm working on a IDOC to File scenario. I'm using CREMDM.CREMDM04 as outbound Interface & small structure VEND_FILE_IN_MI as Inbound Interface. Though I've configured the receiver Communication Channel as a File Adapter with proper Inbound Interface I'm seeing the message getting failed which is showing CREMDM.CREMDM04 as both Outbound & Inbound interface and pointing a Receiver Agreement issue . The Receiver service is coming Properly, only the Interface is coming wrong as the sender interface. I've checked both Receiver Agreement & Receiver determination and found the Receiver Service, Communication Channel & Interface are perfectly mapped there, I cross checked the same Configurations in IE via SXI_CACHE after full Cache copy.
Error Message:
No receiver agreement found for sender -SAPERP to receiver -IDOC2FileReceiver,urn:sap-com:document:sap:idoc:messages
Error Category : Outbounding
Error ID : CO_TXT_OUTBINDING_NOT_FOUND
My IR design:
Sender:
 Interface : VEND_IDOC_OUT_MI
 Message Type : CREMDM.CREMDM04
Receiver:
 Interface : VEND_FILE_IN_MI
 Message Type : VEND_IN_MT , Data Type VEND_FILE_DT
My ID Config:
1. Sender / Outbound Message: Service Type --> Business System
 Service ---> SAPERP
 Interface--> VEND_IDOC_OUT_MI
 Adapter Type : IDOC
2. Receiver / Inbound Message: Service Type --> Business Service
 Service --> IDOC2FileReceiver
 Interface ---> VEND_FILE_IN_MI
 Adapter Type--> File
3. In Sender Agreement : Specified the Sender Communication Channel
 VEND_IDOC_OUT_Channel
4. In Receiver Agreement Configured the receiver service IDOC2FileReceiver aging sender service SAPERP & Interface VEND_IDOC_OUT_MI.
5. In Interface Determination Specified the Inbound Interface VEND_FILE_IN_MI and Interface Mapping VEND_IDOC_FILE_IMAP
6. In Receiver Agreement specified the receiver communication Channel IDOC2FileChannel against Receiver Service & Interface.
I used the Configuration wizard in my second attempt to make sure the sequence of configuration.
Can anyone help me identifying what's going wrong. I'm very new to XI and basically this is the first assignment I'm working on.
Regards,
Subhadip

Hi Babu,
 In the Inbound data type all the fields have MinOccurance = 0 and MaxOccurances unbounded.
Please find the XSD:
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://adc.com/poc/sample" targetNamespace="http://adc.com/poc/sample">
 <xsd:complexType name="VEND_FILE_DT">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 8f584d80456311dccd680018fe79f69b
 </xsd:appinfo>
 </xsd:annotation>
 <xsd:sequence>
 <xsd:element name="VENDCODE" minOccurs="0" maxOccurs="unbounded">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 a8653cb0390c11dc843000188bd09370
 </xsd:appinfo>
 <xsd:documentation xml:lang="EN">
 Vendor Code
 </xsd:documentation>
 </xsd:annotation>
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:minLength value="0" />
 <xsd:maxLength value="50" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="VENDNAME1" minOccurs="0" maxOccurs="unbounded">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 a8653cb4390c11dc84e800188bd09370
 </xsd:appinfo>
 <xsd:documentation xml:lang="EN">
 Vendor name4
 </xsd:documentation>
 </xsd:annotation>
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:minLength value="0" />
 <xsd:maxLength value="50" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="ORT01" minOccurs="0" maxOccurs="unbounded">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 a8653cb5390c11dcbe3400188bd09370
 </xsd:appinfo>
 <xsd:documentation xml:lang="EN">
 Vendor City
 </xsd:documentation>
 </xsd:annotation>
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:minLength value="0" />
 <xsd:maxLength value="50" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="PFACH" minOccurs="0" maxOccurs="unbounded">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 a8653cb6390c11dc896100188bd09370
 </xsd:appinfo>
 <xsd:documentation xml:lang="EN">
 Vendor PO Box
 </xsd:documentation>
 </xsd:annotation>
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:minLength value="0" />
 <xsd:maxLength value="50" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="STRAS" minOccurs="0" maxOccurs="unbounded">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 4811db0335fd11dc9e9600188bd09370
 </xsd:appinfo>
 <xsd:documentation xml:lang="EN">
 Vendor House No & Street
 </xsd:documentation>
 </xsd:annotation>
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:minLength value="0" />
 <xsd:maxLength value="50" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="PSTLZ" minOccurs="0" maxOccurs="unbounded">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 4811db0435fd11dc98b000188bd09370
 </xsd:appinfo>
 <xsd:documentation xml:lang="EN">
 Vendor Postal Code
 </xsd:documentation>
 </xsd:annotation>
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:minLength value="0" />
 <xsd:maxLength value="50" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="LAND1" minOccurs="0" maxOccurs="unbounded">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 4811db0535fd11dc870500188bd09370
 </xsd:appinfo>
 <xsd:documentation xml:lang="EN">
 Vendor Country
 </xsd:documentation>
 </xsd:annotation>
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:minLength value="0" />
 <xsd:maxLength value="50" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="STCD1" minOccurs="0" maxOccurs="unbounded">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 7ca8d600403b11dcc9bd00188bd09370
 </xsd:appinfo>
 <xsd:documentation xml:lang="EN">
 Tax Number 1
 </xsd:documentation>
 </xsd:annotation>
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:minLength value="0" />
 <xsd:maxLength value="50" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="TELF1" minOccurs="0" maxOccurs="unbounded">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 9abaee7040e611dcce4300188bd09370
 </xsd:appinfo>
 <xsd:documentation xml:lang="EN">
 Telephone number
 </xsd:documentation>
 </xsd:annotation>
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:minLength value="0" />
 <xsd:maxLength value="50" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="STCEG" minOccurs="0" maxOccurs="unbounded">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 9abaee7140e611dc8f3900188bd09370
 </xsd:appinfo>
 <xsd:documentation xml:lang="EN">
 VAT Registration Number
 </xsd:documentation>
 </xsd:annotation>
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:minLength value="0" />
 <xsd:maxLength value="50" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="LIFNR" minOccurs="0" maxOccurs="unbounded">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 9abaee7240e611dccef700188bd09370
 </xsd:appinfo>
 <xsd:documentation xml:lang="EN">
 Account Number of Vendor or Creditor
 </xsd:documentation>
 </xsd:annotation>
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:minLength value="0" />
 <xsd:maxLength value="50" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="ALTKN" minOccurs="0" maxOccurs="unbounded">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 9abaee7340e611dcb3bc00188bd09370
 </xsd:appinfo>
 </xsd:annotation>
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:minLength value="0" />
 <xsd:maxLength value="50" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 </xsd:sequence>
 </xsd:complexType>
</xsd:schema>

Receive data for same IDOC from 2 different scenarios

Hello,
I have already scenario that received xml file and transfer data to IDOC (The IDOC is purchase order).
This scenario works fine.
Now I try to add more scenarios. This scenario takes files from other xml source work with new mapping and transfer data to same IDOC.
The problem is in integration builder u2013
When I try to create receiver agreement the message the message "Object already exists" appear.
How can I solve this issue?
Elad

Hi Elad,
+Now I try to add more scenarios. This scenario takes files from other xml source work with new mapping and transfer data to same IDOC.
The problem is in integration builder u2013
When I try to create receiver agreement the message the message "Object already exists" appear.+
Does this mean that the other xml source is from the same party? If yes, then that party is already configured in your receiver agreement as explained by the error "Object already exists".
If the xml source is from a different party. What you can do is to delete the existing receiver determination. Make a new one and replace the party with an "*", in that way, increasing the parties would only consist of one receiver determination for that particular interface. You would only have to add sender and receiver agreements.
Hope this helps,

Enhancement for Incoming IDOCs

Hi All,
For the incoming Idoc the invoices are getting parked for the success status 53, after checking whether GR is done or not.
My requirement is that the Invoice should be parked even if the IDOC status is Error ie 51.
The Message type is - INVOIC
IDOC type is - INVOIC01
and the process code is INVL
How to go about it ?

Hi Reddy,
Thanx, can u elaborate this..
DP

Receiver Agreement for Integration Process

Dear All
I am facing a strange problem when I am sending a message via proxy to SAP PI whci is then supposed to forward it to a legacy system.
I am using a BPM and am getting an error like no receiver agreement found between the sender SAPECC system and receiver integration process

Hi,
>>>a BPM and am getting an error like no receiver agreement found between the sender SAPECC system and receiver integration process
use the integration directory wizard and create two configurations
- ECC - PI (integration process)
- PI (BPM) - to the legacy
then it will work - this is not an error but lack of configuration
Regards,
Michal Krawczyk

EREC: Multipal IDOC are getting created in receiver system for one IDOC

Hello Experts,
I ran in to one wearied issue in IDOC creation in Receiver system. I am running PFAL in sender system for only Person but 10 IDOC are getting created in receiver system. I don't know why is this happening.
This issue started popping up after we ran RBDAPP01-Inbound Processing of IDocs Ready for Transfer. We ran this to change IDOC to 53 status. Now I don't know what went wrong but Perner distribution is behaving
Appreciate your help.
Regards,
Krishna Bidwai
Losangeles USA.
818 527 0204.

Yes, employee is getting created after adding 0003 into the filter, but can u please answer my another question, i.e. PERNR in sender and receiver system should be same.
So in Receiver system (ECC) do i need to maintain external number range for PERNR?
Thanks

IDoc adapter - Receiver Agreement

For IDoc Adapter, y should the receiver agreement should be created.
I know y sender agreement is not created.
-Naveen.

Hi Naveen,
The Integration Server pipeline converts the received XML to IDoc XML, and then transfers this IDoc XML to the IDoc adapter. The IDoc adapter converts the IDoc XML to native IDoc format and sends the IDoc to the identified receiver system using the standard IDoc interface, this receiver system is identified because you specify it in your receiver agreement. The IDoc adapter can also call external subsystems.
I hope you have understood the need of receiver agreement incase of IDoc adapters...
Regards,
Abhy

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

Receiver Agreement problem in XI

Hi,
The problem is that when the idoc calls adapter in XI, the following error message is thrown(Display XML Message Versions- window, SOAP Header):
com.sap.aii.af.ra.ms.api.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: FP=;TP=;FS=our_sender;TS=our_receiver;AN=WorkCenterMasterData;ANS=our_namespace
I have checked that the Receiver Agreements are configured right, there should not be problem with that. So what could be the problem? We just updated our XI to SP19, could this affect to idoc processing?

Hi,
I have got a couple of times that Receiver agreement not found even though I have receiver agreement. Also I have done some dummy changes and tried out. Also I have stopped and started the receiver communication channel. But it have not worked. Then I have started and stopped the File Adapter but that doesnot worked. I have done all the cache refreshes but the issue is not resolved.
Then finally just restarted the machine and it worked fine. So there are some caches which is not refreshing when we do the cache refreshes. They are only refereshing when we reboot. Can you also try all these steps and if you dont get success then try to bounce the system and check.
---Satish

No receiver found for sender

Hello,
Scenario:
Idoc from R/3 to XI and external partner LI.
The idoc has to be converted to xml and sent by email (Email is a Business Service in XI).
Question:
I got an error "no receiver found for sender" when sending the idoc to XI. In the soapheader of the message I see that the service of the receiver stays empty. How can I fill the service of the receiver in the soap header?
Thanks for your reactions,
Erik van Lisdonk

You have to define a Receiver Determination for the Sender & Interface (sending SAP Business System plus IDoc interface) and specify the Receiver there. Furthermore, you will need an Interface Determination to determine the interface of the outgoing email and the mapping that is required to transform the IDoc to this interface.
Finally you will require a Receiver Agreement for the Service 'Email' that specifies the receiving communication Channel (in your case an Email Channel).
This is all well described in the SAP online help. As a starting point, you can have a look <a href="http://help.sap.com/saphelp_nw04/helpdata/en/19/8dba88b1db634f891622e909565f7a/frameset.htm">here.</a>
regards,
Peter

Missing receiver agreement for incoming IDoc

Similar Messages

Maybe you are looking for