No Obects found in Receiver Determination

Hi Friends,
In Integration Directory:
  Once i create the Communication channel.
  I try to create receiver determination  :
In receiver determintaion:
once i give the sender Service:
I try to give the sender Interface it gives me in f4 options( "No objects found" )in
In  interface determination it gives me the same problem.
" No Objects found "
What is your suggections>

Hi Chirumamilla,
I have assigned  the BS to SWCV in SLD still my problem is not solved.
You know i have checked in SLD the Business system is propely assigned to  SWCV.
I have cleared sld cace in ID.
Basically i have imported IR and ID objects from diiferent system.
I have created SLD only in our Imported system.
my scenario is as follows:
Webclient-->PI 7.0--
>SAP ECC
(Sender)                                      (Receiver).
Webclient will request for customer details to SAP ecc sytem and SAP ECC system will send back the complete CUTOMER details .
Entire Process in : synronous mode.
Sender Adpater: SOAP adapter & qos - BE
This is my complete theme of my interface.
In my Integration Directory when i click my business system : I  see the empty list for i/b and o/b Interfaces.
Kindly help me

Similar Messages

  • Message Interface not found during Receiver determination

    Hi Folks,
    While doing Receiver determination i found this error
    “Problem Loading Schema Description: Message interface does not exist in any software components installed on this business system”
    i checked it in SLD also for Product assigned to Particular Business System. Even i tried with creating a new one and assigning the product and software component to it.
    When i imported the Business system from SLD, i m not able to see any inbound and outbound interface for particular business system.
    But it is working for another scenario where inbound interfaces are used.
    plz help me out
    Sachin

    Sachin,
    ><i>DEV and QA is having diff. SLD so i created the SWC and products in SLD again.</i>
    You should export the SWCV from your Old SLD and import in into your new SLD.
    and then import the same in Integration Respository.
    When you try to export SWCV from SLD, you will get a .CIM file which you need to save in your local desktop and then import this in the new environment.
    More in this article,
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9e76e511-0d01-0010-5c9d-9f768d644808
    Regards
    Bhavesh

  • No receiver found in Receiver Determination

    Hello Experts,
    Sub: Calling integration process (which in software component1) from sender service interface_Out (which is in another software component2) in Receiver Determination Fails.
           There are two software components, S/W C1,  S/W C2,
            In  S/W C1,->
            Integration process (IP1)created in S/W C1, with name space NS1,
            Service interface1(abstract) SI1 with message type MT
            In S/W C2,->
            Sender service interface2 SI2(outbound) with message type MT with namespace: NS2
    (MT message type, in both service interface holding the same,
    used SI1 In receive step in IP1.
    Interface Determination from BS2,SI2,NS2<->   IP1,SI1(No mapping).)
    In Receiver Determination,
    Business system BS2;
    Sender Service Interface: SI2;
    Name space: NS2, 
    In Receivers  :  IP1
    Problem is :  do not find this receiver.
    I have to call this process, like this.  Please help on this.
    Use case is:
    single Soap request is coming, many application are using the same using common Receiver determination( which in S/W C2), 
    Now i have to use the same receiver determination to send this message in IP1 which is in SW C1;  
    -> any alternative solutions for this                      
    Thanks,
    Deviprasad.

    hi,
    when you use Integration Process the configuration in the ID must be
    Receiver Determination 1:
    Sender System: XXX
    Enterprice Services (outbound)
    Namespaces
    Target System: Integration Processes
    No Mapping requiered in Interface Determination
    Line:
    Receiver Determination 2::
    Sender System: Integration Process
    Enterprice Services (Abstract)
    Namespace
    Target System: YYYY
    No Mapping requiered in Interface Determination
    Sender Agreement=1
    Receiver Agreement=2
    Interface Determination=2
    Communication Channels=2
    Take in mind that in the Interface determination you have to define as receiver structure the Service Interface (Enterprice Service in PI7.1) type Abstract. if you cant select it delete all filter in the popup qhen you have to select the Inteface in the reciver structure.
    Check the Integration PRocess if you define the SI_XXX_abs in the reciver step.
    check all changes in the ESR were activated
    Check this out and let me know
    Edited by: Rodrigo Alejandro Pertierra on Sep 3, 2010 2:42 PM

  • Receiver Determination: Sender not found is in

    Hi,
    I am getting a "message incomplete: no sender found" error, in a synchronous step from a BPM(The intended receiver is another BPM which is in a separate namespace & SWCV). The message interface for the send step is also in a different namespace & SWCV.
    I tested the call to the target BPM(with the same message interface) using a tester BPM and it was working fine. However both were in the same namespace.
    I couldnot find any reason other than to think about the namespaces being different.
    I have defined the dependencies between the SWCV's and have imported those into the Integratoin builder.
    suggestions/leads/hints will be most appreciated...
    Thanks & Regards,
    Renjith.
    Now we have got a little more clarity on how the error occurs. Let me explain the steps in BPM -
    Step1 Receive MSG1
    Step2 Map MSG1 to MSG2
    Step3 Send ASYNC MSG2
    Step4 map MSG2 to MSG3
    Step5 Send Sync MSG3
    and so on...
    In this case the Step5 send sync msg3 fails and i get the error back - "Message is incomplete. No Sender found" - during receiver determination.
    If i were to remove the step3, send msg3 async, everything works like a charm....Has anyone got an idea why this is happening?
    Message was edited by: Renjith Andrews

    Hi Priyanka,
    Thanks for the response.
    The step 3 was executed successfully and i can see the file in the output folder. It was not failing.
    As for step5, it never got till recevier determination because the error was that the sender information was missing.
    Thanks & Regards,
    Renjith.

  • No receiver determination found in spite of correct url

    Hi everybody,
    our partner tries to reach our XI on https adapter to start a synchronous process. The url is as follows:
    <u>https://[host]:[port]/sap/xi/adapter_plain?party=[PARTY]&service=[SERVICE]&interface=[INTERFACE]&namespace=[NAMESPACE]</u>
    I can see the message in the TA: sxmb_moni but there is always the error: No receiver determination found. But everything is correct. There IS a valid receiver determination set up. Are there any other parameters that have to be put into the url to get that connection online?
    Regards.
    Oliver.

    Yes please...the reason i am asking you try this is that in the comments of the HTTP inbound handler...you see what is below....so i am asking you to put the parameters that seems to be mandatory from this...
    call-syntax:  XI 3
    http://hostname:port/path
                         ?namespace=???
                         &interface=???
                         &service=???
                         &party=???
                         &agency=???
                         &scheme=???
                         [&qos= EO|BE|EOIO]
                         [&msgguid=???]
                         [&queueid=???]
                         [&trace=[1|2|3]]
    Thanks,
    Renjith

  • Receiver Determination Not Found

    Hi all,
    Currently we integrating SAP ECC with TM using PI ,we have followed the standard document given and done the configuration steps ,
    "Installations and Upgrades - R" SAP Rapid Deployment solutions" SAP Transportation Planning for Shippers RDS" SAP TM DTP RDS" SAP TM DTP RDS V2.90",the reference document is from the above link.
    ECC has triggered an workflow which is in format of XML ,but when we checked in SXMB_Moni,i am getting the below error.
    Receiver Determination: No Receiver could be determined
    2:26:30 PM
    2:26:30 PM
    SHDCLNT900
    http://sap.com/xi/APPL/Global2
    BusinessDocumentFlowTMInformationbyBusinessObjectReferenceQueryResponse_Out
    CENTRAL
    "Current Status"
    Synchronous
    BE
    IENGINE
    00000000000000000000000000000000
    00000000000000000000000000000000
    00000000000000000000000000000000
    53EB863237550A10E10080000A1A016E
    sender =>R/3 system
    Receiver=>TM system .
    Your help is badly needed

    hi Hareesh,
    please find the below screen shot of my ID objects ,we generated it using "Apply Model From ES repository".

  • Receiver determination not found for one interface

    Hi,
    I am receiving the message via SOAP and then sending to SAP as IDOC.
    The communication is party o partyless communication.
    I have configured 2 receiver determination for the same sender and receiver but with 2 different interfaces.
    When i test the scenario via SOAP tool only one gets  executed and the second one neither throws an error nor getting executed.
    I think i have a error in the configuration that i did for the 2nd interface since i am using the 1st receiver determination which has been created already ?
    but in the Quick Test tool and Test tool in ID both the receiver determination is working fine.please provide the inputs
    Thanks in advance,
    Rgds,
    Vasanth.

    Hi All,
    Thanks for all of your replies.
    I have activated all the objects and checked it again once.
    As i said earlier the sender and receiver are same and that's why i have been pushed to create 2 receiver determinations for the same file(not IDOC as i said above) to be dropped in to two different locations.
    Also the configuration is party in sender to partyless in receiver.
    To give a clear explantion:
    All the objetcs are activated and works fine when i test in the test tool in ID by specifying the inetrface and namespace.
    Sender1 - Int1 - sap1.com - SA - RD - ID - RA -Receiver1  = working fine when tested by ID test tool
    Sender1 - Int2 - sap2.com -SA- RD - ID - RA Receiver2  = working fine  when tested by ID test tool
    RD = Receiver determination / SA = Sender Agreement
    It is not working when i send the same file thru SOAP client tool and only one receiver determination is working and another is not.
    Any idea ?
    Thanks,
    RGds,
    Vasanth.
    Message was edited by:
            Vasanthakumar Balasubramani
    Message was edited by:
            Vasanthakumar Balasubramani

  • Receiver Determination Not found   Internal Error...Please help me

    Hi Gurus..
    I have done a file to File scenario and when i test my scenario i am getting this error
    Receiver Determination
     Internal Error
    HTTP connection to ABAP Runtime failed. Error: 403 Forbidden URL: http://sapserver:8001/sap/xi/simulation?sap-client= User: PIDIRUSER
    So please please help to solve this problem.

    Hello,
    Seems that you should configure the RFC Destinations and also
    maintain the correct password, which should be the SAME, for all
    the service users.
    Refer to note below according to your system version:
    PI 7.1:
    #999962 - PI 7.10: Change passwords of PI service users
    XI 7.0
    #936093 - XI 7.0: Changing the passwords of XI service users
    XI 3.0
    #721548 - XI 3.0: Changing the passwords of the XI service users
    Regards,
    Caio Cagnani

  • Receiver Determination and Interface Determination Condition conflict in ICO

    Hi,
    I found a strange issue today while configuring two receivers using the Receiver and Interface Determination conditions.
    Sender - Proxy Service
    Receiver1 - ReceiverA
    Receiver2 - ReceiverB
    Receiver Determination Condition : When Field1 = 100, message should flow to ReceiverA and ReceiverB
    Interface Determination Condition (ReceiverA) : When Field1=100 and Field2=50 message should flow to a specific interface in ReceiverA
    There is no Interface Determination condition for ReceiverB, for all messages having Field1=100, it should go to ReceiverB.
    Test Scenarios:
    1) Field1=100, Field2=50 : Message flows successfully to ReceiverA and ReceiverB
    2) Field1=100, Field2=89 : Message fails to process from ECC itself throwing Interface Determination not found error. Ideally this is a positive scenario for ReceiverB and it should send the message to ReceiverB without any errors. But, this did not happen in this case
    I tried the same by configuring the conditions completely in Receiver Determination itself without using the Interface Determination, it worked perfectly fine. But, just wanted to understand that if this is an expected behavior.

    Hi Sherin,
    As there are two receivers Receiver A and Receiver B.You need to create two bussiness components and two communcication channels for two receivers and one Reciver Determination, two Interface Determination,two Receiver Agreement.In Receiver Determination you need to keep the below and condition.
    In the above screenshot the two receiver are Receiver B and Receiver C and Field 1 is Key_Value and Field2 is Emp_ID.
    If the Key_Value=100 and Emp_ID =22 then the message should go to both the receivers B & C by keeping the following AND condition
    If the Key_Value=100 and Emp_ID is not equal to 22 then the message should go only to Receiver B by keeping the following condition
    You need not keep any condition in Interface Determination just create 2 Interface determination for two receivers.
    Hope this helps you.
    Thanks,
    Durga.

  • BPM - Do we need receiver determination step between trans and sync send?

    Hi Gurus,
    I have a 1:1 transformation step followed by a sync send step. The transformation step is executing fine. While the sync step is executing, I am getting an error says 'No receiver determination found'.
    While I am executing this sync step in a separate, it is working fine.
    Do I need to have 'Receiver determination step' between Transformation step and Sync send step? I think so. Can somebody confirms this?
    Thanks for your kind help.
    Kalyan

    Hi,
    I think there is no need of a Receiver determination step in the BPM.
    You should have a proper receiver determination in configuration for this BPM scenario. (i.e) A receiver determination from BPM to the service configured for the synchronous interface.
    Regards,
    P.Venkat

  • Configuration Scenario Builder - Receiver Determination Problem.

    Hi  I am Follows  configurates Integration Scenario to SRM-SUS scenario in XI
    In Model Configuration.  when I try create Object Bottom in Simulation Process .  generate the report show the next message for
    Component View Connection
    Receiver Determination light yellow color  SRD_009 | PurchaseOrderRequest_out
    Analisys ; Requiered Communication Component | SRD_009
                    a receiver determination was found for connection
                    Reciever are missing in the receiver determination found
    Results ;  the reuse receiver determination is already assigned to the configuration scenario
                   the missing receivers were inserted into receiver determination found
                   added receiver communication component SRD_008
    Notes;      Check the conditions for all receivers of the receiver determination. the default result value for the generated condition
                    is TRUE:
    thanks.

    Hi,
    Please verify letter by letter if you haven't make a typo here:
    Default Interface Namespace -- http://mtf
    Default Interface Name -- mtf_mi1
    please also make a test of your scenario in integration directory
    please also do not use best efort quality of service
    /wg
    Message was edited by:
            Wojciech Gasiorowski

  • Interface Determination causing issue in Receiver Determination

    Hi
    I am having an issue with interface and receiver determination as follows:
    - Inbound message may be sent to two receivers.
    - Message gets sent to first receiver, fails during interface determination. There are multiple inbound interfaces found based on a set of XPATH conditions. This creates an error 'Inbound interface found more than once for outbound interface '. That is itself is <b>not </b>the issue.
    - Issue is that the message is stopped from going to the other receiver even if there are no issues in the interface determination for that receiver.
    Is there a way to resolve this? Appreciate any help. Thx, Duncan

    Again, thanks for the replies.
    <b>MONI for RD</b>
    - <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 level="2" type="T">Start without given receiver</Trace>
      <Trace level="2" type="T">Classic Receiver Determination via Rules.</Trace>
      <Trace level="2" type="T">Check conditions for rule line no. 1</Trace>
      <Trace level="3" type="T">...create rule engine</Trace>
      <Trace level="3" type="T">...call rule engine for Condition %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice")% EX and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% CE COSTCENTRE or %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice")% EX and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% CE INTERPLANT or %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice")% EX and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% CE INTERPLANT_ONESTEP or %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice")% EX and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% CE INTRAPLANT or %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice")% EX and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% CE INTRAPLANT_ONESTEP or %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:receivingAdvice")% EX or %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:inventoryActivityOrInventoryStatus")% EX</Trace>
      <Trace level="2" type="T">......extracting (new) for Extractor: XP /p2:despatchAdvice</Trace>
      <Trace level="2" type="T">......extracting values found: 0</Trace>
      <Trace level="2" type="T">......extracting (new) for Extractor: XP /p2:receivingAdvice</Trace>
      <Trace level="2" type="T">......extracting values found: 1</Trace>
      <Trace level="2" type="T">...valid Receiver with Condition: - GLR430</Trace>
      <Trace level="2" type="T">Check conditions for rule line no. 2</Trace>
      <Trace level="3" type="T">...call rule engine for Condition %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice")% EX and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% NE COSTCENTRE and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% NE INTERPLANT and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% NE INTERPLANT_ONESTEP and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% NE INTRAPLANT and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% NE INTRAPLANT_ONESTEP</Trace>
      <Trace level="2" type="T">...invalid Receiver: P_3PL_XML_ME_ODTH - despatchAdviceToE1EDT20</Trace>
      <Trace level="2" type="T">Check conditions for rule line no. 3</Trace>
      <Trace level="2" type="T">...valid Receiver w/o Condition: P_3PL_XML_ME_ODTH - S_HTTP</Trace>
      <Trace level="2" type="T">No Receiver found behaviour: 0</Trace>
      <Trace level="2" type="T">Number of Receivers:2</Trace>
      </Trace>
      </Trace>
      </Trace>
    Here, you see that both receivers are found.
    <b>MONI for ID</b>
    <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION" />
    - <!--  ************************************
      -->
      <Trace level="1" type="Timestamp">2007-02-26T20:06:49Z CET Start of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="3" type="T">Calling pipeline service: PLSRV_INTERFACE_DETERMINATION</Trace>
      <Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
      <Trace level="3" type="T">P_CLASS = CL_ID_PLSRV</Trace>
      <Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
      <Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
      <Trace level="3" type="T">FL_LOG =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</Trace>
      <Trace level="3" type="T" />
      <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 level="2" type="T">Check conditions for (Inb: Party Srvc If) GLR430 WMMBXY.WMMBID01</Trace>
      <Trace level="3" type="T">...create rule engine</Trace>
      <Trace level="3" type="T">...call rule engine for Condition%CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p1:inventoryActivityOrInventoryStatus/inventoryDocumentType")% CE INVENTORY_STATUS</Trace>
      <Trace level="2" type="T">......extracting (new) for Extractor: XP /p1:inventoryActivityOrInventoryStatus/inventoryDocumentType</Trace>
      <Trace level="2" type="T">......extracting values found: 0</Trace>
      <Trace level="2" type="T">...invalid InbIf: WMMBXY.WMMBID01</Trace>
      <Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) GLR430 WMMBXY.WMMBID01</Trace>
      <Trace level="3" type="T">...call rule engine for Condition%CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p1:inventoryActivityOrInventoryStatus/inventoryDocumentType")% CE INVENTORY_ACTIVITY</Trace>
      <Trace level="2" type="T">......extracting (new) for Extractor: XP /p1:inventoryActivityOrInventoryStatus/inventoryDocumentType</Trace>
      <Trace level="2" type="T">......extracting values found: 0</Trace>
      <Trace level="2" type="T">...invalid InbIf: WMMBXY.WMMBID01</Trace>
      <Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) GLR430 WMMBXY.WMMBID01</Trace>
      <Trace level="3" type="T">...call rule engine for Condition%CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:receivingAdvice/receivingAdviceItemContainmentLineItem/purchaseOrder/documentReference/uniqueCreatorIdentification")% EX</Trace>
      <Trace level="2" type="T">......extracting (new) for Extractor: XP /p2:receivingAdvice/receivingAdviceItemContainmentLineItem/purchaseOrder/documentReference/uniqueCreatorIdentification</Trace>
      <Trace level="2" type="T">......extracting values found: 2</Trace>
      <Trace level="2" type="T">...valid InbIf with Condition: WMMBXY.WMMBID01</Trace>
      <Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) GLR430 WMMBXY.WMMBID01</Trace>
      <Trace level="3" type="T">...call rule engine for Condition%CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:receivingAdvice/carrier/additionalPartyIdentification/additionalPartyIdentificationValue")% CE SHUTTLE</Trace>
      <Trace level="2" type="T">......extracting (new) for Extractor: XP /p2:receivingAdvice/carrier/additionalPartyIdentification/additionalPartyIdentificationValue</Trace>
      <Trace level="2" type="T">......extracting values found: 1</Trace>
      <Trace level="2" type="T">...valid InbIf with Condition: WMMBXY.WMMBID01</Trace>
      </Trace>
      </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
      <Trace level="3" type="T">Persisting message after plsrv call</Trace>
      <Trace level="3" type="T">Message-Version = 002</Trace>
      <Trace level="3" type="T">Message version 002</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </Trace>
      <Trace level="3" type="System_Error">Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">Persisting message Status = 014</Trace>
      <Trace level="3" type="T">Message version 003</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </SAP:Trace>
    Here, you see that the ID runs for the first receiver. It hits an error because two conditions on the ID for the first receiver are satisfied. However, it then stops rather than allow the processing for the other receiver to continue.
    Any ideas? Thx, Duncan

  • Q? Receiver determination error ????

    Hi all.
    I wana transfer from R3 IDOC to XML with FTP service.
    Although I think configuration completely was finished, happens error.
    How can i correct?
    It's results from test configuration.
        Receiver Determination  <Not found>
           Internal Error
           HTTP connection to ABAP Runtime failed.
           Error: 403 Forbidden
           URL: http://R3:8000/sap/xi/simulation?sap-client=
           User: XIDIRUSER Check
    =======================================================
    Scenario : R3 IDOC -> FTP XML (import Ext Definition DTD)
    1) create Business Service System     : R3, FTP
    2) create Message Interface about FTP : MI_FTP_in
    3) create Interface Mapping R3 & FTP  : IM_R3_to_FTP
    4) import business system about FTP server : FTP
    5) create Receiver Determination : |R3|IDOC_inf
         sender : R3
               - interface : IDOC interface
         configured Receivers
               - Service   : FTP
               - Receiver  : FTP
               - interface : MI_FTP_in
               - Mapping   : IM_R3_to_FTP
               - Receiver Agreement: FTP_file_adapter
    6) create Interface Determination: |R3|IDOC_inf||FTP
         Sender   : R3
               - interface : IDOC interface
         receiver : FTP
         Configured Inbound Interface
               - Inbound interface  : MI_FTP_in
               - interface Mapping  : IM_R3_to_FTP
    7) create Receiver  Agreement : |R3|IDOC_inf|MI_FTP_in
         Sender   : R3
         Receiver : FTP
               - interface : MI_FTP_in
               - Receiver Channel : FTP_File_Adapter
    ========================================================

    Hi,
      Please can you check you Cache is updated or not.If cache is succesfull then check the Port & RFC Destination and Partner profiles  R/3 side and XI side.
    R u testing this scenario using WE19.
    If using we 19 then check the your sender information and receiver information (I mean to say Port,Parner...with outbound parameters )
    Regards,
    Venu.

  • Intermittent JDBC error in Enhanced Receiver Determination

    Hi,
    I have an interface that use Enhanced Receiver Determination in PI 7.1 EHP1.
    The database is DB2 on i5/os 6.1
    Sometimes message ends in error :Error when determining the receiver: Problem while determining receivers using interface mapping: Runtime exception occurred during application mapping com/sap/xi/tf/_HI01_to_ReceiverDetermination_;
    But the same message with same values is successfull earlier.
    This is not a design problem; the interface is working well 95% of the time.
    I found some JDBC error in NWA java logs:
    Error in sax handler parsing request: Error when executing statement for table/stored proc. 'table' (structure 'statement'): java.sql.SQLException: [SQL0104] Token "BUSINESS_SYSTEM" was not valid. Valid tokens: FOR SKIP WITH FETCH ORDER UNION EXCEPT OPTIMIZE.
    Error when calling an adapter by using the communication channel CC_RECEIVER_JDBC_PIDB2 (Party: *, Service: INTEGRATION_SERVER_PX1, Object ID: cb7ea38fb2ac3a06b12d79f5ade2bcf7) XI AF API call failed. Module exception: (No information available). Cause Exception: 'Error processing request in sax parser: Error when executing statement for table/stored proc. 'table' (structure 'statement'): java.sql.SQLException: [SQL0104] Token "BUSINESS_SYSTEM" was not valid. Valid tokens: FOR SKIP WITH FETCH ORDER UNION EXCEPT OPTIMIZE.'.
    Thrown:
    com.sap.aii.af.service.api.AFException: XI AF API call failed. Module exception: (No information available). Cause Exception: 'Error processing request in sax parser: Error when executing statement for table/stored proc. 'table' (structure 'statement'): java.sql.SQLException: [SQL0104] Token "BUSINESS_SYSTEM" was not valid. Valid tokens: FOR SKIP WITH FETCH ORDER UNION EXCEPT OPTIMIZE.'.
    at com.sap.aii.af.service.api.AdapterAccess.sendMsg(AdapterAccess.java:214)
    at com.sap.aii.af.service.api.AdapterAccess.execute(AdapterAccess.java:283)
    at com.sap.aii.ibrun.server.lookup.AdapterProxyLocal.execute(AdapterProxyLocal.java:119)
    at com.sap.aii.ibrun.server.lookup.SystemAccessorInternal.execute(SystemAccessorInternal.java:76)
    at com.sap.aii.mapping.lookup.DataBaseAccessor.execute(DataBaseAccessor.java:74)
    at com.sap.aii.mappingtool.flib7.SelectSingle.selectSingle(SelectSingle.java:54)
    at sun.reflect.GeneratedMethodAccessor607.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:592)
    Any idea? Can high volume cause the JDBC Receiver to fail?
    Martin

    hi,
    you r trying to impliment Lookup for the file adapter which is not synch in nature and hance u r not getting the responce back.
    please find the link which deals with how to impliment lookup for file adapter.
    https://www.sdn.sap.com/irj/scn/wiki?path=/display/xi/file%252blookup%252bin%252budf.
    now once u get rhe runtime receiver u can perform enhanced receiver determination (write a simple UDF)
    regards,
    navneet.

  • File to RFC scenario - receiver determination problems

    Hi ,
    Im trying to work out a flat file to RFC scenario, and am facing problems in configuring the receiver determination .
    While creating my receiver determination, in the configured receivers, when i click on the F4 help to select service, i do not see the business system that i configured in SLD .
    This system i have configured as an WAS ABAP system and provided all relevant data. I can also import objects from this system into IR, so i dont think i have set it up wrongly. I have also created RFC destination .
    Is there some setting that has to be made that im missing ? Could somebody point out why im not able to see this system in the list of business services available at receiver configuration time ?
    Thanks,
    Joe
    I also cleared the SLD cache by the way.. that didnt work either .
    Message was edited by:
            Joe Stein

    Thanks a lot for you replies guys , but problems still not solved ;
    1. I looked at the blog given and ive done everything pretty much as given . My problem lies in not finding the business system itself  in the list of services for the configured receiver. How to implement this has not been shown in the blog.
    2. I tried refreshing the cache and checking again, but it still doesnt show me the necessary step.
    SOS !
    I checked in the inbound system , and found that an RFC wasnt created for the XI system . I created that but i still cant see this system as a business system when i try to create the receiver determination . Do i need to recreate the technical system in the landscape to incorporate this change ?
    Any pointers at all ??
    Message was edited by:
            Joe Stein

Maybe you are looking for