Dynamic receiver Determination for Sync Scenario??

Hello Experts,
I have a SOAP -> Xi -> R3 sync scenario i,e, R3 to send back response to SOAP client.
Also I need the Dynamic receiver determination.
When I try to create the Interface Mapping, I get the error:
"Interface modi are different. "
Source interface MI_My_sync_iface is synchronous.
Target interface ReceiverDetermination | http://sap.com/xi/XI/System is asynchronous
I coud find few threads on forum related to this but i think there is no clear solution provided.
I do not wanna use BPM.
Please suggest.
Thanks in Advance!
Appropriate point will be awarded.

> So when I try to define a interface Mapping using a Sync interface as Source and Async interface as target, XI does not allow me to do so.
You are getting this error because in Interface mapping when you use sync source then it generates request and response tab so if at target side if you put anync interface then definetly it will go into error. You have to make both the interfaces as sync.
BTW, after getting the message in R3, how are processing the message? Are you using sync proxy??
You can solve the problem by creating one additional message interface of type inbound-asyn. Use this additional Message interfce in your Interface Determination. And create additional Receiver Agreement to deliver the message to it's destination.
Note: When you careate additional Interface Determination then you have to chose the response message interface (Sync message interface which returns the response from R3) as a source.
Regards,
Sarvesh

Similar Messages

Dynamic receiver determination for synchron interface

Hello everybody,
I want to use dynamic receiver determination for a synchron scenario.
The problem is, that the interface 'ReceiverDetermination' (http://sap.com/xi/XI/System SAP BASIS 7.00) is a asynchron interface.
This leads to an error when activating the Interface-Mapping (synch source Interface -> asynch destination Interface ReceiverDetermination)
Is there a way to use the dynamic receiver determination for synchron interface?
Thanks a lot,
Thomas

Hi Thomas,
I guess your scenario is not possible ASIS, since XI doesn't support 1:n for sync interfaces (and even if your mapping condition reduces it to 1:1, actually it is still 1:n, since your receiver list is unbounded).
Theoretically, you could make it work with BPM, though.
But I've never worked with a Receiver Determination Step reading from an enhanced receiver determination in ID (though there should be no problems).
Use sync async bridge, then use receiver determination step to obtain the receiver from an enhanced Receiver Determination. Pay attention that this enhanced receiver determination is a dummy one, using a mapping from your async abstract interface to the ReceiverDetermination interface. Once your mapping has determined the receiver, the enhanced receiver determination will return that receiver to the Receiver Determination step in the BPM. Then use this receiver in the sync send step (in mode receiver from receiver list, not from context).
The receiver determination of the actual sync send step may be a standard one, with the several receivers there (even if there are several there, at the moment of the sending, only one will be used).
Maybe it will work, maybe not.
Just try it.
Regards,
Henrique.

Enhanced Receiver Determination for synchronous interface.

Hello!
Was anyone faced with the Enhanced Receiver Determination? When I try to create
the definition of the Interface Mapping, I get the error:
"Interface modi are different. Source interface Message Interface MI_My_sync_iface | urn:my is synchronous. Target interface Message Interface ReceiverDetermination | http://sap.com/xi/XI/System is asynchronous"
Thank you.

Hi ,
U can go through below limks :
Illustration of Enhanced Receiver Determination - SP16
SAP NetWeaver Process Integration: Enhanced Receiver Determination for Synchronous Scenarios
Enhanced Receiver Determination in SAP XI - Exchange Infrastructure - Wiki
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/enhanced%2breceiver%2bdetermination%2bin%2bsap%2bxi
Thanks

Enhanced Receiver Determination in Synchronous Scenario

Hi,
my synch scenario with standard Receiver determination is working fine.
the service interfaces i used are SI_OutSynch_EmpInfo_Request and SI_InbSynch_EmpInfo_Provide.
I am now trying to apply enhanced Receiver determination for the same synch scenario.
For this, in ID, in my Receiver Determination object i selected the radio button Extended, then it is asking for an operation mapping. infact it is asking for an OM with sender Interface=SI_OutSynch_EmpInfo_Request (from my swcv) and Receiver Interface = ReceiverDetermination (from SAP BASIS swcv)..
So I logged into ESR, and created an OM_test_EnhancedRD, with sourceInterface=SI_OutSynch_EmpInfo_Request (from my swcv) and TargetInterface = ReceiverDetermination (from SAP BASIS swcv)
But when i tried to activate the OM_test_EnhancedRD, it is not getting activated, and giving below error:
Interface modi are different. Source interface Operation SI_OutSynch_EmpInfo_Request | http://mycomp.com/myns is synchronous. Target interface Operation ReceiverDetermination | http://sap.com/xi/XI/System is asynchronous
So my queries are:
1. is for synch scenarios, if receiver information is part of the request payload, how can we apply the extended Receiver Determination, so that the Receiver is determined dynamically.
2. or is there any synch version of ReceiverDetermination (from SAP BASIS swcv) available.
thanks in advance.
madhu.

in this case, does SAP provide synch version of ReceiverDetermination SI, so that we can use that in OM for enhanced Receiver Determination.
If you have a look at the blog-reference given by Ravi you will find a way on how to make the ReceiverDetermination Si synchronous or work with the same async SI.....for quick reference below is the way mentioned in the blog:
From the blog:
Option 1:
A quick and easy way to allow for synchronous enhanced receiver determination setup is to circumvent the check that prevents
a synchronous interface to be matched to an asynchronous interface in an interface mapping. This can be done simply by
manually entering the name and namespace of the ReceiverDetermination interface object (e.g. 'ReceiverDetermination'
and 'http://sap.com/xi/XI/System' respectively) for the target/receiver interface in the interface mapping, but leaving the value for
the Software Component Version empty.
Option 2:
Select Modify and then change the mode to synchronous. Since a synchronous interface requires an input message as well, you
can reuse the Receivers message type used in the output message - it doesn't really matter as long as some message type is
used.
Both of the above options are available under the Applying the Workarounds section of the blog
Regards,
Abhishek.

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

Receiver Determination for Integration Process - R/3

Hi,
While creating the receiver determination for the BAPI, how to specify the BAPI name in the Receiver (Partner) Service .
I found an example in SDN Blog, however, it did not clear my doubt.
/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
Kindly, reply me.
Regards,
dinesh.

>
Dinesh Kumar wrote:
> Hi,
>
> While creating the receiver determination for the BAPI, how to specify the BAPI name in the Receiver (Partner) Service .
>
> I found an example in SDN Blog, however, it did not clear my doubt.
>
> /people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
>
> Kindly, reply me.
>
>
> Regards,
>
> dinesh.
did you import the BAPI?
Your receiver system will be the SAP BS. when you use the f4 help option for the interface it will list the BAPI and u can select it

Can't see messages on sxi_monitor for sync scenario?

Hi gurus,
We are using PI 7.11. We found after no operation for ESR or ID for a long time, the system pops up the error "no authorization...", then we have to click esr on pi main page and logon again. Is there any parameter to change the user session or somthing?
Thanks in advance.

your subject line seems different to the issue you are having...
or they could be the same! have you set the messaging logging for sync scenarios in SXMB_ADM?
can you explain the actual problem you are having? it makes no sense.

Dynamic Receiver Determination using Soap header

Hi ,
I am trying to use a field in SOAP Header to determine the receivers dynamically.
1, Using XPATH gives me only values in the Payload and not the SOAP header. Is it possible to pull the value from the SOAP header to the payload and then do dynamic receiver determination.
2. Using Context Object is it possible to transfer the value of the field in SOAP header to variable header Xheadername1 and then use it to determine the receiver. I am having problems in passing the value of the field in soap header to XHeadername1.
Any help is appreciated and points will be awarded.
Joe Vellaiparambil

Hi Joe,
This is a good blog by William, hope this is helpful.
/people/william.li/blog/2009/07/30/how-to-read-soap-header-information
Let us know if you need more information.
Regards,
Neetesh

Dynamic Receiver Determination [W/O using BPM] Sync interface

I have been exploring options w.r.t. performance sensitive service interface.
This has following issues :
1. Gets a org code looking up instance and route the msg. accordingly to an RFC and get response back.
2. Prominent answer would be Enhanced receiver determination step but that doesnt work in sync case.
3. Classic Receiver Determination needs the condition to be evaluated in source msg. which is not going to happen.
4. Use BPM i designed one but performance its not all acceptable it has a round trip of 10Sec.
are there any ways to overcome this ?

Hi Bujji,
can you explain the point 1.
<i>1. Gets a org code looking up instance and route the msg. accordingly to an RFC and get response back.</i>
Thanks and Regards,
Himadri
null

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: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">
          
          <xsl:variable name="vAX" select="$vAX + 1"/>
        </xsl:when>
        <xsl:when test="$vFlag = 1">
          
          <xsl:variable name="vSAP" select="$vSAP + 1"/>
        </xsl:when>
      </xsl:choose>
    </xsl:for-each>
    <xsl:if test="$vSAP > 0">
      <xsl:if test="$vAX > 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 > 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 > 0">
      <p1:Receivers>
        <Receiver>
          <Service>
            <xsl:text>BS_AXAPTA_TST</xsl:text>
          </Service>
        </Receiver>
      </p1:Receivers>
    </xsl:if>
    <xsl:if test="$vSAP > 0">
      <p1:Receivers>
        <Receiver>
          <Service>
            <xsl:text>BS_ECQCLNT300</xsl:text>
          </Service>
        </Receiver>
      </p1:Receivers>
    </xsl:if>
</xsl:template>
</xsl:transform>

Receiver determination for Split Message - Bulk message handling

All,
I have a scenario where MATMAS message is split to multiple receivers via multi mapping 1:n; the split is based on plant specific data, all works fine the mapping splits the message perfectly.
The problem I have is in configuring the receiver determiniation. I have put conditions based on plant specific data the message should be distributed to the appropriate receiver. At runtime the MATMAS message received is treated as a bulk message and it produces mutiple sub-documents however in my case if the MATMAS has 3 plant specific data the data is send to all the 3 receivers instead of sending just one message per plant to the appropriate receiver.
Its IDOC to File scenario on XI 3.0, SP20.
Receiver Determination:
/MATMAS05/IDOC/E1MARAM/E1MARCM/WERKS = 'xxxx' -> send to XXXX_receiver
/MATMAS05/IDOC/E1MARAM/E1MARCM/WERKS = 'yyyy' -> send to YYYY_receiver
Though the receiver determiniation splits the message by plant it could be that a material is maintained for both xxxx and yyyy plants and in this case both should receive the message but the contents would be different. The problem I have is both messages are delivered to both receivers.
I appreciate those who have taken the time to read the thread and thank you all in advance supporting with advices.
/ Saj

Please find attached the source xml before transormation used for the xpath that I have indicated in my original message. From the below message E1MARCM-BESKZ differs on each plant and also has a corresponding warehouse view E1MLGNM where for example LHMG1 value differs for each warehouse.
<?xml version="1.0" encoding="UTF-8" ?>
- <MATMAS05>
- <IDOC BEGIN="1">
- <E1MARAM SEGMENT="1">
<MSGFN>005</MSGFN>
<MATNR>000000000001002201</MATNR>
<MTART>ZFGS</MTART>
<MATKL>1111003</MATKL>
- <E1MAKTM SEGMENT="1">
<MSGFN>005</MSGFN>
<SPRAS>E</SPRAS>
<MAKTX>AA Ni-MH Rechargeable Batteries</MAKTX>
</E1MAKTM>
- <E1MARCM SEGMENT="1">
<WERKS>4911</WERKS>
<BESKZ>F</BESKZ>
</E1MARCM>
- <E1MARCM SEGMENT="1">
<WERKS>4912</WERKS>
<BESKZ>X</BESKZ>
</E1MARCM>
- <E1MARCM SEGMENT="1">
<WERKS>5020</WERKS>
<BESKZ>E</BESKZ>
</E1MARCM>
- <E1MARMM SEGMENT="1">
<MEINH>CS</MEINH>
</E1MARMM>
- <E1MLGNM SEGMENT="1">
<LGNUM>020</LGNUM>
<LHMG1>2020.000</LHMG1>
<LETY1>E2</LETY1>
</E1MLGNM>
- <E1MLGNM SEGMENT="1">
<LGNUM>023</LGNUM>
<LHMG1>2323.000</LHMG1>
<LETY1>E2</LETY1>
</E1MLGNM>
- <E1MLGNM SEGMENT="1">
<LGNUM>024</LGNUM>
<LHMG1>2424.000</LHMG1>
<LETY1>E2</LETY1>
</E1MLGNM>
- <E1MVKEM SEGMENT="1">
<VKORG>4900</VKORG>
<PRAT1>X</PRAT1>
</E1MVKEM>
- <E1MVKEM SEGMENT="1">
<VKORG>5000</VKORG>
<PRAT1>/</PRAT1>
</E1MVKEM>
</E1MARAM>
</IDOC>
</MATMAS05>
so in this example above:
Receiver 4911 (WERKS) should receive:
F + 2020 (BESKZ + LHMG1)
Receiver 4912 (WERKS) should receive:
F + 2323 (BESKZ + LHMG1)
Receiver 5020 (WERKS) should receive:
F + 2424 (BESKZ + LHMG1)
The problem is all these 3 messages are delivered to all the 3 plants thus making it 9 messages delivered in total as against 3.
/ Saj

Receiver determination for ALEAUD??

Hi,
I have configured my ALEAUD for a (B2B partner) R3 -> PI (B2b) - > PI (local) - > R3 (local) scenario... I have requested the partner PI system to map their systems to my business systems in their Receiver determination step - header mapping.... But the reverse step of sending back AleAUD is falling in our partners system because of the changed business system names...
I am not able map the ALEAUD back to the original Business sytems used by the partners....Although I have created a receiver aggrement the std Aleaud does not pick it up.
I would like to avoid using the ALEAUD as a seperate message approach.
Regards,
Arvind R

Hi Arvind,
Refer this links. Hope it will help you.
Custom processing for ALEAUD01 messages ??
Re: XML Incoming Invoices - Send response to Vendor for Failed Messages in XI
Thanks.

Dynamic Receiver Determination (Enhanced RD doesn't attend)

Guys,
we have a BPM scenario where we need to determine the receiver of a message based on some conditions which are known only in the runtime of the BPM. In particular, we want to determine the receiver of Message A based on a condition checked over Message B. We can't change the payload of Message A (XSD determined by client).
As you can notice, using Enhanced RD or Standard RD with condition won't solve my problem (since both of these methods only use Message A's payload to determine its own receiver).
Do you have any sugestions on how to accomplish this?
Thanks in advance,
Henrique.

Vijaya,
thanks for your reply.
I don't know if you understood the whole problem.
I'm already using a Switch step. In each of the branchs I have a Async Send Step to send Message A and the condition of the Switch is based on Message B. But the problem is on configuration.
When I create the routing objects, if I create two interface determinations from the same receiver determination, any of the send steps will try to send the message to both receiver systems, since I cannot define a condition in receiver determination itself, because the condition doesn't deppend on the sent message payload.
Regards,
Henrique.

Enhanced Receiver determination - for Integration Process

Hi,
Just wanted to confirm that if it is possible to have more than one Receivers, with Enhanced Receiver Determination and one of the Receiver happens to be Integration Process. I know with Enhanced Receiver Determinations you can find more than one Receivers at Run time, however the key question is, if in addition to normal Receiver Systems (like SAP R/3 or Web Services etc), if we can also kickoff Integration Process within Enhanced Receiver Determination.
Thanking in advance.

as said by Udo Martens
Assumedly the different receivers are using different Inbound Interfaces (a BP is using an Abstract Interface). Therefore you would need for each different receiver a own Interface Determination referring a own mapping.
refer this wiki http://wiki.sdn.sap.com/wiki/pages/pointstab/viewpageversion.action?pageId=131760630&version=5 to Know how to configure Enhanced receiver determination and Interface determination for each receiver .
In your case one of the receiver will be Integration process

Receiver determination for a proxy

I have a sender proxy and I want to configure two receivers for this proxy. But I would like to use a condition. If I now open the condition editor then I do not see the message in the condition editor. Does anybody has experience with sender proxies and conditions for receiver determination ?

Hi Frank,
the interface and the business system are connected in SLD over the product/softwarecomponent which you put in techn/business system. But that does NOT avoid any functionality. It is only useful for help windows in IB directory.
The "message" you got was only a "information", not an error. Just ignore it. The condition editor should open anyway. You can either "click" there to value of your message or put manually a X-Path expression. If your field is distinct just use the double slash like //myfield to ask for the searched value. The parser will read first element called "myfield" which is found.
Regards,
Udo

Dynamic receiver Determination for Sync Scenario??

Similar Messages

Maybe you are looking for