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.
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,
ThomasHi 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. -
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 -
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 -
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 VellaiparambilHi 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 -
Receiver Determination Enhancement
what is Receiver Determination Enhancement?
how will i use it?Hi,
Enhanced Receiver Determination
In IR
Have you imported Receiver Determination in the SAP BASIS --> http://sap.com/xi/XI/System.
Have you created 2 message mapping
1) input_output_mm on input_mt and output_mt
2) input_receiverdet_mm on input_mt and Receivers
Have you created interface mapping under input_mi and ReceiverDetermintion message interface as source mt is your input_mt and target mt is your Receivers
In RD
Sender name->Your source BS
Sender interface->your source MI
Choose the option Extended ->
Choose interface mapping name under your namespace.
Before that Check whether you have activated everything properly.
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/enhancedReceiverDeterminationinSAP+XI&
/people/venkataramanan.parameswaran/blog/2006/03/17/illustration-of-enhanced-receiver-determination--sp16
A typical usage case is if you do not yet know the names of the receivers at configuration time.
/people/venkataramanan.parameswaran/blog/2006/03/17/illustration-of-enhanced-receiver-determination--sp16
Illustration of Enhanced Receiver Determination - SP16
/people/venkataramanan.parameswaran/blog/2006/03/17/illustration-of-enhanced-receiver-determination--sp16
Enhanced Receiver Determination for Synchronous Scenarios
/people/jin.shin/blog/2007/12/11/sap-netweaver-process-integration-enhanced-receiver-determination-for-synchronous-scenarios
Enhanced Receiver Determination
http://help.sap.com/saphelp_nw04s/helpdata/en/43/a5f2066340332de10000000a11466f/frameset.htm
Thanks,
RamuV -
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 > 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> -
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 -
Extended receiver and enhanced interface determination
Hi,
Can somebody list me the business cases when we use the extended receiver and enhanced interface determination.In which scenarios we have to use them?
Where we can use these features and whom they can replace?
Regards,
AnoopHi Anoop
have alook at thses URl's also
http://help.sap.com/saphelp_nw04/helpdata/en/43/01322a7af25285e10000000a1553f7/frameset.htm
:Dynamic file and variable substitution
Similarly Extended Receiver determination is used to determine the receiver at runtime.
Refer my reply:Re: Condition In Receiver Determination Not Working
enhancement in ID
Enhanced Receiver Determination:
You use an enhanced receiver determination to have a mapping program determine the receivers of the message dynamically at runtime. Instead of creating the receivers in the receiver determination manually, you assign a mapping to the receiver determination and this returns a list of receivers at runtime.
http://help.sap.com/saphelp_nw04/helpdata/en/43/a5f2066340332de10000000a11466f/content.htm
Enhanced (Mapping-Based) Interface Determination
In an enhanced interface determination you do not enter the inbound interfaces manually, but instead first select a multi-mapping. You get the inbound interfaces from the target interfaces of the multi-mapping. The inbound interfaces are determined at runtime during the mapping step.
You typically use an enhanced interface determination if the source message has an element with occurrence 0 ... unbounded (for multiple items of a data record) and you want multiple messages (for the individual items) to be generated at runtime.
http://help.sap.com/saphelp_nw04/helpdata/en/42/ed364cf8593eebe10000000a1553f7/frameset.htm
<b>enhanced interface determination</b>
/people/robin.schroeder/blog/2006/11/15/using-dynamic-receiver-determination-with-sync-interface
/people/venkataramanan.parameswaran/blog/2006/03/17/illustration-of-enhanced-receiver-determination--sp16
List of receivers can be dyamically determined and assigned at runtime using enhanced receiver determination .
http://help.sap.com/saphelp_nw04/helpdata/en/43/a5f2066340332de10000000a11466f/content.htm
Thanks
Pls reward if useful -
Purpose of Enhanced Receiver Determination
Hi
i go thrown the some sap help link .. But I did't understand.. so, can any of you plz explain the what is the purpose of the Enhanced Receiver determination..
for this.. in mapping side does we need to do any special things.. or for a normal scenario also.. can we use this..
I want to use this Enhanced Recever determination in my scenario.. for that what are the steps i need to follow..
Regards
BabuHi !
Enhanced Receiver Determination:
You use an enhanced receiver determination to have a mapping program determine the receivers of the message dynamically at runtime. Instead of creating the receivers in the receiver determination manually, you assign a mapping to the receiver determination and this returns a list of receivers at runtime.
http://help.sap.com/saphelp_nw04/helpdata/en/43/a5f2066340332de10000000a11466f/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/42/ed364cf8593eebe10000000a1553f7/frameset.htm
/people/venkataramanan.parameswaran/blog/2006/03/17/illustration-of-enhanced-receiver-determination--sp16
also check this
Please Check
/people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it146s-possible
/people/venkataramanan.parameswaran/blog/2006/03/17/illustration-of-enhanced-receiver-determination--sp16
http://help.sap.com/saphelp_nw2004s/helpdata/en/43/a5f2066340332de10000000a11466f/frameset.htm
/people/shabarish.vijayakumar/blog/2006/06/07/customise-your-xpath-expressions-in-receiver-determination
http://help.sap.com/saphelp_nw04/helpdata/en/42/ed364cf8593eebe10000000a1553f7/frameset.htm
/people/venkataramanan.parameswaran/blog/2006/03/17/illustration-of-enhanced-receiver-determination--sp16
Also check ....
http://help.sap.com/saphelp_nw2004s/helpdata/en/43/a5f2066340332de10000000a11466f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/42/ed364cf8593eebe10000000a1553f7/frameset.htm -
>Enhanced Interface determination.
/people/shabarish.vijayakumar/blog/2006/06/07/customise-your-xpath-expressions-in-receiver-determination --->Customised XPath
Also check the following threads
Enhanced Receiver Determination
Enhanced Receiver Determination synchronous
/people/robin.schroeder/blog/2006/11/15/using-dynamic-receiver-determination-with-sync-interface
/people/venkataramanan.parameswaran/blog/2006/03/17/illustration-of-enhanced-receiver-determination--sp16
List of receivers can be dyamically determined and assigned at runtime using enhanced receiver determination .
have alook at thses URl's also
http://help.sap.com/saphelp_nw04/helpdata/en/43/01322a7af25285e10000000a1553f7/frameset.htm
:Dynamic file and variable substitution
Similarly Extended Receiver determination is used to determine the receiver at runtime.
Refer my reply:Re: Condition In Receiver Determination Not Working
enhancement in ID
Enhanced Receiver Determination:
You use an enhanced receiver determination to have a mapping program determine the receivers of the message dynamically at runtime. Instead of creating the receivers in the receiver determination manually, you assign a mapping to the receiver determination and this returns a list of receivers at runtime.
http://help.sap.com/saphelp_nw04/helpdata/en/43/a5f2066340332de10000000a11466f/content.htm
Enhanced (Mapping-Based) Interface Determination
In an enhanced interface determination you do not enter the inbound interfaces manually, but instead first select a multi-mapping. You get the inbound interfaces from the target interfaces of the multi-mapping. The inbound interfaces are determined at runtime during the mapping step.
You typically use an enhanced interface determination if the source message has an element with occurrence 0 ... unbounded (for multiple items of a data record) and you want multiple messages (for the individual items) to be generated at runtime.
http://help.sap.com/saphelp_nw04/helpdata/en/42/ed364cf8593eebe10000000a1553f7/frameset.htm
Thanks -
Requirement in receiver determination
Hi
We are on XI 3.0 SP18 and have the following requirement -
I have two receivers - A and B for a message - asynchronous mode . I want the message to reach receiver B only if it has successfully reached A - ( technically successful - as in any async scenario ) .
How can this be achieved ? Can enhanced/dynamic receiver determination solve my requirement ? Please elaborate .
Thanks in advance for your answers/solutions.You have to use a BPM model to control to check the response from Receiver A and make a decision to send the message to receiver B.
Also keep in mind a BPM model will additional concerns around the performance of integration scenario, so please make sure these requirement is completly necessary.
In other way you can accomplish the same by using an intermediate sotrage such as JMS storage and JDBC storage etc.
Thanks -
Hi,
I have a situation where I have a message mapping that populates a JDBC insert statement. Basically this is just a message interface that gets sent through to a JDBC receiver adaptor.
Now, there are multiple databases sitting on the WAN. This message interface could be sent through to any of the the multiple databases. So the only difference in the receiver agreement would be the actual communication channel being used (i.e. the communication channel created for each of the different databases).
Now at the time of the message mapping, I know which communication channel to use. Would I be able to change the communication channel being used in the 1 receiver agreement, to which ever communication channel I want?
This would then allow me to have multiple communication channels (1 for each of the databases), but only have 1 receiver agreement.
Thanks,
MiguelThe cardinality of Receiver Comm Channel and Receiver agreement is 1:1
So for every Comm channel you have created for Receiver , You should create as many as Receiver Agreement.
But Dynamic Receiver can be identified by using either Conditional Receiver Determination or Enhanced Receiver Determination.
Enhanced Receiver Determination
/people/venkataramanan.parameswaran/blog/2006/03/17/illustration-of-enhanced-receiver-determination--sp16
Enhanced Receiver Determination
/people/prasadbabu.nemalikanti3/blog/2006/09/20/receiver-determination-based-on-the-payload-of-input-dataextended-xpathcontext-object
Enhanced Receiver Determination https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/enhancedReceiverDeterminationinSAP+XI&
Multiple receiver
/people/shabarish.vijayakumar/blog/2005/08/03/xpath-to-show-the-path-multiple-receivers
Enhanced Receiver Determination
/people/shabarish.vijayakumar/blog/2006/06/07/customise-your-xpath-expressions-in-receiver-determination
Dynamic Receiver Determination
/people/robin.schroeder/blog/2006/11/15/using-dynamic-receiver-determination-with-sync-interface -
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. -
Problem while determining receivers in enhanced receiver determination
i am doing scenario FILE-TO-FILE (with one sender and 2 receivers, dynamic receiver identification based on mapping)using enhanced receiver determination,
it is giving following error in MONI,
<b>Problem while determining receivers using interface mapping
System expected the element 'Receivers'</b>
pls. help me if anybody experienced this scenario,
i am doing this scenario based on the below blog.
/people/venkataramanan.parameswaran/blog/2006/03/17/illustration-of-enhanced-receiver-determination--sp16Have u properly followed the weblog,
Integration Repository Step No 2 and Step No 5
<i>2. </i><i>In order to use the enhanced receiver determination, create a message mapping which has the target message as Receiver Determination in the SAP BASIS --> http://sap.com/xi/XI/System.</i>
<i>5. Create the Interface Mapping </i>
U must have checked that ur Xi is on SP 16 or above )
Regards,
Prateek -
How enhanced receiver determination works..?
hi all,
In enhanced receiver determination Interface mapping(which has java mapping) I have also included logic to make some change in content of input file and dynamic configuration for output file name. My input and output are flat files. So I m using dummy structure. In interface determination i m not referring any Interface mapping.
Receiver determination is working properly But neither dynamic file name nor the changes in content of file are reflecting in out put file.
Is it mandatory to use separate mapping in interface determination to change the content of file and dynamic file name?
Thanks
Jai
Edited by: Jaideep Baid on May 29, 2010 6:27 PMIs it mandatory to use separate mapping in interface determination to change the content of file and dynamic file name?
The mapping used to in receiver Determination is to decide the Receiver.....the mapping used in Interface Determination is to create the target structure....both are to be developed and used separately (one in Receiver Determination and other in Interface Determination respectively)....this wiki gives you an example:
http://wiki.sdn.sap.com/wiki/display/SI/StepbyStepguidetoExplainEnhancedReceiver+Determination
Regards,
Abhishek.
Maybe you are looking for
-
Hi Experts, I have developed dashboard with BEX query as a source(9 queries used in dashboard). This dashboard opens in 40 secs in BI launchpad but if I open same dashboard through SAP BI app it almost taking 3-4 min. Is there any ways to im
-
Converted apple loops won't add to logic.
I think others have had the same problem but I just spent hours converting wavs to apple loops and in the end, more than half of them won't even show up in logic. The ones that do show up in the logic loop pane are not "looping" either even though I
-
Nested classes and GUI integration
I have a GUI class called ArenaHelperGUI and an ArenaHelperRunner that's supposed to store the data taken from the text fields in the GUI and later do some calculations on it. The GUI is nested within the runner, but it can't do anything to the runne
-
Happy New Year, all! Question about my daughter's G4 running OS 9.2.2. Wanting to use the speech mode I bought a "drugstore" mic., plugged it in........and nada! Went out and got a gee-whiz looking made-for-Mac USB mic, plugged in to the back panel a
-
HT4009 In app purchase failed, but card charged!
I made an in-app purchase which i never received but have been billed for - the report a problem does not allow me to explain - what do I do?