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.

Similar Messages

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.

CO_TXT_OUTBINDING_NOT_FOUND and No receiver agreement found for Sender

Hi,
I had imported an RFC in to two different SWCV. In ID I'm able to see the RFC interface listed under one of the business systems but not in the other. Please help me out with this.
When i tested the scenario i got this error.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="OUTBINDING">CO_TXT_OUTBINDING_NOT_FOUND</SAP:Code>
<SAP:P1>-WB_APDRP_DEV_ISU_200</SAP:P1>
<SAP:P2>-WB_APDRP_DEV_CCC,urn:sap-com:document:sap:rfc:functions.ZPI_CONSUMER_PAYMENT_BILL_DATA</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No receiver agreement found for sender -WB_APDRP_DEV_ISU_200 to receiver -WB_APDRP_DEV_CCC,urn:sap-com:document:sap:rfc:functions.ZPI_CONSUMER_PAYMENT_BILL_DATA</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I cleared the cache using SXI_CACHE and http://Server Name:Port/CPACache/refresh?mode=full and still got this error. Can someone explain me about this..
Regards
Satt

Hi ,
This error generally Comes when aggrements are Not There in ID.
1. Check if all the Objects in ID are activated.
2. First test your Configuration Objects IN ID Only ( Tools - test Configuration )
if this gets Successful , Please tell...
Regards
Prabhat Sharma.

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" ?>
- 
- <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 Error in SXMB_MONI

Hello all,
I am working sample file to file scenario. after compliteion of my scenario i tested through component monitoring. i got following error in sxmb_moni, No receiver agreement found for sender, But i defined receiver agreement and communication channel, can any body suggest me how can i resolve this problem,
Thanks&Regards,
VenkatK

Dear Venkat,
Once check whether you have defined the correct reciver aggrement. If it is fine, Then delete the receiver aggrement and configure new one and activate it. And test the sceanrio once. I think this may solve ur problem. If the problem exists again, then follow the below steps.
In SAP system, Goto SICF tcode.
1.There you just click execute button or F8.
2.Then expand "Default Host" .(This will be in below the Virtuelle hosts/services)
3.Then expand SAP.
4.Then expand XI.In that just activate all the service elements.Just right click and select activate service.
After this, execute your sceanrio. This will solve your problem.
If Helpful reward points.

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

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?

Problem with BPM: no receive step found for message ....

Hello,
I have the follwing problem with a BPM ina PI 7.3 system.
I created a BPM for the following 'process':
We will receive an IDOC from SAP ECC, then call a synchronous webservice and finally send the result back to ECC.
I created my BPM.
Now when I send the IDOC, the interface is triggered but it gets stuck in the queue with message 'No receive step found for message ...'. I get this message when I go to Tx SMQ2 and try to simulate the message
I have already refreshed the CPA cache without result however.
in SXI_CACHE I can find my IP* and the status = '0' ( So i guess this is OK )
I do not use correlations in my BPM.
In my configuration I can find my sender agreement and interface determination towards the service (abstract) which is defined in the receive step of the BPM.
Does anybody have any ideas what can be wrong ?
Thanks,
Erwin
Edited by: Erwin Van Lysebetten on Oct 27, 2011 10:37 AM

Hi Erwin, delete Integration Process in the Directory Integration and import it again.

No Standard Receiver Agreement found

Hi all,
I have configured a scenario between a Business System and Business Service .
As we tried to test the Configuration scenario using Test Configuration Tool, it gives the following error in the Receiver agreement.
Sender Business System : M1S_001 (WS Adapter )
Receiver Business Service : BC_MAIL_RECEIVER (Mail Adapter)
"A problem arose to BC_MAIL_RECEIVER, http://sap.com/xi/AP/FO/Activity/Global.ActivityManagementEmailNotificationOut
during the receiver agreement for the transmitter - M1S_001 to the receiver -:
NO standard agreement found for, M1S_001, BC_MAIL_RECEIVER,
http://sap.com/xi/AP/FO/Activity/Global, ActivityManagementEmailNotificationOut
We have checked in the SXI_CACHE ,Receiver agreement is there but still we are getting the same error.
Please help if anyone faced the same problem and has a solution for it .
Thanks
Ashwin Kumar
Message was edited by:
Ashwin Kumar Dhakne

Hi ,
Everything is fine with the Sender / Receiver agreement .Activated all the ID and IR objects , but it seems a different issue .
if you have any clue please reply as soon as possible.
Thanks

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

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 "<b>No receiver agreement found for sender -<SAP-SYSTEM> to receiver -<integration process>"</b> ?
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

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>

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

Similar Messages

Maybe you are looking for