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.

Similar Messages

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.

Enhanced Interafce Determination Split Mapping Performance factor

Hi,
I want to know is it a good practice to use Split Mapping using the Enhanced Interface Determination (EO-Maintain Order at Runtime is unchecked) and let the JEE adapter handle bundlings, etc.
If the number of messages split are more say in order of thousands, it causes severe stress on the JEE Server and it goes down.
Is Enhanced Interface Determination recommended to be used for high volume or any parmeters have to be tuned for its use.
Thanks.
Regards,
Sudharshan N A

Hi
Enhanced Interface Determination can be used for High Volume
BPM is the other option for multimapping.
But as compared to BPM , Enhanced interface Determination is the better option by performance .
Regards
Abhijit

Enhanced Interface Determination - does not work!

Hi guys,
well i have a scenario where i have done a multi mapping where MT_TYPSCH is generated for each new value which occurs in one special source field.
<NO>1</NO>
<NO>2</NO>
<NO>3</NO>
..so three MT will be generated.
Now i would like these messages devided to different Business Services where each one has on FTP-CC to write a file with a certain filename, e.g. File1.txt, File2.txt, File3.txt.
Therefore i thought i use different receivers in Receiver Determination with using Conditions and pointing to a value in field with XPATH. So depending on field <NO> the message should be routed to the given receiver targets.
I surely use the enhanced Interface Determination because i use multi mapping.
But when i run test, i receive 3 files with different names but same content. For me the receiver determination is not working that good.
Can someone help me on this?!
source:
<ZBC0>
<IDOC BEGIN="">
<EDI_DC40 SEGMENT="">
<ZBC0 SEGMENT=""> 0...9999
<NO>1</NO>
<TYPE>1B20-6</TYPE>
<SPEC>152J</SPEC>
</ZBC0>
<ZBC0 SEGMENT="1">
<NO>2</NO>
<TYPE>1B20-6</TYPE>
<SPEC>152J</SPEC>
</IDOC>
</ZBC0>
target:
<?xml version="1.0" encoding="UTF-8"?>
<MT_TYPSCH> 1..1
<TYPSCHRecordSet> 1..1
<TYPSCHDetailsStruc> 1..unbounded
<FELD1/> {represents content of <No>}
<FELD2/>
<FELD3/>
</TYPSCHDetailsStruc>
</TYPSCHRecordSet>
</MT_TYPSCH>

Hi Mario,
ok here is my requirement.
We get ONE IDoc in which several items are listed. These have one field <NO> which can have the values 1,2 and 3. Depending on this value the items should be collected and written to different files on FTP.
My approach is that i divide all the items in mapping in different Message Types. This MT should be routet to different business services which has one CC to write on FTP.
To get the items with e.g. <NO>1</NO> i took condition in reciever determination using xpath. ((/ZBC21/IDOC/ZBC21/NO = 1).
So depending on the mapping everything runs - in my point of view but the different messages are not routed to the different services to write them to different files.
Source
<ZBC0>
<IDOC BEGIN="">
<EDI_DC40 SEGMENT="">
<ZBC0 SEGMENT=""> 0...9999
<NO>1</NO>
<TYPE>1B20-6</TYPE>
<SPEC>152J</SPEC>
</ZBC0>
<ZBC0 SEGMENT="1">
<NO>2</NO>
<TYPE>1B20-6</TYPE>
<SPEC>152J</SPEC>
</IDOC>
</ZBC0>
target:
<?xml version="1.0" encoding="UTF-8"?>
<MT_TYPSCH> 1..1
<TYPSCHRecordSet> 1..1
<TYPSCHDetailsStruc> 1..unbounded
<FELD1/> {represents content of <NO>}
<FELD2/>
<FELD3/>
</TYPSCHDetailsStruc>
</TYPSCHRecordSet>
</MT_TYPSCH>
The output should be files with content of items depending on field <NO>.
file1.txt (all items with <NO>1</NO>)
file2.txt
file3.txt
I hope i made it clearer!
br

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

Error with Enhanced Interface determination

Hi Experts,
In enhanced interface determination for message splitting w/o BPM, i have given the interface mapping.
But while testing the configuration.......... i am getiing an error at Interface Determination & Mapping which is not showing any processing log.
My mapping program works fine.
could anyone tell me where the problem is....

Hi,
Can you post the error message that you are getting....it will help experts solve your problem accurately.
Regards,
Abhishek.

Enhanced receiver determination

why we assign the abstract message interface ReceiverDetermination as the target interface.can we achieve enhanced receiver determination without this abstract interface.I have gone through sap help and some blocks of sdn also but still its not clear to me that whats the role of this abstract interface.

Hi
For receiver determination::- See
http://help.sap.com/saphelp_nw04/helpdata/en/26/5ccd3bb4560f01e10000000a11402f/content.htm
About
Abstract Interface :
The abstract interface work both inbound and outbound interface(Bi directional).
BPM can process messages only through "abstract interfaces" al though Receive and Send steps can have interfaces other then "abstract interfaces" all other intermediat steps of BPM needs "abstract interfaces"
Hope it helps
regards
Piyush

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

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.

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

Can I Using Enhance Receiver Determination?

Hi,
Can I used Enhanced Receiver Determination to push data to Receiver 2 , based on the response coming from Receiver 1 ( a BPM that that has a synchronous send step and fetches response from SAP through a proxy) ? If yes, how ?
thanks & regards,
XA

We can have just a send step and for that send step we can configure a condition based receiver Determination right?
yeah correct
> and Can you throw some light on how to deal with queues, in case if the response doesnt come from SAP to PI due to some reason, which can happen in real time?
it will thhrow time out exception or message expired exception, if you want to do exception handling do it accrodingly using Control step.
Regards,
Raj

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

Enhanced recv determination

Similar Messages

Maybe you are looking for