Receiver Determination Transport

Hi,
We have a case where we have multiple reciver for same IDOC in PI based on diff partner number.
The problem that we are facing, each time we add a new receiver and transport the reciever determination as a part of scenario, it over writes the receiver determination with the values from DEV environment.
One solution that we are using as of now is to manually, copy the values from existing RD before we activate it again on transport.
But this has drawback that since our PI usage is more so more partners are coming on board and we cannot do that each time we have new interface going live.
Is there an y solution that we can transport only change in the reciver determination.
Any help will be appreciated.
Thanks
-Kulwant

u have to create system groups and transport targets in SLD
this will state teh mapping between the dev and corresponding test business systems..
once u have done this properly ...and u import the TPZ files of IR & ID ..the ID in test will automatically reflect the new business systems corresponding the test environment
everytime u have an addition of a business system in the RD in dev ....just update the SLD with the new target and then transport the scenario...the test will then reflect the proper system
http://help.sap.com/saphelp_nw04/helpdata/en/ef/a21e3e0987760be10000000a114084/content.htm
Edited by: Tarang Shah on Feb 3, 2010 10:29 PM

Similar Messages

  • ACK for receiver determination with 2 interface determination

    Hi Forum,
    I have a XI scenario, with a BPM, where i have a Send step,
    this send step corrsponds to a receiver determination in Configuration,  and this receiver determination has 2 interface determination,
    because the send step is like,
    BPM to Receiver1, through sender message interface MI_Sender1, but there are 2 different receiver message interface namely MI_receiver1, and MI_receiver2,
    .......hence 2 interface determination and 2 interface mappings accordingly,
    and now when in BPM, i choose "transport acknowledgement" for this send step, my BPM stucks while waiting for the acknowledgement, but...in MONI, i am receivng both the acknowledgement, but in PE, workflow descrition, it waits for acknowledgement and finally fails,
    what's the reason,

    check the workitems of both sender/receiver (ack) in moni (problem might be in BPM config).

  • Using SHeaderFROM in mailsender CC and in receiver determination

    Hi
    I am using a mailsender adapter where I need to send messages from one particular sender adress to one folder and messages from other senders to an other folder.
    In my mailsender communication channel I am using the AF_Modules/PayloadSwapBean module as the message comes as an attachment. In my receiver determination I am using the SHeaderFROM in this fashion:
    SHeaderFROM u2260 8716867999 xxxorg
    SHeaderFROM = 8716867999 xxxorg
    However, that is not working and even though I select the "Set Adapter Specific Message Attributes" in the mailsender communication channel I cannot see the SHeaderFROM value in the ABAP monitor under "DynamicConfiguration".
    What can I do?
    BR Mikael

    Hi,
    you can use UDF in mapping, like this
       //write your code here
         //Fabio Boni:- UDF for generating the mail parameters from & to
      String valueFrom = "XXXXXX.com";
      String Mail_address_to = "XXXXXX.com";
    DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
    DynamicConfigurationKey key1 = DynamicConfigurationKey.create( "http://sap.com/xi/XI/System/Mail",  "THeaderFROM");
    DynamicConfigurationKey key2 = DynamicConfigurationKey.create( "http://sap.com/xi/XI/System/Mail",  "THeaderTO");
    DynamicConfigurationKey key3 = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/File","FileName");
    conf.put(key1, valueFrom);
    conf.put(key2, Mail_address_to);
    conf.put(key3,Attachment_name);
      return  "";
    and then in CC put "XHeaderName1" in MailAttributeFrom and "XHeaderName2" in MailAttribute2.
    Flag ASMA e Variable Transport Binding in tab Advanced.
    go through this:
    filling Mail subject , to en from using a user defined function
    Edited by: Fabio Boni on Apr 5, 2011 2:23 PM

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

  • Conditions in Receiver Determination

    Hi
            I am doing a scenario in which we are sending PO from R3 to one of two different web-services through XI using RFC.We have already transported our scenario to Production.Using RFC we are executing Webservice.
            Now there on production we want to put conditions in receiver determination according to message data. In F4 help of condition it is not showing message feilds so I filled condition manually but it is not woking. Is there any other way to put conditions there?
           Have anyone face this problem?
           what is the soution of this problem.
           Its urgent!!
    thanks in advance
    Regards
    Sami
    Message was edited by:
            sami qureshi

    Hi Sami,
    Strongly suggested: Do the changes in Dev and re-transport.
    in dev u may create a context obj and assign that to ur msg interface. and use this context obj for conditional routing.
    Hope it helps.
    Regards,
    Latika.

  • Enhanced Receiver Determination - Hard-coded Receivers??

    Hi mates,
    I need to implment enhanced receiver determination. I see from the documentation and blogs that I need to hard-code the receiver service i.e. specifying the value in message mapping.
    What happens if I transport this mapping program to QA or PROD system? Do I need to take care of the Receiver system names in QA & PROD in the mapping.
    Isnt it hard-coding?
    Is there any better way of doing this, apart from using the BPM.
    I appreciate your inputs.
    thx in adv
    praveen

    Hi,
    If you are using enhanced receiver determination, you are going to provide Receiver Details in the Integration Directory right ? If so, anyway while doing Transport from the Dev to QA, you are creating a Transport Target for the business systems.. So here in the configuration it will take care ...
    http://help.sap.com/saphelp_nw2004s/helpdata/en/ef/a21e3e0987760be10000000a114084/content.htm
    But, I am not sure where are you refering about  Hard-Coding ?
    Rgds,
    moorthy

  • Receiver determination step in the BPM and multiline container

    i have made a file2file scenario where:
    there is a BPM,
    the BPM has a send step which contains a receive step,
    a transformation that mapps the incomin message to two messages(Split-messgae case),
    and then a FORK step which sends the two messges to through 2 SEND steps to the intended receiver services.
    It didnt work......and i followed a blog->  /people/sudharshan.aravamudan/blog/2005/12/01/illustration-of-multi-mapping-and-message-split-using-bpm-in-sap-exchange-infrastructure   ............... which suggested to have a
    "receiver-determination" step in the BPM before the SEND step.... it says that this
    "receiver-determination" step will put the message in a MULTILINE container..
    i m confused bout this step ........ can anybody explain.....
    please help

    HI,
    In receiver determination step selctthe multi line container element.in container editor create the one element with type as receiver and select the check box.
    A Receiver Determination step returns set of receivers configured for the output abs interfaces in the directory and puts it into receiver which is a multiline container receiver element
    Regards
    Chilla

  • Regarding receiver determination problem in IDOC-XI-XML file scenario

    Dear All ,
    In IDOC-XI-xml file scenario , I have configured SLD , IR . But in ID , after file adapter , reciever agreement configuration when I am doing receiver determination configuration I am not able to insert mapping program in configuration overview of receiver determination as I am not getting "New Specific" option in mapping .
    Can anybody suggest what could be the reason behind this .
    Thanks in Advance
    Prabhat

    Hi PRabhat,
    In RCVR determination, you need to select the party & service (as appropriate) save the obeject
    then refresh the configuration overview of recr det.
    then you can see the partner/service
    then you can open it & add the necessary objects.
    Regards
    Vishnu

  • How to get a dynamic receiver determination based on a table an SAP PI ABAP Stack

    Hello folks,
    currently I get stuck dealing with a problem about the receiver determination. Let me first describe the Problem: We are using to different SAP ERP- backend system in our test enviroment. But only of this systems is marked as current "actuall" test system. Every once in a while we need to switch between these two systems and mark the other one as the actual test system.
    This is the point were it get's a little bit time consuming for me: We have about 50 interfaces were I need to change the receiver from test system A to test system B or vice versa. So I thought about creating a more dynamic way to determine the actual test system:
    Therefore I have created a table on the ABAP stack of our PI (7.31 double stack) with just one field that holds the current test system. Now I would like to create a dynamic receiver determination where I call the RFC-function RFC_READ_TABLE. But how can I acess a table from the grapchical mapping of the pi which is stored on the PI?
    Is there mybe another fundamental way to retrieve the actuall test system within the mapping?

    You can go for enhanced receiver determination, where in you can determine the receiver system using a graphical mapping.
    Now in that graphical mapping, use the standard function " RFC Look up" and make a call to bapi and get the actual receiver system.
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/40b64ca6-b1e3-2b10-4c9b-c48234ccea35?QuickLink=index&…
    Step by Step guide to Explain Enhanced Receiver Determination - Application Server Infrastructure - SCN Wiki

  • 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

  • Multi Mapping using condition & Dynamic Receiver determination – Used XSLT Mapping

    Dear Experts,
         I am struggling to identify an error on the Technical Routing. Firstly according to my scenario, I receive an XML file with multiple PO's and I have to split the file to 2 different target messages. and also according to the source payload I have to send the file to 2 different receivers. first receiver is ABAP Proxy to the back end system and the 2nd one is to a file location. I have used XSLT to split the message into 2 target message type and I have used a XSLT mapping for receiver determination. Does any one have any idea of what I am doing wrong.
    Note: some time I will only be able to fill in on target message.
    I have attached my XSLT message split mapping with this post, please let me know if you have further question.
    Your help is more appreciated.
    Advance Thanks,
    Pradeep
    <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:sap="http://www.sap.com/sapxsl" version="1.0">
      <xsl:variable name="vFlag"/>
      <xsl:variable name="vPONUM" select="POTRACKING/Lines[1]/PONumber"/>
      <xsl:template match="/">
        <ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">
          <ns0:Message1>
            <ns1:MT_Tracking xmlns:ns1="http://www.findel-education.co.uk/axapta">
              <xsl:for-each select="POTRACKING/Lines">
                <sap:call-external class="ZCL_VNAP_OBJECTS" method="CHECK_PO_EXIST">
                  <sap:callvalue param="IP_EBELN" select="string(PONumber)"/>
                  <sap:callvariable name="vFlag" param="EP_BOLEAN" type="string"/>
                </sap:call-external>
                <xsl:if test="$vFlag = 0">
                  <Lines>
                    <DDate>
                      <xsl:value-of select="DespatchDate"/>
                    </DDate>
                    <PONumber>
                      <xsl:value-of select="PONumber"/>
                    </PONumber>
                    <POLine>
                      <xsl:value-of select="POLine"/>
                    </POLine>
                    <QTY>
                      <xsl:value-of select="Quantity"/>
                    </QTY>
                    <VendorMaterial>
                      <xsl:value-of select="VendorMaterialNumber"/>
                    </VendorMaterial>
                    <AccountRef>
                      <xsl:value-of select="AccountReference"/>
                    </AccountRef>
                    <ConsignNumber>
                      <xsl:value-of select="ConsignmentNumber"/>
                    </ConsignNumber>
                    <CarrierURL>
                      <xsl:value-of select="CarrierURL"/>
                    </CarrierURL>
                    <ConsignURL>
                      <xsl:value-of select="ConsignmentURL"/>
                    </ConsignURL>
                  </Lines>
                </xsl:if>
              </xsl:for-each>
            </ns1:MT_Tracking>
          </ns0:Message1>
          <ns0:Message2>
            <ns2:MT_Tracking xmlns:ns2="http://www.findel-education.co.uk/ecc/ax/po/ftp">
              <xsl:for-each select="POTRACKING/Lines">
                <sap:call-external class="ZCL_VNAP_OBJECTS" method="CHECK_PO_EXIST">
                  <sap:callvalue param="IP_EBELN" select="string(PONumber)"/>
                  <sap:callvariable name="vFlag" param="EP_BOLEAN" type="string"/>
                </sap:call-external>
                <xsl:if test="$vFlag = 1">
                  <Lines>
                    <DDate>
                      <xsl:value-of select="DespatchDate"/>
                    </DDate>
                    <PONumber>
                      <xsl:value-of select="PONumber"/>
                    </PONumber>
                    <POLine>
                      <xsl:value-of select="POLine"/>
                    </POLine>
                    <QTY>
                      <xsl:value-of select="Quantity"/>
                    </QTY>
                    <VendorMaterial>
                      <xsl:value-of select="VendorMaterialNumber"/>
                    </VendorMaterial>
                    <AccountRef>
                      <xsl:value-of select="AccountReference"/>
                    </AccountRef>
                    <ConsignNumber>
                      <xsl:value-of select="ConsignmentNumber"/>
                    </ConsignNumber>
                    <CarrierURL>
                      <xsl:value-of select="CarrierURL"/>
                    </CarrierURL>
                    <ConsignURL>
                      <xsl:value-of select="ConsignmentURL"/>
                    </ConsignURL>
                  </Lines>
                </xsl:if>
              </xsl:for-each>
            </ns2:MT_Tracking>
          </ns0:Message2>
        </ns0:Messages>
      </xsl:template>
    </xsl:stylesheet>

    Hi Hareesh,
    Please find my determination in the XSLT below, I am using enhanced receiver determination.
    <xsl:transform xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:sap="http://www.sap.com/sapxsl" xmlns:p1="http://sap.com/xi/XI/System" xmlns:ns="urn:sap-com:document:sap:idoc:messages" version="1.0">
      <xsl:variable name="vFlag"/>
      <xsl:variable name="vAX" select="0"/>
      <xsl:variable name="vSAP" select="0"/>
      <xsl:variable name="vBoth" select="0"/>
      <!--  <xsl:variable name="vPONUM" select="POTRACKING/Lines[1]/PONumber"/>-->
      <xsl:template match="/">
        <xsl:for-each select="POTRACKING/Lines">
          <sap:call-external class="ZCL_VNAP_OBJECTS" method="CHECK_PO_EXIST">
            <sap:callvalue param="IP_EBELN" select="string(PONumber)"/>
            <sap:callvariable name="vFlag" param="EP_BOLEAN" type="string"/>
          </sap:call-external>
          <xsl:choose>
            <xsl:when test="$vFlag = 0">
              <!--          <p1:Receivers>
                <Receiver>
                  <Service>
                    <xsl:text>BS_AXAPTA_TST</xsl:text>
                  </Service>
                </Receiver>
              </p1:Receivers>-->
              <xsl:variable name="vAX" select="$vAX + 1"/>
            </xsl:when>
            <xsl:when test="$vFlag = 1">
              <!--          <p1:Receivers>
                <Receiver>
                  <Service>
                    <xsl:text>BS_ECQCLNT300</xsl:text>
                  </Service>
                </Receiver>
              </p1:Receivers>-->
              <xsl:variable name="vSAP" select="$vSAP + 1"/>
            </xsl:when>
          </xsl:choose>
        </xsl:for-each>
        <xsl:if test="$vSAP &gt; 0">
          <xsl:if test="$vAX &gt; 0">
            <xsl:variable name="vBoth" select="$vBoth + 1"/>
            <xsl:variable name="vSAP" select="0"/>
            <xsl:variable name="vAX" select="0"/>
          </xsl:if>
        </xsl:if>
        <xsl:if test="$vBoth &gt; 0">
          <p1:Receivers>
            <Receiver>
              <Service>
                <xsl:text>BS_AXAPTA_TST</xsl:text>
              </Service>
            </Receiver>
            <Receiver>
              <Service>
                <xsl:text>BS_ECQCLNT300</xsl:text>
              </Service>
            </Receiver>
          </p1:Receivers>
        </xsl:if>
        <xsl:if test="$vAX &gt; 0">
          <p1:Receivers>
            <Receiver>
              <Service>
                <xsl:text>BS_AXAPTA_TST</xsl:text>
              </Service>
            </Receiver>
          </p1:Receivers>
        </xsl:if>
        <xsl:if test="$vSAP &gt; 0">
          <p1:Receivers>
            <Receiver>
              <Service>
                <xsl:text>BS_ECQCLNT300</xsl:text>
              </Service>
            </Receiver>
          </p1:Receivers>
        </xsl:if>
      </xsl:template>
    </xsl:transform>

  • File name based routing in Receiver determination

    Hi experts,
    I have a requirement to do receiver determination based on file names which are dynamic.To put it clearely, i will be having two files in my source File location and i need to route it based on the file name to two target systems.
    The file name are like Month(changes everymonth)_TargetSys1 and month_targetSys2.
    I dont need any conversions ,so i am not using any IR objects.
    To pick files i kept *.txt in sender channel, and in receiver determination  condition i was trying to use context object called 'Filename'.But it doesnt work asthe file name changes every month.
    Is there any option to take substring from the input file name (say targetSys2 from month_targetSys2.) and put it as a condition for receiver determination.
    There is not DT or structure of the incoming file , as there are no modification to be done with the content.
    Regards,
    Anika

    you need to have the structure in case you want to route it via the xpath.
    Else another option is to code the enhanced receiver determination and using a java mapping with dynamic configuration read the filename and then dynamically create the receiver determination.
    http://help.sap.com/saphelp_nw04/helpdata/en/43/a5f2066340332de10000000a11466f/content.htm

  • How many Receiver determination in File to SOAP scenario

    Hi,
    I am trying a File -SOAP-File scenario, where file will be send to PI asynchronous. BPM is configured to receive the file and
    call the web services and get the response (Synchronous call) .After that BPM send the file asynchronous to File via FTP .
    It is basically asynchronous/ Synchronous bridge scenario.
    To do this I have  have configured the BPM  & created 3 Communication channel . 1 sender (File) & 2 receivers ( SOAP & File)
    But i got confused in Receiver determination. How many Receiver determinations do we require in this step?  2 or 3. If 3 how they will look like. I believe Interface determination is same as Receiver determination. I am suing Business System to send & recv the file.
    Points will be rewarded for suitable answer.
    Thanks

    hi,
    You require 3 receiver determinations.
    one from File to BPM(XI)..
    another from BPM to SOAP and other from SOAP to FILE.
    This is exactly the same scenario.
    RFC Scenario using BPM --Starter Kit
    Thanks,
    Vijaya

  • Receiver determination in BPM ..what is used for?

    Hi everyone.
    I've never used 'receiver determination' step in a BPM. I want to know what is used for.
    Regards,
    Inigo.

    you can ref: this link to find example where a receiver determination step is used in BPM- http://help.sap.com/saphelp_nw04/helpdata/en/43/6211b11c895f6ce10000000a1553f6/content.htm
    More abt RD step in BPM - http://help.sap.com/saphelp_nw04/helpdata/en/14/d5283fd0ca8443e10000000a114084/content.htm

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

Maybe you are looking for