Extended receiver determination and Dynamic attributes

Hello,
is it possible to access dynamic attributes within an extended receiver determination? Can I modify / set dynamic attributes of an XI message within an UDF in the extended receiver determination mapping?
In detail: In my scenario I want to use an extended rec. determination, make a lookup in a DB inside the determination in order to define the receiver, and based on the lookup result I want to add some information as dynamic attributes to the XI message, which then can be accessed in the interface determination as conditions.
Thanks,
Chris

Hi,
In my scenario I want to use an extended rec. determination, make a lookup in a DB inside the determination in order to define the receiver, and based on the lookup result I want to add some information as dynamic attributes to the XI message, which then can be accessed in the interface determination as conditions - See you can do a DB lookup in a msg mapping........but by the time you have reached msg mapping your receiver determination will be done......so  your receiver is already decided............Extended recever determination is for dynamically choosing a recever based on source msg's data.........
Regards,
Rajeev Gupta

Similar Messages

  • Extended Receiver Determinatipon and Interface Determination?

    Hi,
    Where exactly (In which business cases) we can implement or required Extended Receiver Determination and Interface Determination?
    Thanks,
    Naidu.

    Hi,
    There are only two modes standard and Extended, Enhanced receiver determinatrion is Extended receiver determination only.
    Enhanced(Extended) receiver determination  -->
    Whenever list of receivers is determined dynamically at runtime, using a message mapping then it is called enhanced.
    Enhanced Interface Determination--> It is when you want the target interfaces to be defined dynamically based on the multimapping, that is called enhanced interface determination.
    Refre SAP help for more detail
    http://help.sap.com/saphelp_nw04s/helpdata/en/42/ed364cf8593eebe10000000a1553f7/frameset.htm
    Thanks!
    Edited by: Sudhir Tiwari on Dec 5, 2008 6:34 AM

  • Extended Receiver Determination problem

    Hi,
    I am making use of extended receiver determination to send 1 source to multiple target systems. When I was testing so that the interface would just send to 1 target system while still making use of the extended receiver determination, I got the following error CO_TXT_OUTBINDING_NOT_FOUND and "No receiver agreement found". The red flag error occurs during Technical Routing and when I checked the details SOAP Header -> Main, I found that the following:
    Sender Service: ServiceA (correct)
    Sender Interface: InterfaceA (correct)
    Sender namespace: NamespaceA (correct)
    Receiver Service: ServiceB (correct)
    Receiver Interface: InterfaceA (wrong)
    Receiver namespace: InterfaceA (wrong)
    It seems that extended receiver determination was able to successfully determine the receiver service but fail in determining the correct receiver interface and receiver namespace. Does anybody know why this happen and how to correct the problem?
    Some investigation that I already done:
    1.) I temporarily changed the extended receiver determination to a standard receiver determination and specifying the 1 target system explicity without changing any other object in both IR and ID as well as using the same test file. The result is that this worked and the file was sent succefully to my intended target system. This tells me that the problem might either be in the extended receiver determination or in the message mapping or message interface Receivers. Also, this means that all the other objects in ID for this interface is configured correctly.
    2.) I tried hard coding the target system as a constant in the message mapping for the Receivers message type and still make use of the extended receiver determination and I got the same problem mentioned above.
    3.) I tried deleting the receiver determination, activating the changes, re-create the object and activate it and I still got the problem
    4.) I tried checking sxi_cache and everything is up to date and correct
    Any suggestions is highly appreciated.

    Elbert,
    I you are doing only standard receiver determination only and using certain condition you are sending to different targets. If yes check this url:
    /people/prasadbabu.nemalikanti3/blog/2006/09/20/receiver-determination-based-on-the-payload-of-input-dataextended-xpathcontext-object
    Can you please put the payload after message mapping and the xpath condition you mentioned. or if you are doing enhanced receiver determination please check this:
    Re: Error in enhanced receiver determination
    ---Satish
    Edited by: Satish Reddy on Jun 23, 2009 9:08 AM

  • Extended Receiver Determination in 7.31 IDApi

    Hi,
    I'm using the 7.31 IDApi to create\change an ICO in 7.31 AEX. Currently this is working fine. However, I also need to create an ICO using the Extended receiver determination but I do not see ay function for this in the existing wsdls that SAP has provided.
    I have also referred to William Li's blogs for IDAPi for this.
    Using PI 7.3’s Directory API
    Could you please let me know if creating an ICO with Extended receviver determination from IDApi is possible and any pointers as to how it can be done would be very helpful.
    Regards

    Hi Shiladitya
    I can see that there is a option for dynamic receiver rule in the receiver determination of ICO.
    You can find the same in
    IntegratedConfigurationCreateChangeIn----> IntegratedConfiguration--->Receivers--->DynamicReceiverRule
    I am in 7.31 dual stack SP 07.

  • Error in Extended Receiver Determination

    Hello Experts,
    We are working on a scenario where, we are using Extended Receiver Determination.
    In this reveiver determination mapping we are doing JDBC lookup and some receivers are determined on that basis.
    Also, we have a default receiver in mapping.
    We are using: SAP PO 7.4 SP 7
    We are getting below error while testing from WSnavigator/SOAP UI, but mapping works when we test it in ESR.
    Error:
    <s:SystemError xmlns:s='http://sap.com/xi/WebService/xi2.0'>
              <context>XIAdapter</context>
              <code>ADAPTER.JAVA_EXCEPTION</code>
              <text><![CDATA[
    com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.xi.routing.RoutingException: Error while executing receiver determination mapping.
    at com.sap.aii.adapter.soap.web.SOAPHandler.processSOAPtoXMB(SOAPHandler.java:773)
    at com.sap.aii.adapter.soap.web.MessageServlet.doPost(MessageServlet.java:530)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
    at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:202)
    Kindly help.

    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.

  • Want to Use Extended Receiver Determination

    Dear All,
    As my last post I came to know that i was using invaild data in input payload so i now have tested with proper data.
    i am getting lot of invaild things in my input like space ,# and all from ECC side in first step of pipeline(Receiver Determination). so thinking to use extended reciver determination so that there i can validate the input paylaod there only..........is this possible
    Plz suggset.....
    Regards
    Abhay Agarwal

    Hi Abhay,
    As i read the all the posts in this thread.. and ur error status is..
    <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
    <SAP:Category>XIServer</SAP:Category>
    <SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
    <SAP:P1 />
    <SAP:P2 />
    <SAP:P3 />
    <SAP:P4 />
    <SAP:AdditionalText />
    <SAP:ApplicationFaultMessage namespace="" />
    <SAP:Stack>No receiver could be determined</SAP:Stack>
    <SAP:Retry>M</SAP:Retry>
    </SAP:Error>
    This problem is not from the mapping which will be in interface determination... also,
    the mapping(interface determination) comes only after the receiver determination...
    So the problem lies in the receiver determination configuration....
    please delete the receiver determination once and recreate it once more(some times due to cache problem's)
    For ur requirement dont create the extended receiver determination...(it's required only when u want to determine the receivers in run time)
    To delete the spaces and special chars...
    u can solve these in mapping,using the stringReplace and trim functions....
    Also i doubt if at all the incoming source XML is proper structure or not... please check once in the SXMB_MONI.. the incoming payload.
    Still some problem... please post the problem in detail .. so that others can also understand..
    Babu

  • Extended Receiver Determination

    Hi
    I have scenario like this.
    Sending order file into SAP through XI
    If the order is there in SAP it needs to be send mail along with details of
    order else if this is new order then it needs to posted into SAP and create IDOC .I need to use RFC function module which is developed in SAP that returns 0 or 4
    If SUBRC=0 then need to send mail as I mentioned above
    If SUBRC=4 then need to create Idoc in SAP system.
    Note : without BPM - Need a solution
    Let me know how to use extened Receiver determination.
    Till now I have designed like this:
    In the IR :
    I have created 3 message mappings for this.
    1st one is to decide receiver.
               Source - file
               Target -  Receiver determination (structure - which available in SAP
    Basis software componenet)
    2nd one is to create IDOc
                Source - file
                 Target - Idoc
    3rd one is to create mail
                Source - file
                Target - Mail ( External defination)
    In ID:
    I am using extended receiver determination , their i have given the mapping program which ti determine the receiver.
    Next i have created 2 Interface Determinations,Sender as well as Receiver agreements.
    Finally Activated all .
    While testing i am getting message in the MONI No Receiver agreement found
    Could pls help this case.
    Cheers
    MMV

    Hi Mrutynjaya,
    Rest all seems to be fine, but are you using 2 sender agreements??? You need only 1 sender agreement,as you have only 1 sender. Correct me if i am wrong.
    Regards,
    Sanjeev.

  • Receiver Determination and Interface Determination

    Hi,
    Please, can anyone explain what is the concept of 'Receiver determination' and 'Interface Determination'?
    Thanks,
    Harikumar. S

    Hi,
    >>>>Receiver determination
    its about finding the receiver system for particular source system and outbound interface.
    Suppose,you want to send data from file->XI->SAP and CRM based on some condition
    in this scenario you need to determine whether to send file data to SAP or CRM system,this decision you will do in Receiver determination
    in Receiver determination screen you need to provide the following details
    1.Source system(ex: File system)
    2.Outbound Interface(File Message Interface)
    3.condition and receiving system(ex:if some x field value in source payload is 1 go to SAP elseif '0' go to CRM system)
    >>>>>>Interface Determination
    suppose in above scenario you determined the receiver i.e SAP,you will have number of IDOCs (Inbound Interfaces)in SAP.
    so to which IDOC you will send file data?This decision you will make in Interface determination(we can it as Inbound Interface determination).if you find the IDOC is CREMAS then how will transfer file structure data to IDOC structure? answer is Message Mapping
    From all the above decisions you need to provide following details in Interface determination screen
    1.Source System
    2.Outbound Interface
    3.Receiver System
    4.Inbound Interface(IDOC type)
    5.Message Mapping(i.e file to IDOC)
    Even in Interface determination you can specify the condition to select Inbound Interfaces(ex.IDOCs)
    if you have any doubts please lets know.
    Cheers,
    Jag

  • Extended Receiver Determination option missing

    Hi All,
    In the Receiver Determination the extended receiver determination option is missing. We are on PI 7.0. I would like to know as to which patch level i need to upgrade it to see this option.
    Thanx for all your help in advance
    Regards,
    Abhy

    hi,
    you need to go for: SPS07 which is SP16 in 3.0
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

  • Multiple targets using extended receiver determination

    Hello,
    One quick question related to extended receiver determination
    for same receiver 4 conditions exists.
    at the same time 3 can become true.
    will the extended receiver determination has the capability to create 3 records for the same receiver depending on the condition?
    if cond1 -->> target1
    if cond2 -->> target1
    if cond3 -->> target1
    if cond4 -->> target1
    ( I am using ext interface determination so that my message inputs to receiver determination is also many )
    but now when  I execute, its executing only first condition n generating records generated with the first condition only.
    regards,
    nikhil.

    im using extended receiver determination n giving 4 diff conditions as inputs to the receiver.
    however, thanks...
    answer is you can do it
    its working

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

  • Question regarding Receiver Determination and Differente Namespaces

    Dear sirs,
    I have the following scenario:
    I have a mail account read by a sender communication channel IMAP4 in namespace http://a. The message is sent to a receiver communication channel type XI delivering to an ABAP Proxy at the same namespace. Everything works fine here.
    I need to split the route: Reading the same mail account and depending on the message received send it to an ABAP Proxy of namespace http://A or namespace http://B. The receiver determination does not allow to configure destinations of different namespaces.
    Please someone could give me an idea how to solve this issue?
    Thank you in advance.
    Fabio Purcino

    Hi,
    I have already two receiver agreement and two mapping programs but I'm not able to set these programs on interface mapping  because it's on a different namespace.
    I attached a image of my interface determination configuration.
    [http://img683.imageshack.us/img683/7909/imagenamespacepi.jpg]
    Best Regards,
    Fabio Purcino

  • Dynamic ALV with Static and Dynamic attributes

    Hi All,
    In my requirement we have some 5 static attributes and rest attributes needs needs to be dynamically created based upon the input selections. for eg my input for start date and end date is between 201023 to 201152 then weeks between this range should apear as dynamic columns.
    i am able to create a dummy alv table display with out populating data into it but unable to set the data to it . Kindly help me in solving this issue.
    Regards,
    Sana.

    You might have created a dynamic node, bind the data to this node and after that use the SET_DATA method of ALV interface controller to set the data by passing the dynamically created node.

  • Tables for Receiver Determination and Receiver agreement

    Hello Experts,
    Is anyone aware if there is a some table which gets updated whenever we create a receiver determination or receiver agreement in PI. If possible can you guys give me the table names.
    Thanks in advance,
    ~ Suraj

    hi Suraj,
    SAP XI is built having two stack the abap and the java stack. Its not all that correct that only cache info resides on the java stack and nothing on the abap stack.... Its like black box and the internal workings are hidden from end users ... only sap would be able to tell you. As someone in this thread has given his point of view that only cache info is stored on the java stack which may be correct but how much so is open to debate. I wonder whether you have played around with the table that you come across with the transaction sara.
    Suggestions are most welcome
    Regards
    joel

  • Enhanced receiver determination and value mapping

    I want to use enhanced receiver determination functionality in my scenario.
    I couldn't see any message interface or data type under http://sap.com/xi/XI/System.
    we are on Sp08 nw04s and SAP BASIS 7.0 software component in IR.
    I don't want to hard code my business service name in mapping.How can I achieve this?
    Thanks,
    Rekha.
    Message was edited by:
            Rekha Lather

    Hi,
    ><i> couldn't see any message interface or data type under http://sap.com/xi/XI/System.
    we are on Sp08 nw04s and SAP BASIS 7.0 software component in IR.</i>
    After upgradation to SP08 on NW04s , did you reimport the SAP BASIS Component into your IR? Ask your basis admin team to reimport the SAP basis Component into the IR.
    ><i>I don't want to hard code my business service name in mapping.How can I achieve this?</i>
    Similar discussion available in the comments section of this blog,
    /people/venkataramanan.parameswaran/blog/2006/03/17/illustration-of-enhanced-receiver-determination--sp16
    Would suggest you use value Mapping.
    Regards
    Bhavesh

Maybe you are looking for