Dyanamically determining receivers

Hi experts,
i had an requirement that i have to send the IDOC to multiple receiving system based on certain conditions.
Receiver determination should happend dynamically(logical routing) based on mapping content we have send the data either file system or mail box. Here i should not create any communcational channel. Recevied determination communications will create dynamically. Nothing to create in configuration side.
How to acheive the above scenario.
Thanks
viswa

Hi,
You need to have Communication channels defined for routing the messages to Business systems or services.
We can dynamically Identify the routings to Business Systems/Services based on the mapping or field values in Receiver Determination using the option "conditional routing ".
Please check this Blog :-
Conditional Routing in XI
Edited by: PhaniKumar Akella on Mar 26, 2008 3:22 AM

Similar Messages

Problem while determining receivers using interface mapping: "SYSTEM FAILURE" during JCo call. Bean SMPP_CALL_JAVA_RUNTIME3 not found

We have a SOAP to PROXY scenario Which is in Production.
We keep getting the Error:
" Problem while determining receivers using interface mapping: "SYSTEM FAILURE" during JCo call. Bean SMPP_CALL_JAVA_RUNTIME3 not found on host XXXXXX, ProgId =AI_RUNTIME_XXX.
We are using Standard Receiver Determination with single receiver without any condition. And no mapping being used in interface determination.
What are all the possible situation where we face such as this issue in Production.

Please check the SAP note
# 1706936 - messages fails with error java.lang.RuntimeException Bean SMPP_CALL_JAVA_RUNTIME3 not found
1944248 - PI unstable due to JCO_SYSTEM_FAILURE mapping issues

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 to dynamically determine Receivers within BPM

Im trying to design a way to determine my receivers within my BPM process during runtime.   My Scenario is as follows:
SAP IDOC
    V
XI
             XI uses JAVA Mapping MT1 to determine vendors and if customer receives PIDX
                         JAVA Mapping MT2 to creates the PIDX output file if required
V
SENDs to required Vendor (PIDX if required otherwise email)
My problem is how to dynamically determine the appropriate receiving vendor for my PIDX.
I can not use the condition editor on the standard Receiver Determination because the output message (PIDX) doesn't have specific enough information to determine the vendor.
Other than the customer number there are no other values and we don't want to use customer number because each vendor can have multiple customer numbers (hundreds).
I've tried various attempts but none seem to work. This could also be because I have limited knowledge of BPMs and this is my first complex development. Below are the different attempts I've made at dynamically determining the receiver. Any input would be appreciated.
Receiver Scenario 1
I developed an interface mapping with MT1 as input and the SAP Receiver Determination as output. The problem is for me to use this, the interface mapping had to reference the PIDX output (MT2 instead of MT1) which has no data that I can use to determine the receiver.
Receiver Scenario 2
I added a receiver step right before my send step and used the receiver list. This appears to send the PIDX to everyone in the list and there is no way to evaluate or eliminate a name from the list.
Receiver Scenario 3
I created a context object in the Integration Builder and assigned it to a field in MT1. I then added a switch step with a branch for each vendor. Within each specific branch there is a Send step that has the context object name I created in the "Send Context" field. However, on the configuration side Im unable to access the context object which I created on the design side. Whenever I open the condition editor and select the radiobutton for "Context Object" the list does not include the context object I created in the Integration Builder.

Hi,
Try using the enhaced receiver determination concept.
Maybe based on certain field values you can write a UDF which calculates the receiver.
Try this Blog out
Link : [
http://help.sap.com/saphelp_nw70/helpdata/en/43/a5f2066340332de10000000a11466f/frameset.htm]
Regards,
Abhishek
Award if helpful.

How to determine receivers in the send step in BPM?

Hi Guys,
I have 3 send steps in BPM defined with send context and for each send step i have defined a receiver determination in ID. Each Receiver Determination has a condition based on which identifies multiple receivers.
The BPM is failing and unable to determine the conditional routing. Do i need to add the receiver determination step before each send step so that it identifies the receivers.
Any help would be appreciated.
Thanks,
Raj

Hi Guys,
Thanks for all of you for the quick replies and it is really a great help.
We have resolved the issue. The approach is as below.
we have a generic design used by multiple customers. For the interface where we have the BPM, we are doing conditional routing for each customer before they hit the BPM that is as soon as we receive the Asynchronus request based on the condition we direct the message to a particular BPM. Basically every customer will have different BPM process. ie we create the same BPM with different names specific to each customer and in this way we dont complicate the BPM process and we will know if any particular customer has problems with his process.
Please let me know comments or suggestions on the above approach
Thanks,
Raj

Error:Returning to application. Exception: com.sap.aii.adapter.xi.routing.RoutingException: Can't determine receivers because condition evaluation failed

my requiremant is one sender and based on receiver detremination condition it should go to many receivers.
Just to elaborate the requirement.
Observe the Xpath example below:
<Identifier>
 <Name>abc</Name>
 <Value>first</Value>
</Identifier>
<Identifier>
 <Name>cdf</Name>
 <Value>come</Value>
 </Identifier>
 <Identifier>
 <Name>ten</Name>
 <Value>go</Value>
 </Identifier>
Now am using the following Xpath.
/p1:MT_fd/MessageHeader/OtherArea/Identifier/Name[1] ≈ abc AND
/p1:MT_fd/MessageHeader/OtherArea/Identifier/Value[1] ≈ first AND
/p1:MT_fd/MessageHeader/OtherArea/Identifier/Name[2] ≈ cdf AND
/p1:MT_fd/MessageHeader/OtherArea/Identifier/Value[2] ≈ come AND
/p1:MT_fd/MessageHeader/OtherArea/Identifier/Name[3] ≈ ten AND
/p1:MT_fd/MessageHeader/OtherArea/Identifier/Value[3] ≈ go
any suggestions for the correct xpath are welcome
thanks in advance

Hi,
so you want to trigger based on the below condition
Receiver 1
/p1:MT_fd/MessageHeader/OtherArea/Identifier/Name[1] ≈ abc AND
/p1:MT_fd/MessageHeader/OtherArea/Identifier/Value[1] ≈ first or
Receiver 2
/p1:MT_fd/MessageHeader/OtherArea/Identifier/Name[2] ≈ cdf AND
/p1:MT_fd/MessageHeader/OtherArea/Identifier/Value[2] ≈ come or
receiver 3
/p1:MT_fd/MessageHeader/OtherArea/Identifier/Name[3] ≈ ten AND
/p1:MT_fd/MessageHeader/OtherArea/Identifier/Value[3] ≈ go
so please apply this condition to different receiver service. Or if it is for one then put or in between the condition

Xpath condition not working for determining receivers

hello all
am writing a xpath expression for a simple structure
<doc>
 <status>
 <id>
</doc>
status is attribute field.and will have value 'error' and some other value for no error. I want to choose one receiver if error and other receiver if no error
so I wrote an xpath expression
/Doc[@status='Error'] EX --> Error receiver
count(/Doc[@status='Error']) = '0' --> no error receiver
it was working couple of days ago but suddenly stopped working
whats going on? thx
mike

But xpath is not working properly..
Are you using this in the condition editor of Interface Determination (it should not be a cause of concern though)
Can you confirm that the condition that you have specified is proper ....does it work when you specify only one condition?
Regards,
Abhishek.

Problem in receiver determination

hi experts
I am working on a idoc to file bypass scenario where i am using extended receiver determination ,abap class is being used for abstract interface mapping ,It is working fine with other interfaces.but on a particular idoc its started showing error in sxmb_moni that"Error when determining the receiver: Problem wh
determining receivers using interface mapping:
Error in mapping program
/GLB/CL_ZGTIS_GNERIC_ROUTING (type SAP-ABAP,
kernel error ID CREATE_OBJECT_CLASS_NOT_FOUND)" so can u tell where is the problem i have crosscheked the abap class very well all entries r right.
plz update its urgent

hey i have done a mistake in writing the class name in the mapping ............

Error in determining receiver

Hi Experts,
I am facing an error in one of the file to Proxy scenario. It's giving the following error.
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: Error when parsing receiver listLength of XML Document 411</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: Error when parsing receiver listLength of XML Document 411 Problem while determining receivers using interface mapping: Error when parsing receiver listLength of XML Document 411 Error when parsing receiver listLength of XML Document 411 An error occurred when deserializing in the simple transformation program SXI_PARSE_RECEIVERS Data loss occurred when converting ExceptionMessage: LookupValueNotFound: SourceContext: http://sap.com/xi/XI SourceAgency: SenderBusinessService SourceScheme: Payments TargetContext: http://sap.com/xi/XI TargetAgency: ReceiverBusinessSystem TargetScheme: ReceiverCheck KeyValue: BusService</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
The same scenario is working fine in production but in quality,its giving teh above error. We have used the value mapping. I have checked each and everything. Every thing is matching with teh production. The XSLT mapping program is working well in production but in quality same program is not working. I have also checked the extended receiver configuration setting. Everything is same as in production.
Please help me out. I would be greatful to every one.
Thanks
Veeru

HI,
Error clerly says that there is error in value mapping ..
Check the target values exist for the source scheme and agency..
Check the cache is updated in RWB..
HTH
Rajesh

Failed Receiver Determination on empty file

I have seen suggestions matching the solution I have tried, but it is not working in my scenario.
The scenario is an empty CSV file inbound to 3 receivers. In the standard receiver determination, I created a context condition for the 'SAP system' receiver, which uses RFC adapter. The condition is: 'Sourcefilesize not equal 0'. For an empty file, the 'SAP system' receiver should not be selected because it has mapping to the RFC structure. The other 2 receivers are SFTP and file, and the client requires they receive the empty input file.
I see the file size is captured in the dynamic configuration in the MONI:
namespace: XI/System/File.....name="Sourcefilesize">0<SAP:record...
The error is: Problem while determining receivers using interface mapping: Error while determining root tag of XML: BOM / charset detection failed.
The system is PI 7.1, the sender comm channel is Advantco with namespace override and content conversion. I have tried using file type 'binary' and type 'text', with UTF-8 encoding - results in the same error either way.
The file is coming from an external vendor - I do not believe they will make any changes to it, so hopefully this can be resolved in PI.
All suggestions are appreciated. Thank you.

Hareesh and Osman, thank you for your replies.
I should have pasted the entire message. When testing in the IB, it fails in receiver determination..
""Error when determining the receiver: Problem while determining receivers using interface mapping: Error while determining root tag of XML: BOM / charset detection failed Error while parsing an XML stream: 'BOM / charset detection failed&#39""
Only the SAP system RFC receiver has message mapping - the SFTP and file receivers do not. (I have changed only namespace and system names in screen below)
Receiver determination -
Interface Determination XXXX_D
Interface Determination Archive_D
Interface Determination SAP system

BPM interface determination error

Hi All,
i have BPM scenario. scenario like three files coming from the sender once picking the all file i have to merge these file based on the common filed in three files.
for this i used correlation in BPM
i followed the below steps:
1) i creatd three out bound service interfaces for the sender three files
2) one inbound service interface for the receiver.
3) four abstract service interfaces for the BPM.
5) Operation mapping between the abstract interfaces.
ID objects creation :
imported the integration process in ID from IR.
communication componets created for the sender & receiver
4 receiver determinations created 3 RD between Sender bussiness component & BPM ,1 RD between BPM & receiver business component
4 Interfaces determinastion created as per as RD
3 sender agreements
1 receiver agreement
while testing i got this error in SXMB_MONI
RCVR_DETERMINATION">CX_RD_PLSRV</SAP:Code>
<SAP:P1>Problem while determining receivers using interface mapping: No operation with XML root tag
i got confusion while creatin the Interfaces Determination i.e weather do we need mention Operation mapping between outbound service interface & abstract service interface
please correct what is the correct process to create the Interface determination in BPM like this scenario.
thanks in advance

Are you doing any content conversion in Sender file Adapter then check whether the Flat file properly converted to XML file or not?
You need to create Interface determination but if source and target interface message type is same then no need to specify operation mappinhg in Interface determiination.
So interface determination should be there without any operation mapping

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

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.

Error while doing Enhanced Receiver Determination

Hi,
My scenario is Fiel->XI->File with enhaced receiver determination that is i should get the receivers dynamically at runtime.
I gave Operation mapping in Receiver determination and created all other objects.
Even if i check message mapping i am getting multiple receivers but, in SXMB_MONI i am getting the following error
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">CX_RD_PLSRV</SAP:Code>
<SAP:P1>Problem while determining receivers using interface mapping: Error when parsing receiver listLength of XML document 144</SAP:P1>
<SAP:Stack>Error when determining the receiver: Problem while determining receivers using interface mapping: Error when parsing receiver listLength of XML document 144 Problem while determining receivers using interface mapping: Error when parsing receiver listLength of XML document 144 Error when parsing receiver listLength of XML document 144 System expected the element 'Receivers'</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
Can anyone suggest
Regards,
Sunitha

Hi,
I am getting error in Receiver Determination step only. so, unable to see the receivers.
Is there any option to check that particular message which conists of receivers in PI.
"In every receiver root node only one receiver can exist.
you have to reapeat the root node for every receiver. "
ya i changed the occurance of the message type. In message mapping i am getting multiple root nodes at target but in SXMB_MONI i got that error.
Regards,
Sunitha

Enhanced receiver determination - Idoc 2 Idoc scenario

Hi,
I am trying Enhanced receiver determination - in an Idoc 2 Idoc scenario.
But when I selected Enhanced receiver determination in ID, it is asking for interface mapping.As it is an Idoc 2 Idoc scenario, I did not create any mapping objects in IR.
Is there any round about for this.
reg,

Hi,
if you are planning to send the Idoc to two systems then you do not need Enhanced Recieevr Determination.
You can add multiple Receivers In the receiver Determination under Configured Receivers and now the same idoc will be sent to 2 receivers.
Like mentioned by moorhty, Enahnced Receievr Determination allows you to dynamically determine receivers using a mapping program.! I dont think that is needed in your case
Regards
Bhavesh

Dyanamically determining receivers

Similar Messages

Maybe you are looking for