Failed to determine a receiver agreement

Hi All
I am using PI 7.1. My current scenario is from a RFC Sender to a JDBC Receiver. I have configured the scenario on PI. When I execute the SE38 program which calls the RFC I get an error that "Sender Agreement Not Found". When I execute from RWB using the Test Message I get an error that "Failed to determine a receiver agreement". When I test the configuration at Integration Builder, it diagrammatically displays that the entire configuration is fine with the Sender and Receiver Agreement.
I have removed the "*" from the Sender Communication Channel and Sender Agreement. Despite I get the "Sender Agreement Not Found" error when execute from SE38.
Could anyone please help me on this issue? I am not able to move on with this persistent error.
Thank you.

>
John jeyaraj wrote:
> Hi Aashish
>
> I am not using ABAP proxies as Sender. I am using RFC Sender Communication Channel. Also I have created the required RFC Destinations on the application server as Registered Programs. Whenever I fire the RFC through the SE38 program, I am able to trace the error from RWB. This means that the communication with the PI server is established, I suppose.
Yes, Exactly. That means Your communication between Program and SAP PI is establish and they are communicating,
Let us know the error message in SXI_Monitor, so that we can help you further.
Regards
Aashish Sinha

Similar Messages

Tables for Receiver Determination and Receiver agreement

Hello Experts,
Is anyone aware if there is a some table which gets updated whenever we create a receiver determination or receiver agreement in PI. If possible can you guys give me the table names.
Thanks in advance,
~ Suraj

hi Suraj,
SAP XI is built having two stack the abap and the java stack. Its not all that correct that only cache info resides on the java stack and nothing on the abap stack.... Its like black box and the internal workings are hidden from end users ... only sap would be able to tell you. As someone in this thread has given his point of view that only cache info is stored on the java stack which may be correct but how much so is open to debate. I wonder whether you have played around with the table that you come across with the transaction sara.
Suggestions are most welcome
Regards
joel

Configuration Error in PI 7.1 Receiver Agreement

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

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

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

Failed to determine receiver - Async to Sync communication

Hello,
I have a setup in which IDoc flows from R/3 to XI to destination through HTTP. Being Async to Sync a BPM is put in place. This flow runs fine.
We tried adding one more receiver to the existing setup. The sender is the same as in the above mentioned flow. The receiver determination is failing. A separate receiver determination was configured for the second flow. The error message is "NO_RECEIVER_CASE_BE". We checked the entire configuration settings. Everything appears fine. Why is the receiver determination failing ? None of the solutions existing provides an answer that works. Any clues ?
Early answers would be much appreciated.
Thanks in advance.
Warm Regards,
IS / Siva

In the same receiver determination, with no condition, just add an additional receiver. Create interface determination and receiver agreement for the corresponding receiver. Activate all objects and try again with your input.
Hope this works..
Regards,
Parvathy

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?

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

Receiver agreement not visible in receiver determination( ID)

Hi,
I could not see receiver agreement in receiver determination in ID.
Even i could see my receiver agreement in ID.
Give some inputs to solve this issue.
Thanks & regards,
Ruban

Hi,
I did as u said..even though i could not see receiver agreement in receiver determination.
One more issue is in interface determination, if i select type of interface determination as Enhanced i could able to select name and Name space in inbound interface and interface mapping.
If i select type of interface determination as standard i could not see name , name space for inbound interface and interface mapping.
Thanks
Ruban

Receiver Agreement and Interface determination

Hi
I have an input file that generates two output files. The two output files go to the same interface. One output file will have header and the other will have details. I want to kow how many receiver determination, interface determination, sender agreement and receiver agreements we need to create
Regards

Hi Ajith,
As perception, I understand that you would like to like to split the input file into two as Header and Details. For this requirement, you should need Integration Directory (Configuration) as below:
1. Need to Two Receiver agreements.
2. One Receiver determination.
3. One sender agreement.
4. One Interface determination ( Type: Enhanced)
Thanks,

Receiver agreement fails in Proxy to Mail Scenario ( B2B)

Hi All,
I have a proxy to mail Scenario. It is an B2B scenario. I communicate on the sender side via a Business System and on the receiver via a Business Service.
This is a Proxy to mail scenario. I test via the test configuration tool. The sender agreement, Receiver detemination, Interface detemination runs fine.
The failure occurs in the receiver agreement. It fails saying " NO standard agreement found" .
I did the the following checks
1. Checked whether the Agreement is active
2. Checked the name of the Communication component and Interface. all ran well
What could be the issue. Why can sender agreement fail.
Can anyone please help.
Thanks
Abhishek

Hi All,
I have a proxy to mail Scenario. It is an B2B scenario. I communicate on the sender side via a Business System and on the receiver via a Business Service.
This is a Proxy to mail scenario. I test via the test configuration tool. The sender agreement, Receiver detemination, Interface detemination runs fine.
The failure occurs in the receiver agreement. It fails saying " NO standard agreement found" .
I did the the following checks
1. Checked whether the Agreement is active
2. Checked the name of the Communication component and Interface. all ran well
What could be the issue. Why can sender agreement fail.
Can anyone please help.
Thanks
Abhishek

1 Receiver Agreement, multiple Receiver Determinations

Hi Gurus,
Is this possible?
1 Receiver Agreement, multiple Receiver Determinations
I can't create a new receiver agreement because the object already exists.
I can't see the receiver agreement that was created before in the new receiver determination that i created.

Hi,
yes you can have one receiver agrement for multiple Receiver determinations..
let me explain one example.
Sender System File(BC_FILE) and receiver System SAP ECC.
suppose you have multiple secnerions between File System to SAP ECC,but mutiple scenarions sending data to ECC in the form of ORDERS IDoc, in this case you will crearte N number of receiver determinations but only one receiver agrement.
i hope i got you query correcttly.
Regards,
Raj

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

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>

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

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

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

Failed to determine a receiver agreement

Similar Messages

Maybe you are looking for