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,
> 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.
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 don't want to hard code my business service name in mapping.How can I achieve this?
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

Similar Messages

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

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>

PI 7.1 - Parameter in enhanced receiver determination

Hello experts,
I am working on PI 7.1.
I defined a scenario where I am using an enhanced Receiver determination to determine the list of target services thanks to an operation mapping and its related message mapping. I'd like to pass a constant value from this receiver determination to use it in the message mapping.
To do so, I set an import parameter in the operation mapping and the message mapping and made the needed binding.
I can then see this parameter in the receiver determination, but I can not put a constant value in it and then activate my configuration..
Do you know why ?

Hi
I have not used this feature yet, however I dont think that this is a bug.
the Parameterized mapping feature is for ID->OM->MM & not for RD.
more info
http://help.sap.com/saphelp_nwpi71/helpdata/en/43/bbb7fd90f5332ee10000000a11466f/frameset.htm
/people/jin.shin/blog/2008/02/14/sap-pi-71-mapping-enhancements-series-parameterized-message-mappings
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/909e33f0-738c-2a10-4f87-ce73398bcf08
Regards
Vishnu

Intermittent JDBC error in Enhanced Receiver Determination

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

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

Interface Determination under Enhanced Receiver Determination Scenario

Hi,
One of the very basic assumption for Enhanced Receiver Determination is that Receivers are found at run time, and one of the such requirement is that we don't know about Receiver Business System at the time of configuration.
Now for such scenarios, how do we configure "Interface Determination". For Interface Determination one of the input filed is "Receiver Service/Party", in addition to "Sender Service/Party" plus "Sender Interface"
Since we don't know Receivers at config, what value(s) should come in "Receiver Service/Party" in Interface Determination at config time.
Thanking all of you in advance

Hi Rajan,
You have to do the following things:-
First, maintain Database Table in SAP XI. Which contains several keys like Sender, Receiver system and then according to that key combination we perform a JCO call and fetch the values which gives us the correct receiver and interface.
Create a Data Type which will be having Two elements Service And Interface.
Now careate a message type and message interface for this data type. This will be for your receiver.
Then use source payload and perform a message mapping between Sender Payload & this Message Type.
Use UDF and make a JCO call and fetch table entries for service and interface.
Then in Directory perform extended determination and use this mapping into it. The result will be Service & Interface.
Thanqs
Biplab

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.

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

Problem with Enhanced Receiver Determination

Hi Friends,
I am doing the enhanced receiver determination scenario, But it is giving the
error in SXMB_MONI like this
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <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">CX_RD_PLSRV</SAP:Code>
<SAP:P1>Problem while determining receivers using interface mapping: Fehler beim Parsen der Empfänger-Liste.Länge des XML-Dokuments 264</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error when determining the receiver: Problem while determining receivers using interface mapping: Fehler beim Parsen der Empfänger-Liste.Länge des XML-Dokuments 264 Problem while determining receivers using interface mapping: Fehler beim Parsen der Empfänger-Liste.Länge des XML-Dokuments 264 Fehler beim Parsen der Empfänger-Liste.Länge des XML-Dokuments 264 System expected the element 'Receivers'</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
this is error is coming in the SXMB_MONI
THE DATA type(Receivers) we create in basis component is comes automatically?
are we have to create?
in my scenario i creted manually,
is it compulsory to specify the properties for the party and agency?
is it compulsory to create 2 Receiver structures in msg structure?
if yes what r those, actually i used from sap.help.com,
Can any body should give me the solution for this, regarding mapping and configuration , if anybody experienced this scenario. Pls . give me the guidelines to do.

Hi,
the mapping creating the receiver list is not producing the required element "Receivers" from Namespace "'http://sap.com/xi/XI/System". Look to the operation mapping given in the enhance Receiver Determination (IB Directory) and detect the corresponding mapping program (ESR). Copy the source payload from MONI, test the mapping program and correct it.
Regards,
Udo

Enhanced Receiver Determination in PI7.1

Hi,
We have a requirement where in we have to use the Enhanced Receiver Determination for one of our scenarios for choosing the receiver.We are on PI7.1.
As of now,we have mapped a constant rcvr(Test_Supplier) to the Service in the message mapping from our source to the target -Receivers, as we do for Enhanced Receiver determination.The rcvr determination choosing Extended and the correct Operation mapping has been configured.The coresponding Interface determination and Receiver agreements have also been configured.
When trying to test this by posting a payload through RWB,we get the No_Receiver_Case_Async error.
Is it necessary to map the party field also in the message mapping?Am I missing something here?Kindly advise.
Thanks and Regards,
Induja

When trying to test this by posting a payload through RWB,we get the No_Receiver_Case_Async error.
Is the Mapping which you developed to determine the receiver(s) able to give the appropriate output? Apart from cache problem, this can also be the issue when the mapping does not produce i.e. no proper service is populated in the corresponding node....the service must be actually present (and active) in ID
Regards,
Abhishek

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

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,
Problem while determining receivers using interface mapping
System expected the element 'Receivers'
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--sp16

Have u properly followed the weblog,
Integration Repository Step No 2 and Step No 5
2. 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.
5. Create the Interface Mapping 
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 PM

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

Enhanced Receiver Determination with RFC Lookup

Hi All,
I am building an interface with Enhanced Receiver Determination. Scenario would be that the Receiver Systems would be stored in a Z table in SAP ECC, and in PI Receiver Determination I am doing an RFC look up to find the systems, and using those.
I built the mapping for Receiver Determination, and it tested fine in ESR. But while Creating the Receiver Determination in Integration Directory, After I specify the Receiver mapping name, and put the RFC channel name for the RFC parameter, it doesnt allow me to save the Receiver Agreement with a run time error message
"Link from Receiver Determination | <Sender>| <Interface>| * | * to object type "Channel" with role "122474913b1311deaadb42057dd8b002" is not permitted"
My question is a) if the RFC lookup allowed in the mapping for Receiver Determination?
B) if yes, am I missing someting or is it a system issue?

i have seen Enhanced RD with lookups that work. Have to say it was not a RFC lookup used but rather a DB look in one of the implementations i had worked with. But still I really dont think a RFC lookup should be an issue.
Troubleshoot the lookup mapping to be working other than in the enhanced RD (i.e independently) .
if you head no where, i suggest opening a OSS note.

Using Enhanced Receiver Determination with a Synchronous Service Interface

Hi Experts,
I want to use ERD on a Synchronous Interface. Is that possible? Perhaps it has no sense, because in an ERD you can choice multiple receivers and that its against the synchronous philosophy: what if you declare 2 or more receivers, from wich one has the right response to be taken?
In technical terms I build the operation mapping as it is written both in the blog (/people/venkataramanan.parameswaran/blog/2006/03/17/illustration-of-enhanced-receiver-determination--sp16) and the SAP HELP.
But in my OM I have as source service interface one Abstract Synchronous and in the target I have one Abstract Asynchronous wich is not possible. So I tried many tricks like creating my own synchronous ReceiverDetermination Service Interface in my SWC, but it is not detected. Other trick will be modifying the standart SI, but it will affect the next guy trying to use ERD with an Asynchronous interface
The point its that it is a little funny that the receiver determination allows using ERD with a synchronous SI wich makes me think that it will be possible...
Is it possible to use ERD with a Synchronous Interface?
Regards
Gonzalo

i have seen Enhanced RD with lookups that work. Have to say it was not a RFC lookup used but rather a DB look in one of the implementations i had worked with. But still I really dont think a RFC lookup should be an issue.
Troubleshoot the lookup mapping to be working other than in the enhanced RD (i.e independently) .
if you head no where, i suggest opening a OSS note.

Enhanced receiver determination and value mapping

Similar Messages

Maybe you are looking for