Sender agreement error

hi,
we have two XI systems connected using XI adapter. I am observing a strange behaviour in a case where a file was processed, mapping was done and finally one XI is trying to send it to other. The error being reported is about sender agreement but in the call adapter version of message, in the IE.
Error in sender agreement for party , service XXXXX , interface namespace XXXXX , interface XXXX No sender agreement found for , , , , ,
Any pointers?
Rgds,
Amol

Hi Suraj,
that is not the case. XI1 is aware of what is being done and the fact is actually this has been working fine for last 1.5 yrs but started giving this error all of a sudden.
Do you know if SLD related changes could have such kinda weird impact?
SOAPFault received from Integration Server. ErrorCode/Category: XIServer/IN
here the thread owner mentions that the issue was because of some SLD issue.
R/
Amol

Similar Messages

No suitable sender agreement error (File -- XI -- IDOC R/3)

Hi All,
I am completeing teh 'File --> XI -->IDOC to R/3' scenario.
Have manged to complete teh IR and ID config as per the various threads in SDN.
I am using FCC in the Sender File adapter (which I assume will read the file data and convert to XML data). When this channel is activated, it gives me the error 'No suitable sender agreement found'.
As per various posts in sdn, this scenaruio may not need sender agreement as XI is finally using IDOC adapter to send data to R/3.
Am I correct in assuming that ??
Could you help point any potential missing config.
For your reference:
The comm Channel used to read file data is using File adapter (marked as SENDER/NFS/FCC/Integration server)
Appreciate your feedback.
Thanks
Shirin

Hi,
chk for ALE settings....
Steps for ALE settings:-
Steps for XI
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the R3 system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto IDX1.
     Create a new port.
     Give the port name.
     Give the client number for the R3 system.
     Select the created Rfc Destination.
Step 3)
     Goto IDX2
     Create a new Meta data.
     Give the Idoc type.
     Select the created port.
Steps for R3.
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the XI system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto WE21.
     Create a port under transactional RFC.(R3->XI)
     Designate the RFC destination created in prev step.
Step 3)
     Goto SALE.
     Basic settings->Logical Systems->Define logical system.
     Create two logical systems(one for XI and the other for R3)
     Basic settings->Logical Systems->Assign logical system.
     Assign the R3 logical system to respective client.
Step 4)
     Goto WE20.
     Partner type LS.
     Create two partner profile(one for XI the other for R3).
     Give the outbound or inbound message type based on the direction.
Step 5)
     Not mandatory.
     Goto BD64.
     Click on Create model view.
     Add message type.
Step 6)
     Goto WE19
     Give the basic type and execute.
     fill in the required fields.
     Goto IDOC->edit control records.
     Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
     Click outbound processing.
Step 7)
     Go to SM58
     if there are any messages then there is some error in execution.
     Goto WE02.
     Check the status of the IDOC.
     Goto WE47.
     TO decode the status code.
BD87 to check the status of IDOC.
In case if not authorized then go to the target system and check in SU53, see for the missing object
and assign it to the user.
SAP r3
sm59(status check)(no message)
WE02(status check)
WE05(status check)
BD87(status check)
Xi
IDx5(Idoc check)
SU53(authorization check)
reward points if helpful...
Prashant

XI 3.0 Sender Agreement error during Configuration Wizard

Hi
During the Sender Agreement generation of the Configuration Wizard an error occurs because it takes the value of "" for Receiver Party and Service. This was discuused during the XI252 Session at the San Diego SAP TechEd. The proposed solution was to copy the existing Sender Agreement and remove the "" values. However, no Sender Agreement exists that could be copied. Therefore, I attempted to manually create a Sender Agreement. But now I end up with the following error:
Thrown:
MESSAGE ID: com.sap.aii.ib.bom.landscape.rb_landscape.SLD_***_NOT_FOUND_EX
com.sap.aii.utilxi.swing.framework.PersistenceException: Unable to find an associated SLD element (source element: SAP_BusinessSystem, [CreationClassName, SAP_BusinessSystem, string, Name, XID, string], target element type: SAP_BCSystem)
Has anybody encoutered this also, and more importantly, found a solution?
Frank Deijkers

Hi,
I think you have to add:
Optional: xml.addHeaderLine 0
Obligatory: try to put the ; between quotation marks like:
Hope this helps.
Cheers,
Paul

Using file adapter, got "Sender Agreement not found" error

I used file adapter in my CC and defined all the necessary objects. When I tried to test the configuration and I kept getting "Sender Agreement" error.
Also the chache is cleared too, searched the forum already, couldn't find any clue
Not sure what I did wrong

Hi,
First things first, ensure you have an agreement for each single Communication Channel you have
and that they are correctly associated.
If they are created and associated, you may try the cache refresh with the link:
http://host:j2eeport/CPACache/refresh?mode=full
Kind regards,
Caio Cagnani

Error while publishing Service from Sender Agreement

Hello Experts,
I have Enterprise Service Scenario in which i am publishing Enterprise Service from Sender agreement (using SOAP Sender adapter).
When i am trying to publish this Enterprise Service i am getting below Error.
Adapter Engine XXXX for communication channel XXXX not registered in SLD.
Can someone please help me solve this error?
Thanks,
Hetal

Hi.
Pleas check the following threads
how to check adapter engine was registered in SLD or not?
No Adapter Registered for this channel
Regards
Lucho.

Error While activating Sender agreement having WS Sender Adapter.

Hi all,
I am very new to this technology. I have done Demo example Agency. I configured all the objects. While activating sender agreement having WS adapter as sender adapter, I am gettign the following errors.
1. Field Receiver Communication Party has the value "*"; adapter type WS of communication channel GeneratedSenderChannel_WS does not allow generic key field values
2. Field Receiver Communication Component has the value "*"; adapter type WS of communication channel GeneratedSenderChannel_WS does not allow generic key field values
3. Interface FlightSeatAvailabilityQuery_Out | http://sap.com/xi/XI/Demo/Agency is compatible with SAP NetWeaver 2004 (XI 3.0). Business system GeneratedSenderChannel_WS does not support Web service communication using XI 3.0-compatible interfaces
Can any body solve my problem?? where exactly problem lies??
Regards,
Pavani

hi pavani,
pls see this link.it may help you.
http://****************/Tutorials/XI/XIMainPage.htm
http://209.85.207.104/search?q=cache:fC2GF0rQ6WMJ:www.sap-press.de/download/dateien/1191/sappress_exchange_infrastructure.pdfErrorWhileactivatingSenderagreementhavingWSSenderAdapter%2B+sap&hl=en&ct=clnk&cd=1&gl=us
chk each n every step once again. this may happen due to not checking of generic fields.
thanks
klarthik

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

Regd. error in sender agreement(when to check sender uses virtual receiver)

hi Experts,
I am doing a file( SFTP adapter ) to IDOC scenario.
I got an error :
Couldn't retrieve inbound binding for the given P/S/A values:FP=XYZ;TP=;FS=XXXX;TS=XXXX;AN=XXXXXX;ANS=;
I checked my sender agreement and saw some "*" symbol displayed at the end on SA name.
To quick fix it and remove the star symbol'', i have just created SAgreement again and this time i checked "Sender uses virtual receiver " and revomved thestar symbol '' and saved without mentioning anything there.
When i tested it worked! but i want to know what made it work, is it the right practice.
i did a lilttle search on when to use "sender uses virtual receiver" option.i came to an understanding that it is mainly used to handle multiple input file formats in a single configuration scenario.
one more qns:
What are marketplace adapters,is this error comes when we use adapters which are not inbuilt or bought from external vender.
Regards,
Anika
Edited by: Anika Gulati on Jun 10, 2009 1:23 PM

Here are few ways for it...
SAP Process Integration: When to Use u201CSender Uses Virtual Receiveru201D in a Sender Agreement
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/40cb67f7-6464-2b10-bcb9-8edb9a3569f9
SAP Network Blog: Virtual Receiver - Why do you 'really' need it?
/people/shabarish.vijayakumar/blog/2008/09/16/virtual-receiver--why-do-you-really-need-it
-SM

HTTP response code 500 : Error during Sender Agreement Determination

I am trying a simple file to file scenario and messages are not being received in Integration Server.
Through communication channel monitoring, i have received the below error message.
Error Transmitting the message to
endpoint http://<hostname>:50000/sap/xi/engine?type=entry using
connection File_http://sap.com/xi/XI/System failed, due
to:
com.sap.engine.interfaces.messaging.api.exception.MessagingException:
Received HTTP response code 500 : Error during Sender
Agreement Determination.
Can you please help
Regards
Harish

Hi Harish,
http://<hostname>:50000/sap/xi/engine?type=entry
it should be http://<hostname>:8000/sap/xi/engine?type=entry not 50000 as port It should be your HTTP port...please .make the changes !!
In SXMB_ADM transaction under Integration engine configuration please change the settings to http://<hostname>:8000/sap/xi/engine?type=entry
make sure with your basis team that ur http port is 8000 or 8001 ..as per that make the necessary changes..
Regards,

Sender Agreement Determination Error

Hi Experts,
I am getting an error while posting my message from RWB. the error details is below.
Error While Sending Message: 500 Error during Sender Agreement Determination
It is a HTTP to IDOC scenario so no need to determine the sender comm channel and sender agreement, so I have not done that
but still the error persists. Please help me out. As, everything seems ok to me.
Thanks and regards,
Aniruddha

Hi,
If any ABAP Adapter is tested ideally if u post directly to IE it sholuld not through a error.
Please check if u have any other interface with the same name and same BS, but have 1 sender agrement.
If yes try to rename any1 of the two.
Also refresh the once and try to test it again
Babu

Error: Sender agreement not found, lookup of binding via CPA-CACHE failed.

Hi,
I am doing an RFC to File Scenario in which RFC has to be triggered from CRM system. The TCP/IP connection and communication Channel are working fine. But when i trigger my RFC using the RFC destination following errors occur:
1. The SYSTEM_FALIURE exception comes on CRM side.
2. In adapter monitoring the following error comes on XI side:
Error: Sender agreement not found, lookup of binding via CPA-CACHE failed for Adapter type RFC.
I have also tried the scenario with RFC request as source message and also after J2EE cache refresh but the problem still persists. And one more thing my file adapter (In receiver communication channel) is not working means it is not started. And no message is coming in SXMB_MONI.
Could anyone please help me to resolve this issue.
Regards,
Vinay Yadav

Hi Aaron,
I had the same error and your feedback solved my problem!
Thank you sooo much!!!!
Luciana

Error when sending message: 500 Error during Sender Agreement Determination

Hi,
Am getting this error, while testing to post a data from RWB. can anyone tell me what the problem is? its IDOC to JDBC scenario. i've checked all the config objects in the scenario and they all seem to be fine.
Regards,
Rashmi

Hi Prateek,
i have created sender agreement, as i ran config wizard to create the scenario and it forced me to create a sender agreement.
Seshagiri, i tried using the test tool you mentioned, Interface Mapping step is failing and the error i'm getting is:
During the application mapping com/sap/xi/tf/_outCustomerDetails_DEBMAS_DEBMAS03~ a com.sap.aii.utilxi.misc.api.BaseRuntimeException was thrown: RuntimeException in Message-Mapping transformatio~
any clue?
Regards,
Rashmi

No Objects Found error during Sender agreement in ID

I created all objects, activated in IR and refreshed Cache with SXI_Cache.
Created Scenario in ID.
During Sender agreement creation, I gave Sender Service ( Which doesn't have to be in SLD ). Then Iam trying to pick Interface from drop down. Surprisinglt I cant see any object instead it throws error "No Objects Found" .
What should I do to see the Interfaces from Design?. Any suggestion here ?
Iam doing File to File scenario with Business Service.
Thanks

S T,
from what you've said, you're using Business Services and not Business Systems.
Business Services are simpler (in the sense that you don't need to refer them in SLD and all), but the catch is that they don't have some useful stuff that Business Systems have.
One of these is that, for Business Systems, all the interfaces that are in SWCVs which belong to that BSy are automatically considered as valid interfaces for that BSy.
As for Business Services, you have to define all the interfaces that you want in the BSe, one by one. The good news is that you can use the Message Interfaces of any SWCV of Integration Repository, without having to specifically add the SWCV to the BSe (which can be a pain in the @$$ some times...).
To see and/or include message interfaces for a Business Service, just double click on it on Scenario or Objects tabs of Integration Directory.
Regards,
Henrique.

RWB error: no suitable sender agreement found

Hi Experts,
my scenario is File to proxy...
i am developed end to end scenario
i am using single stack i.e AAE
while checking in RWB it gives the error : no suitable sender agreement found
how to solve this error...
please help me on this..
Thanks&Regards
E.Ravi chandra reddy

Hi Ravi,
Please follow the steps in this blog if you want to send messages to an ICO using RWB
HowTo - Send Test Messages to the Adapter Engine (to an Integrated Configuration)
Hope this helps,
Mark

Error when trying to Display WSDL for Sender Agreement

Hi,
I'm getting an error when trying to display WSDL for a sender agreement. The error message is as follows:
Adapter Engine af.xxx.yyy for communication channel not registered in SLD Unable to find the SLD element (SAP_XIAdapterFramework, [CreationClassName, SAP_XIAdapterFramework, string, Name, af.xxx.yyy, string], [AdapterType, SOAP, string])
The SOAP adapter being used is from the non-central AE. I I immediately checked for inconsistent SLD components per note 746176 but everything is in order there. I tried re-registering manually the non-central AE manually as well.
Anyone else ever had the same error? Any hints much appreciated!

Hi Luqman,
go to the sender channel and replace the Adapter Type.
Select the type as SOAP from SWCV SAP BASIS 7.xx or SAP BASIS 3.0
The channel is referring to a swcv which is not present in esr.
As you might know, the adapter metadata is fetched from ESR/IR, so if the SWCV containing the metadata inside namespace http://sap.com/xi/XI/System etc, is not available then it will throw error.
If you do not want to change the Adapter Type in the channel, import the swcv from SLD to ESR and create/import the respective adapter metadata.
Should resolve your issue.
Cheers!
Souvik

Sender agreement error

Similar Messages

Maybe you are looking for