No Sender Agreement (Specific)

Dear All
I have gone through SDN forums and found a number of threads where this problem is discussed.
Most of the answers include
Re - activate ID objects : not always helpful
Delete and recreate ID objects : not possible in production environments
Cache refresh: does not solve problem most of the time.
I have very specific question regarding the problem
What exactly is the reason for a problem saying "No Sender Agreement Found"
Instead of solution let us have some inputs on the cause of this problem so that we can concentrate on the root cause for this.

Hi,
on what I understand you trigger EXTERNALLY a sender Communication Channel.
To solve your issue, for each triggering, your scheduler tool has to do a : STOP-START-<Tempo>-STOP of your sender CC.
The first STOP, it's because before to do a START, you cannot be in status "Started". So you have to stop It.
See in CC monitoring, when CC is started, you cannot select the "START" button but only the "STOP" button.
Note: I think the reson why you have your error message (sorry I have not my doc to check the exact SAP message).
The Last STOP, it's just a "security". If you do not do it and if your J2EE server have been to be restarted, then all CC which are in status "START" are started... on so the CC are run at a non-desired time. To avoid that, I suggest you to do the last STOP, for instance, with a <Tempo> of 60 / 90s after the START... It's depend of the connection to your legacy... let time to PI to pick-up the file before to do the last STOP.
I did these three steps since several years, and it works perfectly.
Regards.
Mickael

Similar Messages

Why we dont need sender agreement and comm channel in IDOC to file scenario

Hi,
there are 2 queries:
first query :
Scenario is "Idoc to file transfer"
why we dont need sender agreement and communication channel for IDOC to file ,while we do need
both of these for "File to RFC "
Answer : which i got is because IDOC sits at ABAP stack but same is valid for RFC also.
Then why For "IDOC to file" we dont need that.
Second query:
Also when i did scenario for File1-RFC-File2 scenario using BPM i have created a interface
between XI-RFC synchronous to send data which we got from file1 in XI to RFC importing parameter
and getting data from RFC back to File2.
Here in IDOC to file scenario why we dont need any interfface for IDOC-XI Asynchronous.
Regards,
Mayank
Edited by: mayank verdia on Jan 13, 2009 11:49 AM
Edited by: mayank verdia on Jan 13, 2009 11:50 AM

Dear All,
For file to idoc scenario is there any possibility to get line items details or xml details i.e the segments and its related field details using reference id, transaction id or interface name or message id in SAP PI 7.0. I know we need to click each and every message in sxi_monitor and look for details.
For SAP(R3 System) I can create a report and set the job for specific time period so automatically it throws the details(like reference no, document date, invoice no from) in ftp path as .csv file. The same ftp path is maintained in program.
I wanted to check FTP--->PI postings and I have set the job at r3 system it is working fine and Im monitoring it too.
Now the end to end scenario is FTP--->PI--->ECC(R3 system). Please help.Many Thanks.

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.

Sender agreements on high availability setup

Hi
We have XI and ERP exchanging some messages. Our ERP system has been switched to high availability setup.
As for one scenarion in XI: ERP is sender and there is ONE sender agreement that can use ONE communication channel (RFC).
In that communication channel, "RFC Server Parameter" is configured for one of the app servers. "RFC Metadata Repository Peremeters" are set to point to the load balancer.
What happens is that this scenarion can be started only from this app server that is configured in the communication channel.
How to enable that both ERP app servers could be th senders for this scenario?
I am missing something obious...
Thanks,
Heiko

This seems strange for me too. But if I set the RFC Message server and Metadata server to use the same system, the connection will not work.
It seems that there are two possible ways:
- change communication channel so that it would not be app server specific. Tried but don't seem to figure out how this should be configured.
- add multiple sender agreements. XI dos not allow multiple sender agreements... requires different receiver... but there is no receiver at all.
Any ideas?
Heiko

Sender Agreement - Virtual Receiver - what is it for?

Hi guys!
When u create Sender agreement - what is Virtual receiver good for? What is the difference when u use it and not?
Thank you for answer!
Olian

Hi ! Olian
For more Information about Sender Agreement - Virtual Receiver -
refer these below links .....
the following link has something regarding Virtual receiver, check this one.
virtual receiver???
configure virtual receiver in cross system
If you want to create a receiver-dependent receiver determination, select the Sender Uses Virtual Receiver checkbox in the create dialog.
Check out this Rec Det steps.
http://help.sap.com/saphelp_nw04/helpdata/en/26/5ccd3bb4560f01e10000000a11402f/frameset.htm
Also u can chk out this blog where he hav shown the screen shot.
/people/james.guanzon/blog/2006/09/09/how-to-support-industry-standards-in-xi-part-iii-of-iii--config-test
Also, http://help.sap.com/saphelp_nw70/helpdata/en/b1/f29e7a56e18a439984a3c6630951d2/frameset.htm
/people/michal.krawczyk2/blog/2005/11/21/xi-idoc-to-idoc-tunneling--how-fast-and-easy-can-you-get
http://help.sap.com/saphelp_nw04/helpdata/en/26/5ccd3bb4560f01e10000000a11402f/content.htm
o enter specific values for the receiver, select the checkbox Sender Uses Virtual Receiver
http://help.sap.com/saphelp_nw2004s/helpdata/en/da/7a2f41b239a831e10000000a1550b0/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/b1/f29e7a56e18a439984a3c6630951d2/frameset.htm
you want to create a receiver-dependent receiver determination, select the Sender Uses Virtual Receiver checkbox in the create dialog.
Check out this Rec Det steps.
http://help.sap.com/saphelp_nw04/helpdata/en/26/5ccd3bb4560f01e10000000a11402f/frameset.htm
Also u can chk out this blog where he hav shown the screen shot.
/people/james.guanzon/blog/2006/09/09/how-to-support-industry-standards-in-xi-part-iii-of-iii--config-test
Also, http://help.sap.com/saphelp_nw70/helpdata/en/b1/f29e7a56e18a439984a3c6630951d2/frameset.htm
A real world scenario
/people/william.li/blog/2006/09/08/how-to-send-any-data-even-binary-through-xi-without-using-the-integration-repository
http://help.sap.com/saphelp_nw04/helpdata/en/b1/f29e7a56e18a439984a3c6630951d2/frameset.htm
Questions are welcome here!!
Also mark helpful answers by rewarding points 
Thanks,
Abhishek Agrahari

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

Sender agreement not updated in XI cache after commit

Hi all,
somehow none of my created sender agreements appears in the XI cache after commit. I also did a complete refresh of the XI chache.
Any ideas?
Thanks!
Denis

Hmm,
I have created sender agreements for SOAP channels, this would explain why I could not see the agreements...
Actually I am wondering why the 'test configuration' tool in the ID brings up an 'java.io.IOException' in the receiver determination. Prior to that the sender agreement lookup fails. So I thought it's the XI Cache...
I restarted the J2EE engine but the problem remains.
Any other ideas?
Thanks so far!

What's the usage for WSDL of sender agreement?

Hi gurus,
Our scenarios are using soap sender adpater, and we find in PI 7.11 there is a functionality to display the wsdl of sender agreement.
It seems xmlspy can create soap request based on the url format of wsdl, but we can't send the soap request to PI as it gave the error message as below " Couldn't retrieve inbound binding for the given P/S/A values: FP=;TP=;FS=null;TS=;AN=null;ANS=null;".
Do we have to use the "TOOLS->display wsdl" menu to get the wsdl file to local and then provide it to 3rd party system? If so, we have to export wsdl again whenever data structure changes.
Thanks in advance.

HI,
Do we have to use the "TOOLS->display wsdl" menu to get the wsdl file to local and then provide it to 3rd party system? If so, we have to export wsdl again whenever data structure changes.
---->yes ,we have to export wsdl again whenever data structure changes.
and
we have 2 approaches for generating WSDL FILE
1. in sender Agreement
2. from memu bar-> tools
but we have to generate WSDL file Through Menu bar "TOOLS" because there is chance to provide url and sender details after change the Structure..,..
thanks,

Sender Agreements for HTTPS

Hi
I am aware that there that there is no Sender Agreement necessary for sender Http scenario, maybe a silly question but why in that case is there a Sender option on the HTTP communication channel ?. Also for HTTPS if there is no sender agreement (hence no Communication Channel) then where can HTTPS be assigned as the Security Level on the channel, i.e. the "Security Check for Incoming Messages option".
Thanks
Damien

Hi!
According to my knowledge in XI there the HTTP Sender service is in disable and eventhough u can create in XI. but now in Latest version like PI 7.1 the service is enable
In mostly in some real time projects there are some requirements like they need some security purposes in that cases mostly they need a Sender agreement mandatory for security purpose.
Inorder to satisfy these requirements they are configuring HTTP sender and hence Sender agreement and but they are selecting as HTTPS protocol and while selecting HTTPS protocol kindly note one point that your network Firewall settings needs to be in open and they needs to all the flow of messages.
I hope now you are free from confusion.
Regards:
Amar Srinivas Eli

Sender Agreement not needed when in httpclient to file scenario.

Hi,
I will like to understand why in the httpclient to file scenario, a sender agreement is not needed?
Thanks.

HI
Integrattion server - IS expects the messages in XML format. If you see the HTTP request you will see that we pass all the info contained in the Sender areement in the the HTTP request itself , namely - Message interface, message type and the namespace (along with login parameters). For IDOCs the the IDOC- XML are are sent to the IS (through IDOC port configuration at the source system.
When send a message to XI the sender knows that XI system parameters, but when at the reciver end there could be any any system that is reciving the IDOc/HTTTp message. you specify those message through a commumication channel and this channel is associated to a receiver agreement.
For more information you can search in sdn.
Regards
Goli Sridhar

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

No sender agreement configured in the XI Integration Directory

Hi,
I am using MPA(MML) message format in XI scenario. My scenarios are R3->XI->Marketplace and Marketplace->XI->R3. The first scenario works fine with no problems where as when i try to post MML message from marketplace to XI system, i am seeing the "No sender agreement configured in the XI Integration Directory for the given message header:SenderParty=xxxx; ReceiverParty=; SenderService=xxxxx; ReceiverSerivce=xxx; Interface=xxxx; InterfaceNamespace=xxx;". I have created sender agreement for this secenario, and moreover i haven't this sender agreement in the xi cache. Please let me know if i am missing anything in the configuration.
Thanks & Regards
Sruj

Thanks a lot for replies, but i have tried all these options but no luck. Does it need any additional configurtion to resolve this issue, i dont think this is cache issue, if that is the case after all steps which i have done should have fixed it. Please post your comments.
Once again thanks a lot for everyone.
Thanks & Regards,
Sruj
Message was edited by: Srujan Gogineni

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

No Sender Agreement (Specific)

Similar Messages

Maybe you are looking for