Sender & Receiver Agreement

Hello Folks,
I'm a beginner to SAP PI. Can some one explain me what is the need of sender and receiver agreement in the integration process....what are the critical aspects that can be handled using these agreements....
Thank you
Vittal

Hi Vittal,
The sender and receiver agreement defines how PI system will collaborate the third party system. And it is used to specify the adapter used for connecting with the respective systems.
Please find below mentioned link for further help.
http://help.sap.com/saphelp_nw04/helpdata/en/5d/112d20f6ce6c46ba66afb98d278fbd/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/b1/f29e7a56e18a439984a3c6630951d2/content.htm

Similar Messages

Principal Propagation - no checkbox in Sender/Receiver agreement

My SAP XI version is NW04s SP11 (upgraded from sp09). I activated Principal Propagation in RSXMB_CONFIG_PP (it's status is green) and made the settings according this blog:/people/alexander.bundschuh/blog/2007/01/16/principal-propagation-in-sap-xi , but there is no Principal Propagation checkbox in Sender/Receiver agreement of Integration Directory.
Can anybody help me?
SAPXIAF11P_1-10003482.SCA and SAPXIAFC11P_5-10003481.SCA were deployed, ABAP kernel patch level is 95.

Did you import the SAP Basis Component in your IR after the Upgarede corresponding to your SP level in your IR?
Regards
Bhavesh

Error : Receiver agreement not found

Hi all,
My scenario is RFC to JDBC.
Its showing the below error, when 'I try to send data through test configuration after configuring ESR and ID part.
Receiver Agreement
Runtime error
Problem occurred in receiver agreement for sender -SAP_BL_ISU to receiver -RFC_To_JDBC_Async_R_SQL_bllmstest,urn:sap-com:document:sap:rfc:functions.ZTEST_TIPS_DOI1: No standard agreement found for , SAP_BL_ISU, , RFC_To_JDBC_Async_R_SQL_bllmstest, urn:sap-com:document:sap:rfc:functions, ZTEST_TIPS_DOI1
<Trace level="1" type="B">CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV</Trace>
<Trace level="2" type="T">O U T B O U N D - B I N D I N G </Trace>
<Trace level="2" type="T"> Cache Content is up to date </Trace>
<Trace level="2" type="T">determine OUTBOUND BINDING for: </Trace>
<Trace level="2" type="T">-SAP_BL_ISU </Trace>
<Trace level="2" type="T">-RFC_To_JDBC_Async_R_SQL_bllmstest </Trace>
<Trace level="2" type="T">urn:sap-com:document:sap:rfc:functions.ZTEST_TIPS_DOI1 </Trace>
<Trace level="1" type="T">error with outbound binding. </Trace>
<Trace level="1" type="T">No standard agreement found for , SAP_BL_ISU, , RFC_To_JDBC_Async_R_SQL_bllmstest, urn:sap-com:document:sap:rfc:functions, ZTEST_TIPS_DOI1 </Trace> <Trace level="1" type="E">CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV</Trace>
please suggest me...

Hi,
This is configuration issue, please check the ESR sender/Receiver interfaces and the associated
Sender / Receiver agreement and the associated communication channels are configured correctly.
Try to test the configuration using Test configuration / send a test message from RWB to this interface.
If the configuration is correct and you are facing the same issue. try to delete the ID configuration and recreate it.
Before re-creating the configuration, do cache refresh.
Regards
Bhargava Krishna

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

Problems while sending/receiving IDOCs

Hi,
I am trying to store IDOC data to MS access database. I created a scenario and able to activate that successfully, but after sending IDOC from SAP, in SXMB_MONI I can see status as "Message Processed succesfully" flag, and acknowledgement status as "Still awaiting acknowledgement" and data is not stored in database. Anybody having any idea about this problem.
Another problem what I am facing is, when sending an XML file from a file server to SAP(through XI), I am getting status as " Scheduled for outbound processing". Receiver determination, Interface determination, Sender & receiver agreements all are present and correct. Any help?

Hi,
Check what chris has said....Also in SXMB_MONI check the status of the message on the outbound side(by scrolling to the right)...This will say whether it has been transferred to the Adapter Engine....
For the second problem, pls check whether all your queues are registered. All queues can be registed from transaction SXMB_ADM...then doublwe click on "Manage Queues"...and choose the register queues and execute...
Thanks,
Renjith

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

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.

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,
Query 1?
do i have to create Communication channels also.....even After creating communication channel template
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
Query 2 ?
once i transfer this integration scenario from IR to ID and cerate the configuration scenario
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

Receiver and Interface Determination, Sender and Receiver Agreement

Hi Experts,
Could you please tell me, what Receiver Determination, Interface Determination, Sender Agreement and Receiver Agreement we have to use for the below blog.
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1403 [original link is broken] [original link is broken] [original link is broken]
Regards
Sara

Hi Sara,
WS->BP
Receiver Determination: Sender IF, Sender NS, Sender BS determine the BP
Interface Determination: Sender IF, Sender NS, Sender BS determine your start msg IF (abstr IF) and IF mapping
Sender Agreement: SOAP sender channel for that Sender IF, Sender NS, Sender BS
Receiver Agreement: not reqired
BP->DB
Receiver Determination: BP IF (abstr), BP IF NS, BP determine the 3rd party BS (DB)
Interface Determination: BP IF (abstr), BP IF NS, BP determine Inbound-IF and IF mapping
Sender Agreement: not reqired
Receiver Agreement: JDBC receiver channel for that Inbound IF, NS and 3rd party BS
BP->File
Receiver Determination: BP IF (abstr), BP IF NS, BP determine the 3rd party BS (File)
Interface Determination: BP IF (abstr), BP IF NS, BP determine Inbound-IF and IF mapping
Sender Agreement: not required
Receiver Agreement: File receiver channel for that Inbound IF, NS and 3rd party BS
Regards,
Udo

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

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.

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

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

How does B2B in SOA SUite 11g identify sender/receiver of inbound document?

Hi All,
I am checking basic B2B features - custom document protocol. I have defined docuement definition, trading partner, agreement, channels as per guide. When I copy (manually) a sample xml payload (complaint to definition xsd and identification expression), it gives error as the sender could not be identified (receiver is taken as the host as I am putting the file over host's listening channel).
So question is - how does B2B identify sender, receiver and match the incoming message payload to identify the agreement?
Thanks in advance.
regards, sibendu

Hi Sibendu,
First of all, let me direct you to the right forum, Oracle Integration B2B forum - Integration - B2B
Now coming to your question,
how does B2B identify sender, receiver and match the incoming message payload to identify the agreement?For each and every document, exchange and transport protocol there are certain fields (generally message headers) on the basis of which B2B identifies the sender and receiver. As far as identifying the incoming message payload is concerned, in each and every document definition we define some UNIQUE selection criteria to identify a document. For XML documents, it is the X-Path of some node(and/or it's value) and for non-xml documents, it is the start and end position of some element (and/or it's value) in the document.
You may get faster and better answer in Oracle B2B forum, for the questions related to Oracle B2B (10g/11g).
Regards,
Anuj

Sender & Receiver Agreement

Similar Messages

Maybe you are looking for