Receiver Agreement Issue

Hi Experts,
     I am doing the scenario of Flat File to RFC.
     I have craeted DT, MT, SI, for file strucure and imported RFC and used in OM and MM.
     Design has done fine.
     I have created Business service for file adapter and in my system there is already created business system which are using
     in other scenario so i used same BS for RFC channel.
    I have created sender agreement fine and when i tried to create receiver agreemt i am unable to find RFC name over there.
    Can anyone pls guide me how can get RFC name in receiver agreemnt and also i have tried to add RFC in receiver tab of
    business system but i am unable to do that.
    How can acheive this.
Thanks,
Bhaskar

Hi baskar,
ideally you have to assign the software component version in which the RFC is imported to your receiver business system in SLD. Once you done this SWCV assignment to BS in SLD you will be able to see all the interfaces of that SWCV in your business system.
Please check this blog-
/people/shabarish.vijayakumar/blog/2010/05/13/cant-find-interfaces-in-the-associated-business-system
you can also have the workaround mentioned in above post, that is selecting "any" to avoid restriction of BS.
regards,
Francis

Similar Messages

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>

"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

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?

Error: Could not read Header Mapping in Receiver Agreement

Dear SAP experts,
Newly installed SAP G7A PI 7.1(Acceptance box) was already released to customer.
We are doing an initial test (BAT phase), wherein, our end-to-end scenario is, from a EP Portal application ---> G7A PI 7.1 --> Trading Partner via AS2 protocol.
G7A PI is connected to Trading Partner via AS2 protocol.
Currently, our EP Portal application is in-active at the moment, that's why we used 'manual XI submitter', to send a message from G7A PI itself going to Trading Partner.
The message was success in the Integration engine of G7A PI, and the output message was produced.
As the message reached the Adapter Engine layer of G7A PI, we encountered a specific error,
Delivering the message to the application using connection AS2_http://seeburger.com/xi failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: javax.resource.ResourceException: Fatal exception: com.seeburger.xi.connector.queue.TaskBuildException: Could not create CPAObjectMapper: InvocationTargetException caused by Could not read Header Mapping in Receiver Agreement: while trying to invoke the method com.sap.aii.af.service.cpa.Party.getParty() of an object returned from com.sap.aii.af.service.cpa.NormalizationManager.getXIParty(java.lang.String, java.lang.String, java.lang.String), Could not create CPAObjectMapper: InvocationTargetException caused by Could not read Header Mapping in Receiver Agreement: while trying to invoke the method com.sap.aii.af.service.cpa.Party.getParty() of an object returned from com.sap.aii.af.service.cpa.NormalizationManager.getXIParty(java.lang.String, java.lang.String, java.lang.String)
Basically, "Could not create CPAObjectMapper - InvocationTargetException caused by Could not read Header Mapping in Receiver Agreement"
I am thinking, one of the possible cause is that we used manual XI submitter, in G7A PI, instead of the utilizing the actual Sending system (EP Portal application).
Or possible cause is that the AS2 adapter in G7A is not yet stable, thus causing the issue.
We've already done successful connection when we're in GDD PI (Development box) during our SIT phase.
Objects in G7A were mirror of GDD PI.
Kindly advise for your inputs.
Thanks!
Gerberto

Hi,
It seems that the cause of the error is the unstable performance of the PI box, since, this was newly installed and there were patches that were not yet added.
Thanks for the support!
Gerberto

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

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

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

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

XI - restrict access to Communication Channel and Receiver Agreement

Hello Experts,
We are trying to restrict the access to certain communication channels and receiver agreement in our XI system. We are able to restrict access to business service but not the afore mentioned objects.
Our XI system version is 7.0 with SP level 17.
Thanks
Vijaya

We raised an OSS message and found that the issue was due to a missing JAVA patch

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

Material stock received and issued for a given period of time

HOW to get the material stock received and issued for a given period of time including the open orders.
if there is any BAPI Available then please tell me. or give me the table relations thaks.
thanks inadvance

hi friend,
Why don't you try using a TIMER. Try using this code
Timer timer = new Timer((TIMER), new ActionListener()
public void actionPerformed(ActionEvent ae)
// perform your task here...
timer.setInitialDelay(TIMER);
timer.setRepeats(true);
timer.start();
I think this will work fine.
Bye,
Ravi.

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

Receiver Agreement Issue

Similar Messages

Maybe you are looking for