SAP PI Error: No standard agreement found

Hi SAP experts,
Hope you can give advise on what is missing/error in my SAP PI configurations, why I am encountering this specific error,
<SAP:AdditionalText>No standard agreement found for , SAPR/3, P_GDDXI, S_HTTP, urn:sap-com:document:sap:idoc:messages, IDOC Type </SAP:AdditionalText>
<SAP:Stack>Problem occurred in receiver agreement for sender -SAPR/3 to receiver P_GDDXI-S_HTTP,urn:sap-com:document:sap:idoc:messages.IDOC Type: No standard agreement found for , SAPR/3, P_GDDXI, S_HTTP, urn:sap-com:document:sap:idoc:messages, IDOC Type</SAP:Stack>
I've configured already the receiver agreement but it seems there is still an error.
Thanks in advance!
Godofredo

You might be using a wrong XML structure for which there is no Integration Directory objects exist especially Receiver Determination.
Make sure your sender agreement is right and hooked up to a correct communication channel.
Try testing this first in the Integration Directory Test tool before sending an actual message?
If you are still having issues then please provide the message flow ex. IDoc to File, Idoc to HTTP etc.

Similar Messages

Error: No standard agreement found for....

Hello,
I've been fighting during hours with this error. I'm using PI 7.1 ehp 1 in a SOAP to RFC scenario and I can't find why this is happening.
In the scenario everything it's ok. If I go to the receiver determination I can see the interface determination, receiver agreement and receiver communication channel but when I test the scenario PI isn't capable to determine the receiver interface (the system determines that the receiver interface is the sender interface)... It doesn't matter if I use a SOAP client or I use the RWB tool to test it directly to the IE.
I've refreshed all the caches, and I created allt the scenario again but the problem is still there...
Can it be a problem with this last PI version?

Thank you Rajesh,
I've tested the configuration in ID and it's much more clear there. The problem is that the system didn't found any interface determination... and then it uses the sender interface as receiver interface... But it has no sense because if I go to the receiver determination object I can see how PI detects the interface determination for that receiver...
<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 "RECEIVER" </Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) "RECEIVER" "OUT INTERFACE" </Trace>
<Trace level="2" type="T">...valid InbIf without Condition: "IN INTERFACE" </Trace>
<Trace level="2" type="T">Number of receiving Interfaces:1 </Trace>
<Trace level="1" type="E">CL_ID_PLSRV-ENTER_PLSRV</Trace>

No standard agreement found for BS_A ,, BS_B

Hi Experts,
We are getting a very common error " No standard agreement found for BS_A ,, BS_B https://abc.com,SIOA_forcast,,,
There interface was succsfully executing few days back.
Here are some information abount the interafce.
1) JMS to IDOC
2) IDoc control record mapping
When i checked the pipe line steps in MONI , starngely it is showing
SAME SENDER interface name SIOA_forcast in sender and receiver interface . And thus it got failed in reciver agreent. I could not see the Idoc and IDoc namespace
I have searched in SDN but, did not get any clear picture
I have done the following
1) checked SXI_CAHCE and cahche instance if every object.
All objects are up -to-date
2) Deleted and recreated ID objects
3) Check the interfaces in message mapping , operation mapping , interface determination etc..., all are looking fine.
DId anyone faced this issue before.
I have asked basis for a full refresh , but i am not confident wheather that will solve the issue or not.
Please provide your valuable input and let me understand the issue.

Hi Sam
Was anything changed during last few days?
PI is not able to determine receiver interface and keeps sender inteface details. For this reason it can't find receiver agreement.
Check that your interface determination object is correct and perform a full cache refresh.
Also copy your message payload from SXMB_MONI and use the test tool (Tools -> Test configuration) in ID.
Regards,
Giuseppe

Error while executing a JDBC to Idoc scenario : No standard agreement found

Hello SAP PI Gurus,
I am having a JDBC to idoc Scenario .And the interface is running at 10 min of duration.
<SAP:AdditionalText>No standard agreement found for ,
BS_EXT_CTBSREPDB, , BS_ERPQAS_QE1_320, http://XYZ.com/FI/FI_FI_01/Charges, FIDCC2</SAP:AdditionalText>.
While i test the configuration...i get an error in reciever agreement as mentioned above.
Can you pls help me in resolving this issue.
Regards,
Ravi

Hi,
I think the problem is with namespace....for IDOC the namespace will be "urn:sap-com:document:sap:idoc:messages"...but in your case it is different.....i.e http:....etc.....please check whether you 've used the same IDOC withe above mentioned namespace in all the configuration objects like interface determination, receiveragreement etc.....
Thanks
Priyanka

No standard agreement found Error.

Hi i am working on File to IDOC scenario and i am getting the below error.
"No standard agreement found for , D_XXX_YY, B_XXX, ECC1800".
I deleted all my Config objects and recreated and reactivated.cache is up to date but still no use.
When i test this in ID test confguration.It works fine. we are using parties here.
could some one please help me out.really appreacite your help.
Regards

Hi,
try creating your receiver agreement with virtual communication channels.
You can also try re-activating your receiver and interface determination objects. Also check if you are using correct (same) namespace for receiver and interface determination objects. You might want to have all objects in same namespace.
For IDoc scenarios, Imported IDoc itself acts as a interface. So you need not create a message interface on the IDoc side. This interface would correspond to standard sap namespace.
Do a complete cache refresh.
If this did not help, check the SAP Note: 832965
Also, check this link : /people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi helps you to troubleshoot File-IDOC scenarios.
Thanks,

Outbound binding exception: No standard agreement found

Hi ,
I have 2 asynchronous FILE to IDOC scenarios. These scenario work fine most of the times but strangely some times it gives the error OUTBOUND_BINDING_NOT_FOUND (outbound binding exception: No standard agreement found for , <out_BS>, , <IN_BS>, <http://ns>, <Query_Out>)
sxmb_moni shows that in the errored messages, the interface names in the sender and receiver side are same
i.e. Outbound interface "Query_Out", but in the successful messages the interface name in the sender is "Query_Out" and in receiver is "FIDCC1_FIDCCP02".
The Scenarios were working until today when i tested it again, no changes were made to it. Every other Scenario is working except these 2 interfaces housing the same logic.
I have checked for errors in cache but none were there.
Thanks in advance.
Amith

Hi Amith
Check this link and find out where you have done mistake
http://help.sap.com/saphelp_nw04/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
Regards
Dheeraj

No standard agreement found for receiver

HI,
I am doing File to Multiple files (3 )bases on Identifer
Each and Every File of receiver has Different Communication component.
I am doing Multimapping to split based on the condition.
1) Created 1 Sender Agreement
2) Created 1 Receiver Determination Given all the receiver component (3) in configured receivers
3) Created 1 Interface Determination , called the Operation mapping which contains all the 3 Service interfaces including Multimapping.
4) Created 3 Receiver communication channels.
But I am getting Following error
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="OUTBINDING">CO_TXT_OUTBINDING_ERROR</SAP:Code>
<SAP:P1>-TR</SAP:P1>
<SAP:P2>-XXX_60,http://TEST</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>No standard agreement found for , TR, , XXX_60, http://test,
Thanks in advance

Hi Sap pixi ,
Try to create the scenario like this ,
1) Create 1 Sender Agreement
2) Create 1 Receiver Determinationwith all the receiver components (3) in configured receivers along with the conditions.
3) Create 3 Interface Determination .
4)3 mappings ,3 Operation mapping , 3 Service interfaces .
4) Create 3 Receiver communication channels.
Try the above scenario as the multi-mapping is not working for you,I tried the same for two different communication components, with no conditions in receiver determination and its working fine .
Regards,
Lavanya.B

Send Message SOAP to Proxy failed - No standard agreement found for

Hello to all,
we have a SOAP to Proxy scenario.
The Service Interface have 6 Operations.
When I implement 2 Operation it works fine. Now I have implemented all Operation.
When I send a request I get following Error:
I have checked the Interface determination. It is ok. I have Sender, Receiver and all Operations.
Where could be the error?
Please help us.
Thanks and regards
Martin
Edited by: Martin Weidauer on Nov 9, 2010 4:45 PM
Edited by: Martin Weidauer on Nov 9, 2010 4:47 PM

Martin,
Please perform the following..
1) Please go thru this link.
Re: Error CO_TXT_OUTBINDING_ERROR in SXMB_MONI
2) Perform a full CPACache refresh using PIDIRUSER.
http://XiHost:Port/CPACache/refresh?mode=full
3) Kindly check Note No.'s in service market place ::
1284103, 1278244, 1278273 .
Just perform and let me know...
Regards
Veeru

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

Error 1311 source not found

All Basis,
Any idea on this,
When tyring to open a Excel from SAP, the Error 1311 source not found throws up.

hello folks,
I have Windows XP home Firefox v1.0.6.
removed old java in Add/Remove programs.
cleared the "Temporary Internet Files" folder that contained C:\Documents and Settings\Greg\Local Settings\Temporary Internet Files\Content.IE5.
tried to load jre-1_5_0_04-windows-i586-p-iftw.exe for the third time, and the install still hangs up.
J2SE Runtime Environment 5.0 Update Installer Information : Error 1311. Scource file not found: C:\Documents and Settings\Greg\Local Settings\Temporary Internet Files\Content.IE5\2XFKL4VY\je150000[1].cab. Verify that the file exists and that you can access it.
and,
Error 1311. Scource file not found: C:\Documents and Settings\Greg\Local Settings\Temporary Internet Files\Content.IE5\EEIDPHGA\jp150040[1].cab. Verify that the file exists and that you can access it.
here's the thing, I cannot surf to "Content.IE5" folder in my "Local Settings\Temporary Internet Files" folder, but I can plug in the directory in the address bar of Windows Explorer & see the "Content.IE5" folder.
I do not see "je150000[1].cab" or "je150000[1].cab" in there.
Am I using the wrong program to fresh install Java for Firefox in XP?
Is there something wrong with my operating system?
monitoring this thread.....
thanx.

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.

ERROR in PI : No sender agreement found for , , , , ,

Hello everybody,
i'm working with SAP PI 7.1
it's a new installation.
I created the first easy interface JDBC-Pi-File.
when i activate the CC i don't see any message in SXMB_MONI but in RWM i see the messages in Waiting status and when i look inside i see the follow error:
SOAPFAULT received from Integration Server. ErrorCode/Category: XIServer/INBOUND_BINDING_ERROR; Params: BS_CSIS_DEV, http://xxxx.com/test, SI_DB2SP_DOCUMENTS_AA_02; AdditionalText: null; ApplicationFaultMessage: null; ErrorStack: Error in sender agreement for party , service BS_CSIS_DEV, interface namespace http://xxx.com/test interface SI_DB2SP_DOCUMENTS_AA_02 No sender agreement found for , , , , ,
1-Configuration is ok. I create all steps and sender Agreement exist
2-end point http://yyyyy:50100/sap/xi/engine?type=entry is correct and the same in SLD and sxmb_adm -> Integration Engine Configuration
3-i suppose 50100 port is correct because when i try to use 8010 port i have a different error.
4- i alreadi used CPA cache refresh and SXI_CACHE.
Any suggestion?
thanks

after 20 minuts i retry.
Now the error message is changed:
Transmitting the message to endpoint http://yyyyyy:8010/sap/xi/engine?type=entry using connection JDBC_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error transmitting the message over HTTP. Reason: java.net.ConnectException: Connection refused.
Edited by: apederiva on Aug 25, 2010 11:35 AM

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.

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

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.

SAP PI Error: No standard agreement found

Similar Messages

Maybe you are looking for