Doubts on Enhanced Recever determination blog

Hello ,
Regarding Enhanced Receiver determination I am working on the
blog " Illustration of Enhanced Receiver Determination - SP16
But I didnt understand the floww...
so Could you pls give the necessary Interface mappings and message mapings I need to deevelop
and also steps for the ID part too....
Blog is not clear for me...
Please do the needful

Hi Satya,
You will need to create 2 message mappings. One will be simple mapping between source and target messages. The other mapping will be between the source message and in the target you need to select Receivers from the Software Component SAP BASIS and namespace http://sap.com/xi/XI/System. Then go ahead and create the respective Interface Mapping. In the second Interface Mapping use Receiver Determination in the target interface.
In the ID part you need to select the Enhanced option in the Receiver Determination and select the Second Mapping that you have created.
Then the rest interface determination and all you need to create accordingly.
Thanks and Regards,
Sanjeev.

Similar Messages

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
Babu

Hi !
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

Enhanced Interface Determination?

Hi All,
I have a scenario where i need to do a header validation . if validation succeeds i have to map source to target data and sent to SAP system. if validation fails i need to map source to error data and sent it to MQ system.
I am using enhanced receiver determination for selecting proper receiver based on the header validation. but in this case inspite of failed header validation there is no error message in SXMB_MONI...
what i wanted is that when header validation fails , error message should be displaced in moni and also a error message (xml ) should be sent to MQ system.
for implemention the above mentioned feature , i took another message mapping and interface mapping where i am explicitly throwing error -- Repository work.
In configuration , i just create one more receiver determination with new message type and in existing interface determination , i added the additional interface mapping ( throwing error ).
due to above changes , i am getting three message in Moni.. if header validation fails.
1. which indicated that there is message splitting.
2. one successful message ( source to error xml file ) to be sent to MQ system.
3. error message where i am explicitly throwing error .
can we have a situation where we have only one error message in moni and also the error is sent to MQ system?..
i guess there is some feature in interface determination.. what is enhaced interface determination..
I hope i am clear with my requirement..
Ranjeet Singh...

Have a look
/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

Enhanced Inerface Determination for File to IDoc scenario

I am using Enhanced Interface Determination in my scenario - where I map my source message (from a single instance) into more than one IDoc messages (separate instance of Idoc for each occurance of a particular segment in the source message). To implement this I am 1:n message mapping for Message Splitting.
The mapping is being executed successfully and several instances of the target IDoc type is being created at the runtime. But at the technical routing step I am getting error:
<SAP:Stack>Messages in multi-message format can only be sent to one Adapter Engine</SAP:Stack>
Does this mean that we cannot use Multi-Mapping for Message Splitting for IDoc Outbound Channels? Even if all the target messages (more than one) are being sent through the same Inbound interface and same Reciever IDoc Channel?
Regards,
Suddha

Thanks Farooq for your valuable advice.
You know what, I read those restrictions in the help.sap.com but had thought there must be some work around. It says split messages are sent using only one AE, but I hoped that Idoc and Http can be used as they are not part of AE and rather IE itself. Anyways, can't help...............but could help me understand what are the technical reasons for these restrictions?
The blog is really a nice one and very helpful..............thanks! I used multi-mapping in exactly similar way as in the blog and used enhanced interface determination - but the target message being Idoc
Is BPM the only option for my scenario?
Regards,
Suddha

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

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

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

Regarding Enhanced Receiver Determination

Hi Experts,
I go through the Blog
/people/venkataramanan.parameswaran/blog/2006/03/17/illustration-of-enhanced-receiver-determination--sp16
In this i am not getting the Source Msg Structure And Target Msg Structures
Can any one Give me a LOOK at this Structures Please..............
Regards
Khanna

Hi,
>>>>Can u Explain me in detailed what is the use of SAP BASIS 6.40 here.
What is the necessary in this scenario.
Why should we create Receiver et in the SAP BASIS.
>>>>SAP BASIS 6.40 here.
you can get required message type from it
>>>>Why should we create Receiver et in the SAP BASIS.
no need as it's already there (the message for receiver det)
Regards,
michal

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.

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,
Anoop

Hi 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
enhanced interface determination
/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

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

Enhanced Reciever Determination Map problem

Hi,
i am working on enhanced reciever determination, i followed this blog for reference
/people/venkataramanan.parameswaran/blog/2006/03/17/illustration-of-enhanced-receiver-determination--sp16
after the mapping recievers MT (predefined from BASIS) . i have tested with the following payload and it is working fine.i got my ERD is working
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_SampleFile_sx xmlns:ns0="urn:TestScenario">
 <Person>
 <name>mr</name>
 <age>123</age>
 </Person>
 <Person>
 <name>ms</name>
 <age>12</age>
 </Person>
</ns0:MT_SampleFile_sx>
if i give the payload with more mr or ms node like below, i am getting error.
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_SampleFile_sx xmlns:ns0="urn:TestScenario">
 <Person>
 <name>mr</name>
 <age>123</age>
 </Person>
 <Person>
 <name>mr</name>
 <age>12</age>
 </Person>
 <Person>
 <name>ms</name>
 <age>1256</age>
 </Person>
</ns0:MT_SampleFile_sx>
ERROR: Cannot produce target element /ns1:Receivers/Receiver[3]/Service. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd
can any one help me to solve this problem
Thank You,
Madhav

Hi,
I had checked UDF. As per UDF you want to give ,
<name>mr</name>
instead
<name>Mr</name>
Change the payload and map like below,
Receiver:
Name(Change Context to parent)--SplitByValue(ValueChange)--CollapseContext--Receiver
Service:
Name(Change Context to parent)--ServiceDetermination(UDF)--SplitByValue(EachValue)--Service
Regards,
Prakasu.M

Enhanced recv determination

Hi All,
If we do enhanced recv determination : I have 2 mappings : one is routing(enhanced recv mapping) and second is the regular mapping.
Do I need to specify these 2 mappings as part of one Interface mapping or as 2 separate interface mappings : one ofr enhanced recv det and other as regular mapping.
Thanks

Hello,
You need two Interface mappings. If you have doubt, please see the thread
Re: Condition In Receiver Determination Not Working (page 3) and look out for my reply.
Hope it helps!!!
Best regards,
raj.

Enhanced Interface Determination in PI 7.1

Hi All,
My scenerio will work as follows
The changes in the process order will triggered by the client system .I will get the already converted XML file.I have used the file adapter in the sender side to pick the file.At the receiver side I am using the 3 custom BAPIs.I have used 3 message interface instead of multi-mapping as the inbound interfaces.
The Logic is like that:
If the Process order status is = 1 then call BAPI 1,if it 2 then call BAPI 2 & call BAPI 3.
Please tell me the following
1.Is there Enhanced Interface Detrmination option available in PI 7.1?If so then can I mention or call 2 BAPIs in one condition over there?Do I need to write ABAP condition?
2.Is Enhanced interface Determination possible when I have used 3 inbound interfaces instead of multi-mapping?
3.From my point of view I need the following in my scenerio
- 3 message mappings(Graphical Mappings),
- 3 interface mappings,
- 1 sender agreement,
- 1 receiver determination,
-1 interface determination(with 2 conditions in it),
-3 receiver agreements.
Am I right?
4.How many sender and receiver agreements do I need?
5.Do I need to go for Enhanced receiver determination?
Thanks in advance.

the same status node in the source file on which I will impose check will call the selective inbound interface based on the
status node.Is it?If so,then do I need to mention anything other than the check condition in XPATH e.g.do I need to mention any
mapping program or inbound interface (though I dont thing so but I am still confused) ?
Yes, apart from specifying the condition in the Condition Editor you also should mention the corresponding Inbound Service Interface and Interface Mapping (if any).
Condition will only cause the execution of that particular line and wont automatically call the mapping/ interface (unless these are specified in the Interface Determination).
Is XPATH the alternative option in condition editor which can be skipped though I would surely like to go through it as
much as possible?
XPATH is the easiest option to specify a condition....other option includes the use of a Context Object.
So as of now think that you cannot skip XPATH (for this particular requirement).
Once you become an expert in using a XPATH (which you can in a days period) you can try out for Context Objects.
Regarding Test Case:
There is no standard template for this.....i would suggest check with peers in your company.....many a times companies have their own templates for test cases alongwith the possible cases....then referring to those test cases you can build the cases for your scenario. Avoid a direct copy of the test cases.....many wont be relevant for your case.
Regards,
Abhishek.

Doubts on Enhanced Recever determination blog

Similar Messages

Maybe you are looking for