Adapter don't need Sender Agreement

Hi, Can some one Answer me with the reasons/clarification.
What adapters dont need Sender Agreement? and Why?
a) HTTP, IDOC.
b) IDOC, RFC
c) IDOC, JMS
d) JDBC, JMS
Chandra

Hi Chandra,
yes now u know that the ans is (a)
to add above......
In a sender agreement, you define how the message of a sender is to be transformed so that it can be processed by the Integration Engine.
We specify details like the sender interface, sender service, sender namespace in sender agreement.
--> so that when the message comes in integration engine, XI should be able to identify the receiver based on the details we identified in the sender agreement.
In the case of IDOC & HTTP details about the sender like sender service, interface, namespace are part of the payload, ie header details are present.
IDOC and HTTP adapter are the only adapters that sits on the ABAP stack (Rest all adapters r on Java stack). So when messages are posted to these adapters, the message directly goes to the Integration Server. They are pushed from the sender to be recognized directly in Integration server.
There is no need to create an IDoc sender Communication Channel for XI. Instead, the backend SAP system must be configure to send the IDoc to XI.
For HTTP adapter it is not required to have sender agreement. As this adapter is part of Integration Server. SO the message will be automatically put into XI pipeline.
This thread will clearify your doubt:
Re: idoc and http adapters
Also chk out the threads below:
IDOC and HTTP Adapters - sender agreement ??
Question on sender agreement
Hope this was informative to you...
kanan

Similar Messages

Why we do not need sender agreement for Mail and SOAP adapter

Hi SDN,
I know, we do not need sender agreement for IDOC ,HTTP,XI adapters. As these three adapters will run in Integration engine of the abap stack.
In our scenario if sender is other than IDOC or HTTP or XI .
By Refering Sivamni's blog.
/people/siva.maranani/blog/2005/05/25/understanding-message-flow-in-xi
message will be pickedup by communication channel with the help of sender agreement and prepare XI message header by performing cpa cache lookup. then message will go to module processor etc.
In our scenario if sender is IDOC or HTTP or XI .
As these 3 adapters are run in Integration engine.
Doubt 1:
how the integration engine will create the xi message header like sender interface sender system name etc...
Doubt 2:
I believe SOAP and mail adapter will run in adapter engine.but i came to know that we do not need sender agreement and sender comm channel for these two adapters too...then how the XI message header will create...
Please do correct me if i am wrong
and throw some light on the same..
Appreciate your help....
Regards,
Reehan.

Reehan,
Thanks for pointing me to that link. Guess I was wrong .,But,let me try to put to you why you need a sender agreement for a Sender SOAP Adapter,
1. In the sender SOAP adapter , the Sender Interface and the Interface Namespace as provided in the fields Default Interface Name and InterfaceNamespace. The Name of the Sender Service is provided in the WSDL when you ceate the WSDL in the Integration Directory. So, as all details are available in either the Sender SOAP adapter or in the WSDL url you do not need a Sender Agreement. It is not obligatory but you can always create the Sender Agreement.
2. For the mail adapter , if you select the option XIPAYLOAD, you will have the option to mention the Interface Name and Interface Namespace under XI Parameters and so in this case as once again the details provided in the sender agreement are available in the Sender Adapter itself the sender agreement is not needed for the mail adapter when you have select option XIPAYLOAD.
If you have selected XIALL then you need a sender agreement.
Regards
Bhavesh

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

Sender Agreement is not Active

Hello,
I am developing a JMS to File and File to JDBC scenarios on XI service pack 9.
All the necessary objects and configuration are created and activated . When i activated them,evertying got activated but i don,t see sender agreement from the SXI_CACHE even its associated communication channel is not visible from the adapter minitor.
I can see all onjects from SXI_CACHE , only sender agreement is missing.
Any suggestions for this problem?
Best Regards,
Chandra

Chandra,
Click on the Sender Agreemt and then Click on the Sender Business Syste, with which you have associated the Sender Agrement. You should then be able to see the same if it active.
Also, if there is no sender agreement for your adapter, then the adapter in Comm Channel Monitoring would give you the error log , "No sender agreement found" . Are you getting this?
Regards
Bhavesh

Question on sender agreement

Why doesnt IDOC and HTTP have a sender agreement?

Hi Srinivas,
     Even XI Adapter also doesn't need sender agreement and Sender Communication Channel like HTTP & IDOC Adapters.Because these adapters stay in ABAP STACK
    Remaining other adapers like RFC,FILE,JMS,BC,etc we need to create sender agreement and sender communication channel also including with other creations like receiver agreement, interface determination, receiver determination. Because these adapters stay in JAVA STACK.
http://help.sap.com/saphelp_nw70/helpdata/en/45/17be55967e4574e10000000a114a6b/frameset.htm
    If you have any doubts, feel free to ask me.
Thanks & Regards
Srikanth
plz award points if it is helpful to u

No Sender Agreement Configured in Dual Stack( PI 7.31)

Hi All,
I am configuring a simple file to file scenario.
Initially i Have created the scenario without ICO and It worked fine.Later I changed this ( ie, I have deleted sender agreement,Interface determination etc)
and used ICO to configure.
But I am getting the below error.
If the configuration is based on ICO,I don't think sender agreement is required.Please help.
Regards,
Tibin Joseph

Hi Tibin,
Please, if your issue is solved close the thread according this How to close a discussion and why
In this way further SCN members can figure out how to resolve their problems easier.
Regards.

Sender agreement & communication channel not needed in case of IDOC adapter

Hello everyone ,
I am new to xi , as far as i know a communication channel cannot be created in ID when using IDOC adapter , the answer for this question is like , the idoc adapter resides on the integration server & not part of j2ee AF .
Can some one explain me in the terms of a laymen , its not clear to me.
Thanks & Regards,
Reena.

Hi ! Reena
IDOC adapter resides on Integration server, so Integration engine takes care of the conversion format from IDOC to XML, hence there is no need for sender Adapter .Also since its residing on Integration server you can directly post the message in the Integration engine.
well lemme explain a little bit,the main reason for sender agreement is to associate namespace with the sender adapter,now when we shoot IDOC from R/3 it already contains its standard SAP namespace so no need of sender agreement.
now comes the sender CC,main use of sender CC is to identify the sending system and the adapter.the IDOC header contains details of all the this,so again there is no need for sender CC
loook at this thread discuss the same
Re: Why we r not Creating Sender Agreement For HTTP & IDOc Adapter at Sende
Re: why HTTP & IDOC adapter do not require sender communication channel?
Thanks!!
Questions are welcome here!!
Also mark helpful answers by rewarding points
Regards
Abhishek Agrahari

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

Need Help in Creating adapter module for SFTP Sender in NWDS

Hi experts,
I have a scenario where i should write an adapter module for SFTP sender in NWDS.. need your help in achieving this..

Hello,
>>i have followed the procedure of FTP but, adapter is not picking the file
Make sure u have written proper expression to pick file.
>>do we have any different adapter parameters for SFTP... the input file is .csv..
I don't think there are any specific parameters needed for SFTP (but in case u are reading file name in AM then u might have to adjust SFTP namespace)
Thanks
Amit Srivastava

Problems using access control in sender agreement for SOAP adapter 7.1

I am trying to use Access Control Lists to restrict user access to web services/interfaces which are exposed via PI. This can be configured via the Integration Builder Directory using the u201CAssigned Usersu201D tab of both Communication Components (Business System) and Sender Agreements.
The configuration is via the above mentioned components. However, I understand that itu2019s the adapters which at runtime are responsible for actually applying these checks.
I have been having problems getting the access control to work using a setup involving a SOAP adapter of type SAP BASIS 7.10.
The symptom of the problem is that although the access control works as expected at the Business System level, any settings at the Sender Agreement level appear to have absolutely no effect whatsoever.
I have confirmed that I have no problems if I use an adapter of type SAP BASIS 7.00. However, I really need to get this working on 7.1.
I have looked on the SAP support portal but can not find any notes that relate to this.
Has anyone else had a similar problem? And have you found a fix for it?
Any suggestions would be welcome.
Edited by: Malcolm Dingle on Jun 17, 2009 1:08 PM

Hi Shai,
Please have a look at the following link and see if it helps you .
It deals with SOAP adapter installation and activation
Re: SOAP adapter installation and activation
Best Regards
Edited by: Prakash Bhatia on May 8, 2009 11:51 AM

No suitable sender agreement found - File / Adapter, Sender FTP

Hi SDN Friends,
Is my first time in PI with FTP / FILE ( really I'm newbie in PI - but 2 years in ABAP ).
I have configurated my communication channel with and FILE/ADAPTER on a Sender FTP...
I have Tried with 2 FTP, one in my PC, and one Public... but in both cases, it's doesn't works... monitoring my communication channel, I get the No suitable sender agreement found ERROR....
I thought... may be PI has not access to the FTP's servers, so run in SAP PI server, an ABAP program trx se38, program: RSFTP002 and with this, I could connect to the FTP... it works perfectly.
so I don't understand... what I'm doing bad?
Any Help?
regards every body!

u r welcome...2 yrs back i am newbie
when ever we make changes after an error, sometimes XI will not take the changes in cache automatically; uses old one. solution for this is complete Cache refresh.
welcome to Integration World have fun....

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

Why sender agreement need not to create for IDOC

Hi Experts,
why sender agreement need not to create for idoc

Please check these related discussions:
Re: Question on sender agreement
Re: IDOC and HTTP Adapters - sender agreement ??
Re: ** Sender Agreement is required for RFC but not IDoc, XI, & HTTP.. Why ?
Many threads with the same Q are answered on SDN....so if you search you can find the correct answer that you need!
Regards,
Abhishek.

Adapter don't need Sender Agreement

Similar Messages

Maybe you are looking for