on 12-20-2012 6:04 AM
Hi,
As i am new to SAP PI, I am doing self learning. When i was go through the ESR & ID objects, i struck at a level.
I cant find the real time difference between the Enhanced Interface Determination & Enhanced Receiver Determination?
Please elaborate the diff with any example will be helpful for the beginners.
Thanks
Jansi
Hi Jansirani,
please find the following links which explains the terminology with examples!
Enhanced Interface Determination - http://help.sap.com/saphelp_nw04s/helpdata/en/42/ed364cf8593eebe10000000a1553f7/content.htm
Enhanced Receiver Determination - http://help.sap.com/saphelp_nw04/helpdata/en/43/a5f2066340332de10000000a11466f/content.htm
Regards,
Lakshmi Naik
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jansi,
I agree with some of above posts and in addition to that please see this concept as below:
1 Extended Receiver Determination:
First think about Standard Receiver Determination:
This concept is used when you have multiple receivers and with and without conditoin to identify
them based on payload data at ID time..
Example : you are sending one single file with business data along with company code, in that case
as per your business you can route the data to a particular receiver only.
If you assign condition then it will route to all the recivers which are satisfying the same.
Now come to Extended Receiver Determination:
This concept is used when you do not the content of the payload to determine the Receiver system.
Here you have define a mapping program using with and without UDFs also, specifying a condition
to create the target field "Receiver". If you test this at mapping time this will not give you final result.
So you have to define the mapping program to identify the receiver system. Here Receiver system
could be assigned to header at the execution of the pipeline step called Request Massage Mapping,
If you send multiple records in a single message with different company codes then it will go to all the
receivers based the condition.
2. Extended Interface Determinaiton:
This concept is used when you want sent the data to multiple inboud interfaces with or without same
receiver systems.
Here also you need to define the mapping program by using Multi Mapping Concept.
You can find the blogs for this from above postings from deiiferent experts.
Here you can use multiple CCs or Same CC depending on your requirement.
Keep posting in our SDN site to know any concept.
Regards,
Sreeni.
Hi guys,
Thanks to all. All of your answers make me clear cut idea in ERD & EID..
Thanks & Regards
Jansirani S
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HI Mistri,
First you have to refer Scn and Sap.Help for more calrification On Sap PI :
http://help.sap.com/saphelp_nw70/helpdata/en/5f/555a421b5ec153e10000000a1550b0/frameset.htm
Enhaced RD:
If You want Define the multple Receivers In RD then we have 2 Approaches
first one :
On RD , using Standard RD , this is default option .
we used to define the condition in codtion editor for root the message to multiple receivers but in that condition does not support Arthmatic operations.
Enhanced receiver determination :
the list of receivers can be determined dynamically at runtime In message mapping and also this allow us to any condition for rooting the message.
Coming to Enhanced Interface determination:
this is used for multi mapping and refer below thread for more examples:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jansi,
Please find the difference:
Enhanced Receiver Determination - In the Enhanced Receiver Determination, Instead of creating the receivers in the receiver determination manually, you assign an Interface mapping to the receiver determination and this returns a list of receivers at runtime.
A typical usage case is if you do not yet know the names of the receivers at configuration time. In this case, you can define a mapping program, for example, which reads a list of receivers from a table or from the payload of the message at runtime. So all the functionalities of message mapping can be used.
Please find the blog: http://wiki.sdn.sap.com/wiki/display/SI/Step+by+Step+guide+to+Explain++Enhanced+Receiver+Determinati...
Enhance Interface Determination - We want to use at run time if you want to chose your Operation Mapping or suppose for 1:N mapping without BPM.
Please find the blog: http://scn.sap.com/people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it-s-possible
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
The answer of this is already present in forum.
FYI - Standard RD (receiver determination) - will not use any transformation (mappings) to identify receiver while enhance RD use mapping to identify receivers.
Enhanced ID (interface determination) - is used for multiapping schenario's which standard for normal schenario.
Regards,
Harish
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Harish!!
Please find the difference:
Enhanced Receiver Determination - In the Enhanced Receiver Determination, Instead of creating the receivers in the receiver determination manually, you assign an Interface mapping to the receiver determination and this returns a list of receivers at runtime.
A typical usage case is if you do not yet know the names of the receivers at configuration time. In this case, you can define a mapping program, for example, which reads a list of receivers from a table or from the payload of the message at runtime. So all the functionalities of message mapping can be used.
Please find the blog:http://wiki.sdn.sap.com/wiki/display/SI/Step+by+Step+guide+to+Explain++Enhanced+Receiver+Determinati...
Enhance Interface Determination - We want to use at run time if you want to chose your Operation Mapping or suppose for 1:N mapping without BPM.
Please find the blog: http://scn.sap.com/people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it-s-possible
Warm's Regard
Mujeeb Ahmed
Hi Mujeeb,
Can you please let us know why you have copy pasted my content just after 5 minutes in the same block where it already exists? I dont think this is a Good practice and violation of Rules of Engagement.
User | Count |
---|---|
89 | |
10 | |
9 | |
9 | |
9 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.