Context Object for IDOC in Receiver Determination

hi,
I am trying to filter the receivers based on the vendor values in IDOC ORDERS using Context Object.
I don't see the vendor field where i could filter the value.
Any ideas would be greatful.
Thanks,
Tirumal

hi,
Conditional Receiver determaintion is possible only on the Source Message. the reason being that the integration engine will first execute receiver determiantion--> interface determiantion --> message mapping.
If you are getting the IDOC as a source, then you can use the XPATH to do conditional receiver determination.
Regards,
Bhavesh

Similar Messages

Context object in xpath under reciver determination

hi all.
iam new to xi.
i just want to know what is the need of context object in xpath under reciever determination.
i tried a lot for understanding this context object but no way.
can any body expalin briefly.
waiting for ur great answer.
bye.
regards.
seeta ram.

suppose say you have a particular field in an xml and the xpath for the same is;
root/seg1/seg2/seg3/seg4/seg5/seg6/seg7/seg8/field, so instead of always using the whole xpath you can store it as a context object. It is like a variable say fieldcontextobject = root/seg1/seg2/seg3/seg4/seg5/seg6/seg7/seg8/field and in further development u can just ref. fieldcontextobject instead of the whole xml !!!!
http://help.sap.com/saphelp_nw04/helpdata/en/d6/e44fcf98baa24a9686a7643a33f26f/content.htm
More on Xpath:
/people/shabarish.vijayakumar/blog/2006/06/07/customise-your-xpath-expressions-in-receiver-determination
/people/shabarish.vijayakumar/blog/2005/08/03/xpath-to-show-the-path-multiple-receivers

** Interface Mapping - No Objects Found - IDoc is receiver

Hi Friends,
In our scenario, sender is File & receiver is IDoc. For each record in file, we need to created one IDoc. IDoc is CREMAS.CREMAS05. For this as usual we exported XSD and changed the occurrence of IDOC node as minOccurs="0" maxOccurs="unbounded" (as explained in Michael Blog - 2762) and did the message mapping successfully.
While create Interface Mapping, (Message interface (OB) for File, no message interface for IDoc, we directly use CREMAS.CREMAS05 in the target interface) and 'Read Interfaces' and select the Message Mapping option' it shows 'No Objects Found'. What could be the problem ?
Note that earlier it was working fine (Some times ago), now it is showing this error 'No Objects Found". I am very confused why this error is coming.
Kindly help me friends, to solve this.
Kind regards,
Jegathees P.

Friends,
Thanks for all your reply. When we click Read messages button automaticlly our source message (type) and target message (type) will be selected. Then, we select Mapping Program which is suitable for the Source & Target Message. When we do like this, it is showing the error 'No Objects Found'.
I want to check with you Is this due to what reason ? (Because, earlier it was working fine)
Eventhough we select 'Any' to 'Any' and select the mapping, save. After that If we do consistency check , it will show an warning message about the namespace issue.

Flat Idoc and receiver determination

Hi Folks,
I have a scenario in which the Idoc is sent to XI in a flat format (Flat Idoc) using tunneling mechanism. The receiver determination configured is conditional based (Verifies the values in the specified fields of the Idoc).
Now my question is as we know flat Idoc doesn't contain any fields like XML in the input payload, how the receiver can be identified?
Reminder: (Receiver determination is conditional based and verifies some field values in the Idoc structure)
Thanks,
SPMD

Hi Shabbirmdpasha,
You can use file adapter channel to get idoc flatfile and convert to xml idoc in the module of the file adapter (available in PI 7.1). You only need to make a relation with the type of idoc with the name of the file: for example, DESADV_xxxxxx.txt for all files with DESADV flatfile idoc's.
With this method, you know the interface of the outbound interface, and in the receiver determination you can check in the header of the idoc (dc40) to determine the target system.
PD: Sorry for me english...
Edited by: Oscar Navas on Dec 1, 2010 4:11 PM

IDOC error "receiver determination" while sending from R3 to XI

Hi all,
I'm trying to send an IDOC from R3 to BW thro' XI.
I created 2 business system for R3 & BW.
I created communication channel for receiving BW with IDOC adapter.
I created the receiver determination, interface determination & receiver agreement.
I also used IDX1,IDX2 to configure the port to load to IDOC.
When I send IDOC from R/3, It gets received in XI with the error message
<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
It didn't select the receiver.
Am I missing anything? Can anyone help me with this.
The same problem exists even I tried to get IDOC into a file in XI.
I appreciate all your help.
thanks
felix.

Hello Ujjwal,
Receiver is already defined in "Receiver Determination".
Even I refreshed CPA Chache many times but getting same error.
<?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">NO_RECEIVER_CASE_ASYNC</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thanks.
RP

IDoc to IDoc - conditional receiver determination issue

Hello All,
We are using XI 3.0 and this is my scenario:
Sender: IDOC from SAP system
Receivers: There are 2 receivers (one SAP and one non sap system).
I want conditional receiver determination based on the idoc field RCVPRN.
Integration Repository: I imported standard SAP IDOC FIDCC2 into IR and it is in "urn:sap-com:document:sap:idoc:messages" namespace of my SWCV. I am not creating data types, message types or message interfaces as I want to use the IDOC type directly as the interface name in Integration directory.
Integration directory: When I am creating receiver determination, I am getting a warning 'Message interface does not exist in any software components installed on this business system'. When I got to condition editor and want to choose the idoc field RCVPRN using XPATH, it is not showing the idoc structure.
In SLD, the correct product is installed on my sender ABAP technical system, and correct SWCV (into which i imported the IDOC) is installed on my business system. I refreshed cache and cleared SLD cache in ID. Still i get the same warning 'Message interface does not exist in any software components installed on this business system'.
How can i solve this issue? Any help is highly appreciated.
Thanks,
Chandra

Hi Chandra,
Can you check whether you have assigned or linked the SWCV with the Business system in SLD.
Just go to SLD and open the SWCV and check if it is linked with the BS od the sender system.
Since the sender is ABAP, you must have created the TS and BS using rz70, then see that that the SWCV is attached to the BS correctly. Under TS add the Product and then the corresponding SWCV.
Also check one thing: are u selecting the correct Communication component, under which the Interface is present.
Lastly if these doesnot work: In Integration Directory, Go to Environment-> Clear SLD Data Cache. Then try once again.
Cheers,
Souvik
Edited by: Souvik Chatterjee on May 16, 2011 3:39 PM

Transaction maintaining "number range objects" for IDOCs

Hi everybody,
does anybody know how to mainstain the number ranges for the different IDOC Types?
Thansk
Regards Mario

Hi,
we do not need an answer.
Thaks

Context object in Receiver Determination

Hi,
I am trying to use context object in receiver determination for routing messages to different receivers. From help document , I know that certain context objects are already present. Can we create our own context object in ESR and how?
I am using PI7.1
Thanks,
Neelansha

Hi Neelansha,
You can create a context object for only a request message(source), i.e, if you have a very deep nested structure then
you can use context objects which contains the XPath expression of your request message.
Can we create our own context object in ESR and how
For steps to create- go to context object - create new-->select type (int,string..)-
go to your source Service interface-click on context obj tab-select the element to which you want to assign the context obj name
refer activities mentioned in this help link
http://help.sap.com/saphelp_nw04/helpdata/en/d6/e44fcf98baa24a9686a7643a33f26f/frameset.htm
/people/prasadbabu.nemalikanti3/blog/2006/09/20/receiver-determination-based-on-the-payload-of-input-dataextended-xpathcontext-object
please note that you have to choose interface pattern as Stateless (XI 3.0 Compatible) ,otherwise you will not be able to see the context object in Receiver determination editor.
I found the standard context objects very useful and i think we can sometimes avoid using the dynamic configuration
i have used the file name context object in expression editor in receiver determination to create a condition for routing the messages to two different Business services.
Regards,
Srinivas

Receiver Determination steps for BPM scenario

Hi Experts,
Scenario : SOAP -> Calling different webservices
1. SOAP Client Request
2. Call the Initial webserive to get the unique Id. No need to pass any request to call this webservice, but it will give the response.
3. Take the Initial websrevice's response as a request to second webservice
4. Pass the SOAP client request to Third webservice
BPM steps
1. Receive Step for SOAP Request
2. Send Step for the Initial webservice call.
3. Transformation step Initial webservice response to request change.
4. Send Step for Second webservice (Pass the the Transformation step's target interface as a request)
5. Send Step for Third webservice ( Pass SOAP client request)
I am done with the BPM flow. Could you please help to do the Receiver Determination steps.
Usually I follow the below steps.
1. Sender Service to BPM
2. BPM to other services. I have a doubt with the second step. I am not passing the SOAP client request to Initial webservice. So, please tell me how to proceed further for the BPM Receiver Determination steps..
Thanks & Regards
Sara

Hey,
First, what is th purpose of your SOAP client request.
Is it just to trigger the BPM.
Second on what basis are you fetching the unique Id from initial web service.
If it is a normal scenario then, the reciever determination will be like this.
Soap client-> BPM
BPM->initial webservice
BPM->second webservice
BPM->third webservice
but in this particular scenario i dont know which data is being used to fetch the unique Id.
regards,
Milan

Context Object not found in Integration Directory

Hi experts,
I am trying to do a content based routing scenario using BPM.
The Scenario is
ASYNC -> SYNC -> ASYNC
The synchronous step here refers to a rfc call. The response from this determines the ASYNC systems to which data should be sent.
I have declared container objects REQ and RESP accordingly in the BPM. Also have a Context object for the response.
My issue is, while doing receiver determination, I am unable to find neither RESP message type ( for XPATH ) nor a context object declared in ESR for creating an expression.
Could someone please help/guide me to resolve this.
Please let me know if I was not clear.
Thank you.

Hi,
I am on 7.11.
The problem I am facing is that I am unable to find the corresponding structure to be used for XPATH.
As mentioned, the scenario is
ASYNC -> SYNC -> ASYNC's.
I have two container variables : REq and RESP. RESP is populated after the SYNC call. The message type for the subsequent ASYNC is REQ ( step description ).
So when I do receiver determination for ASYNC, I am able to see only REQ message type for building the expression. ( Obvious )
But I would need RESP to build it.
Please advise.

Context object

Hello,
             What is context object ? where this will be used?
                                                                          shyam

Hi Shyam,
when you have a deep nested XPATH, and you need to use it in multiple locations it can become tricky and so in your IR you create a context object to refer to the XPATH.
Note: For example, you have 2 receivers (receiver1 and receiver2). You need to choose the receiver based on the vale present in any source node. Then you can use context object to choose the receiver dynamically at run time.
Create a context object in IR and assign it to an outbound interface.
In ID, while creating Receiver Determination, in condition editor you can specify the conditions.. like multiple receivers you have to specify.
Creating Context Objects --> Quite Simple.
1. Create a new context object --> Right Click on Context Object --> New --> and then give the type of the context element. Integer, char ,etc.
2. Now, go to the Message Interface and you will find the column Context object. To the corresponding XML element, give your context object name
Comparison between XPath and Context Object
XPath
/InvoiceOut/customerData/address/postalCode = 69120
Context Object
postalCode = 69120
Regards,
Ramana.

Another question about receiver determination

Hi friends
Can we add a new receiver to the list of receivers in the receiver determination , based in some condition only for this new receiver.
Let us say we have the message 1 sent to receiver_1 and receiver_2 no matter what , but the message 1 should only be sent to receiver_3 according to some conditions.
my question if I can only put condition for the receiver_3 receiver determination , or do i have to write a UDF for mapping of the receiveres.
Thanks

Can we add a new receiver to the list of receivers in the receiver determination , based in some condition only for this new receiver.
yes you can add list of the receivers in the receiver determination , based on some condition .
my question if I can only put condition for the receiver_3 receiver determination , or do i have to write a UDF for mapping of the receiveres.
dont need to write any UDF's . u have to use Context Object/X-Path for REC3 in rec.det
for ex: field1 = 1000 -> rec3
field1 =900 ->rec1
Edited by: bhavanisankar.solasu on Feb 10, 2012 3:48 PM

Context Object Usage

Hi Folks,
How can i use context objects for passing the value of context object to another field in BPM .
<b>I am not asking about validating any condition using context Object and then doing something like Receiver Determination I am asking about how to pass the value of a field being declared as context object . </b>
I will appreciate i can get step by step information.
Regards

Hi..
Context Object are simply pointer to a specific XML tag. if you want to simplify your delopment you can define Context object for some fields and use the context objects. many message types come with their own context objects..
Refer this help..
http://help.sap.com/saphelp_nw04s/helpdata/en/6e/ff0bf75772457b863ef5d99bc92404/frameset.htm
Regards
Satya

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.

Receiver determination based on target msg???

Hi All,
Is it possible to do a receiver determination based on some field present in target msg. I know I can do the same if the field is present in source msg with the condition editor in receiver determination. But this will not help my scenario. I need to find the receiver based on a field in target msg. Is it possible?? If so, can u pls explain it???
Thanks & Regards,
Jai Shankar.

Jai,
Am on Sp14 and have not had the chance to try it out.
but, <b>I dont think you will need a extra Receiver Determination for the Enhanced Receiver Determination.</b>
What I understood out of that blog was that the Interface mapping between Source Interface and Receiver Interface will determine the receiver. So, you fill in the reciver service field with the actual receiver and this value will be taken as the receiver.
The Receiver Interface will be taken from the SAP basis SWCV.
http://help.sap.com/saphelp_nw04/helpdata/en/43/a5f2066340332de10000000a11466f/frameset.htm
Regards,
Bhavesh
Regards,
Bhavesh

Context Object for IDOC in Receiver Determination

Similar Messages

Maybe you are looking for