Receiver Agreement error

Hi friends,
I have few scenarios on jdbc-rfc.. for now i can say 6 similar kind at the receiver.. and the rfc is also same..
Now first interface is sucessfull. for the second one i am trying to create new receiver agreement then it is saying it is already exits,,, now what to do.. for this..
for each and evey scenario i have use the same comunication channel then my first scenario out is going to second one..i have faces this... here i can create onley one receiver agreement. please tell me how can we create many receiver agreement

Create the Interface mapping-Here your target Interfae will have "N number of Message Interfaces" for each N message Types. Use the 1:N Mapping done as before.
Now go ahead with other configuration. In Interface Determination select the RB_SPLIT/Extended option use this Interface Mapping over there. If multiple Receivers are required , then go with conditions.
Here i am giving 2 possible ways based on your requirement
In both of the following cases you need to have 2 separate message mappings and 2 interface mappings
Source1_message----
target1_messages - Message mapping(1)
Source1_message----
target2_message - Message mapping(2)
Source1_interface -
target1_interface - use mapping(1)
Source1_interface -
target2_interface - use mapping(2)
1.If 2 receiver messages will be going to same receiving system
a)In Receiver determination no need to specify any condition to determine receiving systems(bcoz you have only one receiving system)
b)But you need to give condition in interface determination.In this case one interface determination is enough
2.If 2 receiver messages will be going to different receiving systems
a)You need to give condition in receiver determination to determine receiving systems
b)In this case, 2 interface determinations required one for each receiving system without any condition
For example
Sender
Service: Source system1
Interface:Source1_interface
Receiver
Service: Receiver1
Inbound interface interface mapping
Target1_interface Source1_interface_to_ Target1_interface
Same as this do for receiver2
Check the following links:
/people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it146s-possible
http://help.sap.com/saphelp_nw2004s/helpdata/en/42/f3b31d48fb1bc8e10000000a11466f/frameset.htm
Note: reward points if solution found helpfull
Regards
Chandrakanth.k

Similar Messages

  • Error in AEX Itegrated Configuration Testing "No receiver agreement found."

    Hi,
              I am working on PI 7.3, doing a File to Idoc by using the AEX(Advance Adapter Engine Extended). While doing the configuration testing i am getting the below error "
    Problem occurred in receiver agreement for sender -BC_XXXXXXX to receiver -BS_XX5_100,urn:XXXX.com:POC:MasterData:Article:ECC:Sender.SI_OA_POC: No receiver agreement found for , BC_xxxxx, , BS_xx5_100, urn:xxxx.com:POC:MasterData:Article:ECC:Sender, SI_OA_POC."
            I gone through the SDN but not got usefull links. I tryied to recreating whole scenario, Cache refresh, but no luck. Can you pls let me know where is the problem. Do i need to do any additional configuration other than creating RFC in Java stack for AEX?
    Thanks & Regards,
    Dev

    Hi RK,
            Thanks for your reply.
                  Yes i have created the Idoc_AAE channel and assigned this channel in my Outbound Processing tab.
    What do you mean by java channel in Inbound Processing? My sender is File so i created File channel and assigned in the Inbound processing tab.
    @ Raghu,
                I have created the Receiver channel. I no need to create Receiver agreement because i am using the ICO so if i give the Receiver and Inbound interface details that is enough. And one more thing i am doing testing in ID Test confiuration.
    Thanks ,
    Dev

  • Error in BPM (No receiver agreement found from sender to bpm)

    Hi all
    In a simple bpm scenario, I am getting a error that No receiver agreement found for sender service to bpm integration process.
    What might be the reason?

    your configuration should like this.
    say u are doing File to File using BPM
    File to BPM
    then BPM to File.
    so u need to create RD where sender is fileservice  and receiver is BPM.
    second u hav to create another RD where BPM is sender and Fileserviceis receiver.
    So there should be
    one Sender Ag
    two RD
    two ID
    one RA.
    Thanks
    Farooq.

  • IDOC to FTP File - Error : SAP:Stack No receiver agreement found for send

    Hello Friends,
    I need to configure a senario Idoc to FTP File, Í did required settings in R3 and in PI... , did mapping and configuratino in PI... and when I send my idoc I got error msg in monitor
    <SAP:Stack>No receiver agreement found for sender ,BMG_ASN_File_Component to receiver ,GTN_224,http://adis-bmg.de/asn,SI_BMG_ASN</SAP:Stack>
    I search the fourm but did not got my answer, me just a bit confused...
    In my senario I have having followings:
    1. Bussiness System ( RFT : sender R3 system).  ( I have define a party and make a connection under Idoc Partner )
    2. Bussiness Component ( ZTEST_COMP as on Reciever side is File Server, so I define the reciver as bussiness component )
    3. Communicatin Channel
        File with protocol FTP having communicatin component as my Bussiness Component ( reciver ). there I defied the required info for FTP
    4. Reciever Determination
        Sender:
        - RFT
        - Idoc-Interface
        - urn:sap-com:document:sap:idoc:messages
       Reciever
        communication party  = space
        communicatin component = ZTEST_COMP
        Configure Reciever:
       There I again define the communication component as  ( ZTEST_COMP)
    5. Interface Determination
        -RFT
        - Idoc-Interface
        - urn:sap-com:document:sap:idoc:messages
       Reviever:
        ZTEST_COMP
    and define the mapping which I did in design ( although I have seen some threads where mentioned we dont need maaping in this case ) ?
    6. Reciver agrement
    sender:
    - RFT
    Reviver:
    - ZTEST_COMP
    - SI interface ( SI_BMG_ASN )
    - http://test-etc.de/asn
    and included my CC for file .....
    Now when I send Idoc I got error msg that Reciver is not found : am I dong something wrong ?  do I have to defien a bussiness system instead of Bussiness Component ?
    Pls suggest...

    ( I have define a party and make a connection under Idoc Partner
    Do you really need a party in your communication? Should it not be a partly-less communication.
    In the receiver agreement ensure that you have included the inbound message interface.
    communication party = space
    No need to give any space.
    In the Interface Determination i hope that you have included the receiver meessage interface and then the corresponding Interface Mapping.
    If still not works then make some dummy changes and again activate....correspondingly check the cache status of the ID-objects
    Regards,
    Abhishek.

  • Configuration Error in PI 7.1 Receiver Agreement

    Hi,
    I am facing a problem while testing my interface throught RWB, I am getting below error.
    Error while sending message: com.sap.engine.interfaces.messaging.api.exception.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:
    I have checked the configuration in ID and its showing green. Also i have tried to re configure complete scenario but still facing same problem.
    point will be rewarded for solution.

    Hi
    Check the Configuration once again .
    Check the Receiver Determination and  Recever agreement .
    Or Else . Test the ID using Test Configuration in tools.

  • 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

  • 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 receiver agreement found Error in SXMB_MONI

    Hello all,
        I am working sample file to file scenario. after compliteion of my scenario i tested through component monitoring. i got following error in sxmb_moni, No receiver agreement found for sender, But i defined receiver agreement and communication channel, can any body suggest me how can i resolve this problem,
    Thanks&Regards,
    VenkatK

    Dear Venkat,
                    Once check whether you have defined the correct reciver aggrement. If it is fine, Then delete the receiver aggrement and configure new one and activate it. And test the sceanrio once. I think this may solve ur problem. If the problem exists again, then follow the below steps.
    In SAP system, Goto SICF tcode.
    1.There you just click execute button or F8.
    2.Then expand "Default Host" .(This will be in below the Virtuelle hosts/services)
    3.Then expand SAP.
    4.Then expand XI.In that just activate all the service elements.Just right click and select activate service.
    After this, execute your sceanrio. This will solve your problem.
    If Helpful reward points.

  • No Receiver agreement found for Sender

    Hello,
    I have a scenario like this : sending an IDoc from R/3 4.6c to R/3 4.7 through XI 3.0.
    I am struck up with the follwoing Error in SXMB_MONI
    "outbound binding exception: No outbound binding found for , R46, , ENT, urn:sap-com:document:sap:idoc:messages, ORDERS.ORDERS04"
    The Complete TRACE is as follows:
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Technical Routing
      -->
    - <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
      <Trace level="1" type="B" name="IDX_INBOUND_XMB" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">ALE-AUDIT-IDoc-Inbound Handling</Trace>
      <Trace level="1" type="T">IDoc-Inbound-Handling</Trace>
      <Trace level="1" type="T">Syntax-Check-Flag X</Trace>
      <Trace level="1" type="T">IDoc-Tunnel-Flag X</Trace>
      <Trace level="1" type="T">Queueid</Trace>
    - <Trace level="1" type="B" name="IDX_IDOC_TO_XML">
      <Trace level="1" type="T">Get the Metadata for port SAPR46</Trace>
      <Trace level="1" type="T">Convert Segment-Definitions to Types</Trace>
      <Trace level="1" type="T">Make Syntax check of actual Idoc</Trace>
      </Trace>
      <Trace level="1" type="T">Set Receiver Routing-object</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-SET_IDOC" />
      <Trace level="1" type="T">Exit Function IDX_INBOUND_XMB</Trace>
    - <Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-GETBLOBDATA">
      <Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-ITAB_TO_BINARY" />
      </Trace>
      <Trace level="1" type="T">COMMIT is expected by application !</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
      <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
      <Trace level="1" type="T">****************************************************</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">XMB entry processing</Trace>
      <Trace level="1" type="T">system-ID = XI3</Trace>
      <Trace level="1" type="T">client = 800</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = SMART01</Trace>
      <Trace level="1" type="Timestamp">2004-12-27T20:08:46Z CET</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">****************************************************</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Message-GUID = F0EAB201EEA5F74A814EF22C32394FD0</Trace>
      <Trace level="1" type="T">PLNAME = CENTRAL</Trace>
      <Trace level="1" type="T">QOS = EO</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
      <Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
      <Trace level="1" type="T">Queue name : XBTI0009</Trace>
      <Trace level="1" type="T">Generated prefixed queue name = XBTI0009</Trace>
      <Trace level="1" type="T">Schedule message in qRFC environment</Trace>
      <Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Going to persist message</Trace>
      <Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
      <Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
      <Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
      <Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
      <Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
      <Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
      <Trace level="1" type="T">system-ID = XI3</Trace>
      <Trace level="1" type="T">client = 800</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = SMART01</Trace>
      <Trace level="1" type="Timestamp">2004-12-27T20:08:46Z CET</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
      <Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
    - <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
      <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>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
    - <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
      <Trace level="1" type="T">I N T E R F A C E - 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>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
      <Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />
    - <!--  ************************************
      -->
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
      <Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">number of receivers: 1</Trace>
      <Trace level="1" type="T">Single-receiver split case</Trace>
      <Trace level="1" type="T">Post-split internal queue name = XBTO____0000</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Persisting single message for post-split handling</Trace>
      <Trace level="1" type="T" />
      <Trace level="1" type="T">Going to persist message + call qRFC now...</Trace>
      <Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
      <Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
      <Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
      <Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
      <Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
      <Trace level="1" type="T">system-ID = XI3</Trace>
      <Trace level="1" type="T">client = 800</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = SMART01</Trace>
      <Trace level="1" type="Timestamp">2004-12-27T20:08:46Z CET</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
      <Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
      <Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>
    - <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
    - <!--  ************************************
      -->
    - <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV">
      <Trace level="1" type="T">No mapping required</Trace>
      </Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
      <Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-GETBLOBDATA" />
      <Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
    - <!--  ************************************
      -->
    - <Trace level="1" type="B" name="CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV">
      <Trace level="1" type="T">processing the outbound binding</Trace>
      <Trace level="1" type="T">search outbound bindings</Trace>
      <Trace level="1" type="T">outbound binding exception: No outbound binding found for , R46, , ENT, urn:sap-com:document:sap:idoc:messages, ORDERS.ORDERS04</Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
      <Trace level="1" type="System_Error">Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      </SAP:Trace>
    I have made neccesary Configurations for the Receiver agreement in the Configuration Directory...
    Anybody could please help me out...
    Regards,
    Romit Arun Shankar

    Hi Frank,
    Many Thanks for your reply.The problem got sorted out and the IDoc(ORDERS04) which i send in SAP 4.6c gets into SAP 4.7 AS ORDERS04 but i have a new problem now....
    I didnt use any mappings until now...but now i have to have the segment E1EDK14 filled up for Sales organisation, Distribution Channel, Division details as well as the material number. These segments will not be filled up when a PO is sent from the source system.These segments has to be filled only in the XI system...Is it ? or is there any other solution for it....
    Now how we can have this segment E1EDK14 which can occur any number of times with constant values for SORG,DV,DC in the mapping process....
    Waiting for ur replies....
    Bye,
    Romit Shankar Arun.
    For this

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

  • No receiver agreement found.

    Hi Experts,
    I am doing one scenario i.e idoc to file .
    I am getting an error that is "no receiver agreement found" in sxmb_moni, but i did the test configuration in ID which is working fine.
    can any one help on this.

    Hi,
    Check the following.
    1. Any cache problems in the ABAP stack and java stack.
    2. Check your receiver whether it is case sensistive.
    3. Check the receiver determination pipeline step in soap header whether the sap receiver anything filled in or blank. If blank, definitely there is an error in your config.
    Since you have tested it in ID, I would assume it would be cache problem.
    Regards
    Krish

  • HT3728 Firmware Update 7.6.4 Error: I uploaded the 7.6.4 firmware update today, and received an error message as it was finalising. As I am using my Time Capsule as the Airport router, I am now no longer able to access it to try to resolve the problem. He

    Dear Support Team,
    I agreed to the Time Capsule 7.6.4 update today, but as it was completing, I received an error. It said to close the page and try again.
    I use my Time Capsule as my Airport wireless router and now can't access the Time Capsule to re-upload the Firmware update.
    Has anyone else had this happen?
    Is there a way to resolve the problem?
    Do I need to hardwire the Time Capsule? Then what?
    Would really appreciate some help!!
    Thanks everyone.

    Factory reset the TC and it should come back to life.
    The Factory Reset.
    Power down the TC.
    Hold in reset. and keep holding it in. Be Gentle! It is a tiny surface mount switch with a plastic lever.. Attempting to push it out the other side of the TC will not make the switch turn on better.
    (I fix TC and have several reset levers bent over and jammed or broken off).
    Power on the TC.. remember with the reset held in.. this needs three arms.. a friend or power switch you can get to with your feet..
    Keep holding in reset for about 10sec until the front LED flashes rapidly.
    Release reset and wait .. the boot will be slow as it deletes previous setting.. only from router side and pulls out the factory defaults. No files are deleted on the hard disk.. but the name of the TC may change.
    As a rule .. wireless is not reliable enough for mission critical work like firmware upgrades.. (Heck I don't think it is reliable enough for backups).
    Apple doesn't insist on wired connections.. some other manufacturers do.. and post warnings not to attempt it over wireless. Warnings inevitably read after the failed firmware update btw.. so perhaps Apple have decided to just save themselves the hassle.
    I believe it is just good practice to use ethernet for any time that sitting on a branch.. whilst sawing it off (ie failure will kill any future access).. means you always use ethernet for any setting up of a wireless router.. but you see I am old.. with grey/white hair.. and too many dead modems and routers around me.

  • Stock Transport Scheduling Agreement - error message: 'Stock in transit...

    Stock Transport Scheduling Agreement - error message: 'Stock in transit exceeded'
    Hi, I do have a question about transport scheduling agreements.
    I have created a stock transport scheduling agreement via ME37, doc. type LU for a stock material from issuing plant TT01 to receiving plant TH01. The material is maintained in both plants.
    After that,I maintain the delivery schedule via ME38 for a quantity for today. The quantity is available at issuing plant TT01, checked via MMBE.
    Then, I try to post the goods via MIGO. When I try to post the document, I get the following error message: "PL Stock in transit exceeded by 1,000 T% : 794 TH01 S1". Why do I get that? My target is to decreate the stock quantity in TT01 and to increase the stock quantity in TH01.
    Thanks, Peter

    Hi,
    This happens when you are issuing more on the schudle qty, Check you have anything on the transit receive it the try agin to process the issue.
    Hope it helps.
    Suresh

  • Integrated Configuration- Problem occurred in receiver agreement for sender

    Hi ,  I am using AAE in PI 7.1  and it is proxy to file scenrios.
    When Ia m doing testing  in Integration Directory in test configuration its giving me this error .
    Problem occurred in receiver agreement for sender -<ECCBUSINESSSYSTEM> to receiver -BS_D_EPS,http://abc.com/sap/pi/HR/Qualifications.Qualifications_Async_Out: No receiver agreement found for , -<ECCBUSINESSSYSTEM> , BS_D_EPS, http://abc.com/sap/pi/HR/Qualifications, Qualifications_Async_Out
    ( here it should take interface  Qualifications_Async_In, but logs says it is pointing to outbound interface)
    here  when I am going in to trace logs  then it seems  that are not able to understand  the   receiver interface . rather then it is taking sender inface in logs..
    In trace logs . I am getting
    Receiver Determination
    <Not found>
    <Trace level="1" type="B">CL_RD_PLSRV-ENTER_PLSRV</Trace>
    <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 - BS_D_EPS </Trace>
    <Trace level="2" type="T">Using Receiver Determination 00000000000000000000000000000000 </Trace>
    <Trace level="1" type="T">No Relation found - accept given Receivers. </Trace>
    <Trace level="2" type="T">...extracting Receiver from Header: BS_D_EPS </Trace>
    <Trace level="2" type="T">Classic Receiver Determination via Rules. </Trace>
    <Trace level="3" type="T">...create rule engine </Trace>
    <Trace level="2" type="T">No Receiver found behaviour: 0 </Trace>
    <Trace level="2" type="T">Number of Receivers:1 </Trace>
    <Trace level="1" type="E">CL_RD_PLSRV-ENTER_PLSRV</Trace>
    Interface Determination
    <Not found>
    <Trace level="1" type="B">CL_ID_PLSRV-ENTER_PLSRV</Trace>
    <Trace level="1" type="T">I N T E R F A C E - 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="1" type="T">...There is no Interface Determination configured for receiver party and receiver service BS_D_EPS </Trace>
    <Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) BS_D_EPS Qualifications_Async_Out </Trace>
    <Trace level="2" type="T">...valid InbIf without Condition: Qualifications_Async_Out </Trace>
    <Trace level="2" type="T">Number of receiving Interfaces:1 </Trace>
    <Trace level="1" type="E">CL_ID_PLSRV-ENTER_PLSRV</Trace>
    Operation Mapping
    <Not found>
    <Trace level="1" type="B">CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV</Trace>
    <Trace level="2" type="T">......attachment XI_Context not found </Trace>
    <Trace level="3" type="T">Mapping already defined in interface determination </Trace>
    <Trace level="1" type="T">No mapping configured </Trace>
    <Trace level="1" type="E">CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV</Trace>
    I  have developed the other integrated configuration scenario and this is working fine . 
    please let me know how can I troubleshoot it

    I am using sender as Soap and receiver as File adapter. 
    here  the problem is that  while going for interface deteremination and receiver agreement  it is calling to  Outbound interface .
    It should call the inbound interface. I put all the details correctly and deleted all the objects and crated again for both Ir and Id..
    I put the name of inbound interface  in configuration but while executing its calling outbound interface.

  • Seeburger AS2 HTTPS receiver channel error

    Hi,
    I am getting the following error in the receiver Seeburger AS2 channel with HTPS connection and going through a proxy to the Partner.All the certificates have been installed,proxy server information gives,mentioned the key store values  and encryption certificate values have been mentioned in the receiver agreement that is using the channel.
    Message processing failed. Cause: javax.resource.ResourceException: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: HTTP-Client component init failed # java.security.PrivilegedActionException: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: Could not retrieve alias collection., SEEBURGER AS2: HTTP-Client component init failed # java.security.PrivilegedActionException: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: Could not retrieve alias collection.
    Can you please give me an idea whether I am missing something or any configuration settings I need to make.
    Thank you,
    Sri

    hi Neetesh,
    Thank you for the link.The first thing I have looked at is the link you gave me.But when I give with * it is complaining that it is not able to retrieve the certificates.
    TRUSTED/AS2CERTS/*,but I have backward slashes..may be  OS is different ,I think the original poste might have Windows servers.
    any other ideas please.
    thank you.

Maybe you are looking for