PCK Sender agreement

Hi mates,
At <a href="http://help.sap.com/saphelp_nw04/helpdata/en/db/73e03fc2269615e10000000a155106/content.htm">help.sap.com</a> I see that Sender agreements are not required in cases of proxies, SOAP & Mail adapter.
Since there is no Receiver Determination Step in PCK and receiver has to be mentioned in the Sender Agreement, If Sender agreement is not required for proxies, SOAP & MAIL, how are the receiver party & service mentioned?
Do they have to be sent by the client programs of proxy, SOAP & Mail? If yes, the WSDL generated has to contain the details of the receiver psrty and service too. Is that true?
Please clarify.

As for RD in XI i am pasting lines from sap.help
To forward the message, the following objects are required in the Integration Server:
·        Party and service of party A, which sends the message. If there is a signature and you want it to be validated, you must also define a communication channel of type Sender and XI. In this case, you must also create a corresponding sender agreement (SA2).
·        Party and service of party B, which receives the message. You must define a communication channel of type Receiver and XI.
·        A receiver determination (RD) to determine the receiver of the message.
·        An interface determination (ID) to define the inbound interface for the outbound interface of the sender.
·        A receiver agreement (RA3) to transfer the message from the Integration Server to the PCK of party B.
Hope it helps.

Similar Messages

  • 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

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

  • Sender Agreement problem.. in ID

    In Integration Directory, I am able to create all the things namely, Business Services and Communication Channels, Interface Determination and Receiver Determination and Receiver agreement but I am unable to create the Sender Agreement.
    Let me explain my scenario : File-XI-File.
    I have done all the necessary things like SLD part, Design part etc..
    I have gone through the blogs by Venkat on File-XI-File Scenario...
    If anybody can guide on this that will be very helpful..
    Thanks in advance.
    Best Regards,
    Mona

    Hi,
    >><i>I am able to create all the things namely, Business Services and Communication Channels, Interface Determination and Receiver Determination and Receiver agreement but I am unable to create the Sender Agreement.</i>
    Create one service and inside that create a Communication channel. Then add your interfaces to it, depending on the type. If it is outbound the add it in the sender tab else in the receiver.
    Then right click on the sender agreemnet and create new. Give all the required fields and click save.
    Regards
    Suraj

  • Wrong Sender Agreement:The Sender agreement does not have channel

    Hi Guys,
    I am trying RFC to File scenarion where I am triggering a report which is calling a RFC module I have given the destinaztion name correct .When I am executing the report it is failing giving the following error
    "Wrong Sender Agreement:The Sender agreement does not have channel"
    I have checked that sender agreement is there.
    Also when Iam changing the RFC call by removing IMPORTING parameters and adding IN BACKGROUND TASK It is getting executed and goin to XI successfullly but after adding IMPORTING Param it is failing ?
    Any suggestion on the same?
    Regards

    Hi Guys ,
    I have tested the same again from RFC directly without Report and after some time it failed giving 'SYSTEM ERROR'.
    When i checked the channel it is giving following error:
    Error: 2008-01-10 13:36:19 IST: Message processed for interface Z_RFC_TESTSYNCASYNC: com.sap.aii.af.mp.module.ModuleException: call to messaging system failed: com.sap.aii.af.ra.ms.api.DeliveryException: Received HTTP response code 500 : Timeout caused by: com.sap.aii.af.ra.ms.api.DeliveryException: Received HTTP response code 500 : Timeout
    Any help now ?
    Regards

  • File Sender without Sender agreement- Possible?

    Hello
    It may seems bit unusual but i am having requirement in which the file sender adapter is expected to trigger the OS level command in which it gets the file from SSH server in the XI polling directory and then XI File adapter would pick up that file.
    Now it has been observed that, XI File adapter doesn't execute OS level command in its poll cycle unless it creates message which means XI would expect some file (atleast a dummy file) in its polling directory.
    Since this is not possible, we thought of creating the second adapter which will poll the dummy file of say 0 KB and call the OS level command which will get the files from SSH server and then the second adapter would poll the actual file.
    Since second adapter would serve just as the trigger channel, its not expected to have any sender interface associated with it and hence it should poll the file without any sender agreement. can this be possible?
    thanks in advance.
    regards
    rajeev

    Hi,
    Actually i tried that earlier but it didn't help.
    It does executes command before or after but that only when it creates a message and it doesn't create message unless we have suitable sender agreement.
    Actually i tried with dummy message interface (without actual message interface in IR) and that works but it fails in MONI and generates the error message as no suitable receiver found which i wanted to avoid.
    Thanks and Regards
    Rajeev Patkie

Maybe you are looking for