Requirement in receiver determination

Hi
We are on XI 3.0 SP18 and have the following requirement -
I have two receivers - A and B for a message - asynchronous mode . I want the message to reach receiver B only if it has successfully reached A - ( technically successful - as in any async scenario ) .
How can this be achieved ? Can enhanced/dynamic receiver determination solve my requirement ? Please elaborate .
Thanks in advance for your answers/solutions.

You have to use a BPM model to control to check the response from Receiver A and make a decision to send the message to receiver B.
Also keep in mind a BPM model will additional concerns around the performance of integration scenario, so please make sure these requirement is completly necessary.
In other way you can accomplish the same by using an intermediate sotrage such as JMS storage and JDBC storage etc.
Thanks

Similar Messages

How many Receiver determination in File to SOAP scenario

Hi,
I am trying a File -SOAP-File scenario, where file will be send to PI asynchronous. BPM is configured to receive the file and
call the web services and get the response (Synchronous call) .After that BPM send the file asynchronous to File via FTP .
It is basically asynchronous/ Synchronous bridge scenario.
To do this I have have configured the BPM & created 3 Communication channel . 1 sender (File) & 2 receivers ( SOAP & File)
But i got confused in Receiver determination. How many Receiver determinations do we require in this step? 2 or 3. If 3 how they will look like. I believe Interface determination is same as Receiver determination. I am suing Business System to send & recv the file.
Points will be rewarded for suitable answer.
Thanks

hi,
You require 3 receiver determinations.
one from File to BPM(XI)..
another from BPM to SOAP and other from SOAP to FILE.
This is exactly the same scenario.
RFC Scenario using BPM --Starter Kit
Thanks,
Vijaya

File name based routing in Receiver determination

Hi experts,
I have a requirement to do receiver determination based on file names which are dynamic.To put it clearely, i will be having two files in my source File location and i need to route it based on the file name to two target systems.
The file name are like Month(changes everymonth)_TargetSys1 and month_targetSys2.
I dont need any conversions ,so i am not using any IR objects.
To pick files i kept *.txt in sender channel, and in receiver determination condition i was trying to use context object called 'Filename'.But it doesnt work asthe file name changes every month.
Is there any option to take substring from the input file name (say targetSys2 from month_targetSys2.) and put it as a condition for receiver determination.
There is not DT or structure of the incoming file , as there are no modification to be done with the content.
Regards,
Anika

you need to have the structure in case you want to route it via the xpath.
Else another option is to code the enhanced receiver determination and using a java mapping with dynamic configuration read the filename and then dynamically create the receiver determination.
http://help.sap.com/saphelp_nw04/helpdata/en/43/a5f2066340332de10000000a11466f/content.htm

Question about Receiver Determination step in BPM

Hello all,
I have a BPM process similar to Multicat BPM Pattern.
I have some questions regarding how the Receiver Determination works:
1. Does it have to have interface determination in the Integration Directory?
2. Does that interface determination (including the mapping) takes place when sending a message to a receiver from that Receiver Determination step,
or should I perform a Mapping step explicitly in the process?
Thanks ahead,
Yoav.

Yoav,
Am not sure if I understood your requirement compltely.
Case A:If you are using a send step without a Transformation Step.
Then Send will have message A being sent out from BPm and then , during Interface Determiantion this will be transformed into Message B by Mapping in Interface Determination and this message B will be received by receiver
Case B:If you have a transform and then a Send
In this case, the mapping has been done, so you have the message B with you and so, them message sent from the BPM will be message BHope this clarifies,
Regards,
Bhavesh
Message was edited by: Bhavesh Kantilal

Use of Receiver determination step in BPM

Hi,
I am not clear about the exact use of Receiver determination step in BPM. From my understanding, it is used for synchronous communication with many receivers configured, for eg. Multicast etc. Can anybody explain the use of receiver determination with any specific requirement example.
Regards,
Santosh

HI,
The usage of Receiver Determination depends on how you have designed your BPM. You can have the mapping getting executed in your BPM itself using a TRANSFORM step or you can do it in your Inteface Determination if you are not doing it in your BPM.
If you do the mapping inside the BPM using Transformation step, then you need to send the Message i.e. Mapped message . In this case, your Interface determination will only determine the Receiver Interface, and it will not execute the interface mapping . (if you are not providing the Interface mapping in the Interface determination).
Example is given here-
http://help.sap.com/saphelp_nw2004s/helpdata/en/14/d5283fd0ca8443e10000000a114084/content.htm
Thanks
Swarup

IDoc TO File: Receiver Determination did not find any receivers at all

Hi,
We have IDoc to file scenario, where based on attributes present in IDoc we have configured different receivers.
Everything was working fine and files were getting created based on the receiver determination criteria.
But there is one change done in custom IDoc to re position the attributes.
Idoc before changes was having NAME1 and NAME2 above KATR6 and KATR7 and after change it looks like below:
So there is no change in segment and no change in mapping but the attributes KATR6 and KATR7 are used to determine the receiver.
Cache refresh is done for both ESR and ID. I have re - entered the receiver determination criteria just to ensure that change should reflect.
But still when I am triggering outbound IDoc from ECC to PI, the transaction is getting errored out with below error:
"ErrText": "Processing error = Receiver Determination did not find any receivers at all",
Can any one providee some idea what could be the reason and what is the right approach to resolve this issue.
Thanks,
Vertika

Hi Krupa,
I have marked your answer as helpful answer and delete of metadata wasn't required.
Reload works . But thanks for your suggestion.
Thanks,
Vertika

XPATH condition in receiver determination.. Sum one of the filed

Hi,
This is my input payload.
segment "Record" will be coming multiple times.
<ns:MT_Account xmlns:ns="urn:com.statement">
-<BalanceRecs>
- --<Record>
<field1>CUA</field1>
<field2>0.00</field2>
<field3>324612.28</field3>
<field4> LTD</field4>
 -----<numRecs>0</numRecs>
</Record>
--- <Record>
<field1>CUb</field1>
<field2>0.00</field2>
<field3>324612.28</field3>
<field4> LTD</field4>
<numRecs>2</numRecs>
</Record>
--- <Record>
<field1>CUc</field1>
<field2>0.00</field2>
<field3>324612.28</field3>
 <field4> LTD</field4>
<numRecs>0</numRecs>
</Record>
</BalanceRecs>
Requirement:
I need to calculate the sum of field "numrecs".
If the sum is 0, then pass to BPM(IP_BPM)
If the sum is > 0 then pass to System B.
I tried using the below blog from shabarish..
/people/shabarish.vijayakumar/blog/2006/06/07/customise-your-xpath-expressions-in-receiver-determination
/p1:MT_ActBalance/BalanceRecs/BalanceRecord[sum(numRecs) = 0] EX --> BPM
/p1:MT_ActBalance/BalanceRecs/BalanceRecord[sum(numRecs) > 0] EX --> SystemB
Is there anything im missing .. kindly suggest.
Thanks
Deepthi.

Hi Mark,
It is working only for one receiver.
i mean
<numRecs>0</numRecs>
<numRecs>0</numRecs>
<numRecs>0</numRecs>
The message is going correctly when the sum value is 0. ie to BPM.
<numRecs>0</numRecs>
<numRecs>2</numRecs>
<numRecs>0</numRecs>
OR
<numRecs>2</numRecs>
<numRecs>0</numRecs>
<numRecs>0</numRecs>
When I pass the above payloads, it is going to both the receivers.
Since the total is 2, it should go only to systemB
Any idea?
This is working perfectly for enhanced receiver determination. I dont want to use enhance version for this simple case.

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

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

Receiver Determination

Hi,
We are running SAP PI 7.11.
Input message:
<?xml version="1.0" standalone="yes"?>
<SITE_ERROR xmlns="http://test.com/SITE_Error">
<ERROR_DATA>
 <ERROR_DATE>20110120</ERROR_DATE>
 <ERROR_TIME>060002</ERROR_TIME>
</ERROR_DATA>
<SITE_INFO>
 <SITEID>AZAZ</SITEID>
</SITE_INFO>
<ERRORS>
 <ERROR>Version 2.00</ERROR>
 <ERROR>Bla Bla 1</ERROR>
 <ERROR>Bla Bla 2</ERROR>
 <ERROR>Bla Bla 3</ERROR>
</ERRORS>
</SITE_ERROR>
I require to route the message for delivery if a second node in XPATH /SITE_ERROR/ERRORS/ERROR occurs else it will not be delivered.
It seems that receiver determination with a condition in the form of a XPATH expression should solve this problem as I would be able to determine if there is a second "ERROR" node and if there is then route it for delivery. However when the rule is not satisfied then for "If No Receivers Is Found, Process as follows:" rule I set "ignore".
Please could you leant some assistance in constructing the XPATH expression? I have it down as:
(/SITE_ERROR/ERRORS/ERROR[(2)] EX )
Your assistance in this matter will be greatly valued.
Regards
Willie Hugo

your Xpath condition seems fine as you have used EX in that it will check for existance of the field element and will route that interface to mentioed system..
which is right.. but as you mentioed its not working I think there is possibility that its problem of cache ..
just to rechcek..
-- check Cache status..
-- go to SXI_CACHE and check status for your receiver determination object..
-- if everything is not green then try to activate receiver determination one more time.. just to be on safer side you can reactivate all ID side objects..
then again check your scenario..
this is about Xpath..and as you mentioed "If No Receivers Is Found" you have selected igonre then in this case it wll just ignore this message and will not show in SXMB_MONI also..
here you can select alternate business system or for timebeing select same receiver system and check.. if it is working..
it should work as your configuration looks fine..
Thanks,
Bhupesh

Receiver Determination in multi mapping

Dear Folks,
I am facing a difficulty in implementing conditional receiver determination in my scenario. This is an IDOC to FILE scenario and requirement is IDOC needs to be split in multiple messages and specific messages to be delivered to different warehouses using FTP.
I have implemented multimapping 1:N and able to split the IDOC as per the requirement. But when I execute conditional receiver determination, all the splitted files are sent to all the warehouses.
The input is
<IDOC>
 <Segment>
 <warehouse_no>1</warehouse_no>
 </Segment>
 <Segment>
 <warehouse_no>2</warehouse_no>
 </Segment>
 <Segment>
 <warehouse_no>3</warehouse_no>
 </Segment>
</IDOC>
and output I want as
File No 1
<MT_WarehouseDetails>
 <warehouse_no>1</warehouse_no>
</MT_WarehouseDetails>
sent to warehouse 1
File No 2
<MT_WarehouseDetails>
 <warehouse_no>2</warehouse_no>
</MT_WarehouseDetails>
sent to warehouse 2
File No 3
<MT_WarehouseDetails>
 <warehouse_no>3</warehouse_no>
</MT_WarehouseDetails>
sent to warehouse 3
currently I am getting all the files in all the folders.
Your help will be appreciated.
- Shri

hi,
it is indeed a nice solution here is what I propose:
define a new communication component called XI_BUS, define a sender comm soap channel SND_SOAP_IDOCTYPE and a receiver soap comm channel RCV_SOAP_IDoctype that points to the sender one. (you will need a service username and password in the pi system). check this link on how to configure your RCV comm channel to point back to your PI system [http://help.sap.com/saphelp_nw04/helpdata/en/2b/d5653fd1d3b81ae10000000a114084/frameset.htm]
source system -> XI (in this flow you do the multi mapping)-> XI_BUS (using RCV_SOAP_IDOCTYPE) (basically re-routing it back to XI)
XI_BUS(using SND_SOAP_IDOCTYPE) -> XI ( here you use your extended receiver determination) -> RCV_1
 -> RCV_2
 -> RCV_n
I hope this helps

Receiver Determination - Configuration Overview for Receiver Determination

Hi All,
I was trying on some tutorial for Calling RFC(sender) and creating a File at Receiver site.
I've configured all the required setting at the Design: Integration Builder.
As for Configuration: Integration Builder. Until the Step where I required to setup the Receiver Determination, there is this part "Configuration Overview for Receiver Determination". where i have to maintain the "Receiver Service", else i will hit this error "Enter the receiver service".
The steps which i followed was :
1. Create 2 Communication Channel for Sender/Receiver in the Business System.
2. Create a Sender agreement.
3. Create a Receiver agreement.
4. Create a Interface determination.
5. Lastly "Configure the Overview for Receiver Determination" for Receiver Determination
The problem which I'm facing now is I have nothing in the "Configure the Overview for Receiver Determination" at all even i have created the sender/receiver agreement and interface determination.
While some troubleshooting, under the If No Receiver Is Found, Proceed as Follows: I tried choosing the "Continue Message Processing with the Following Receiver" radio button and choose the Receiver for the Service then hit the save button.
The error "Enter the receiver service". pop up but now, the Receiver service was shown under the "Configure the Overview for Receiver Determination". When i try choosing back the "Terminate Message Processing with Error (Restart Possible) and hit the Save button. The Receiver service goes missing again.
Any Idea what happen ? or anything i missed out ? thanks in advance.

Hello
Check if you have the issue in the kba #1538009 Error When Executing Open - Object not found.
Also see note #1466011 Usability Improvements in Directory:
o Don't show deleted objects in navigation tree
When you delete an object in Directory the link to this object is not
automatically deleted from Configuration Scenario. You need to manually
open every scenario and remove such 'broken' link. In scenario editor
broken links are displayed in grey font and therefore can be easily
identified. Unfortunately the navigation tree in 7.1 (in contrast to
XI3.0) doesn't make difference between existing and broken links and
shows them as they all leads to existing objects.
Regards
Mark

Receiver Determination conditions

Hi All
We have a scenario where a IDOC is trigerd in the ecc system and multiple IDOC is send to the XI system. Only when a certain field is 3 char or 5 char or 7char long should the file be dumped on the server. Is is possible to have a condition in the receiver determination to say if the field is between 100 and 999 or between 10000 or 99999 or between 1000000 and 9999999 to only create the files?
Any help will be appreciated.

hi,
Its quite easy to achieve this requirement.
You can edit the xpath in the Recv. Determination and then in combination with xpath standard functions achieve this.
have a lo0k at my blog - Customise your 'XPATH' Expressions in Receiver Determination
Also for xpath functions ref: http://www.w3schools.com/Xpath/xpath_functions.asp

Receiver determination issue

Hi all,
I have a typical scenario, where the message mapping is such that a particular child node in the target will get mapped (created) only if certain logic gets satisfied. Otherwise the child does not get created.
Now, my problem is - I want to send this message to receiver only if this child node exists. (There is no point in sending empty message to receiver)
The condition in receiver determination can use only source message since message mapping is executed after the receiver determination.
Can anyone pls help ?
Thanks,
- Shankar.

Hi Shankar,
I'm not sure if you can do that with normal condition in receiver determination
I think this can be done with a condition, (that is the logic you use to decide wheter to create the node or not), just it depends on how much complex is the condition.
If the condition is too complex I think you cannot use just the condition editor to define it.
But consider that in any case enhanced receiver determination can be used even if you have a fixed received.
You can view it in a different way, you do not have a fixed receiver, your receiver is "A" if condition is true and your receiver is "null" if condition is not true.
Is'nt this your requirement?
So I would say assign the receiver in the mapping if the condition is fulfilled, otherwise do not assign a receiver, this will result in a "no receiver found" and you can stop the message processing.
Regards,
Sergio

** XPath condition not work well in Receiver Determination.

Hi,
My scenario is having 3 receivers. I have 'Student' is the data type. I use the same data type for Source & Target Message Types. Requirement is I have to send
1) only records which are having SCOURSE = 'BE' to receiver 1
2) only records which are having SCOURSE = 'MCA' to receiver 2
3) only records which are having SCOURSE = 'MBA' to receiver 3
My Input.xml file contains the following records.
<?xml version="1.0" encoding="UTF-8"?>
<ns0:THIRD_MT_OB xmlns:ns0="http://ganesh_third">
 <STUDENT_INFO>
 <ST_ID>10020</ST_ID>
 <SNAME>Raja</SNAME>
 <SCOURSE>BE</SCOURSE>
 <SFEES>3000</SFEES>
 <SMARKS>1200</SMARKS>
 </STUDENT_INFO>
 <STUDENT_INFO>
 <ST_ID>10021</ST_ID>
 <SNAME>Ram</SNAME>
 <SCOURSE>MCA</SCOURSE>
 <SFEES>3000</SFEES>
 <SMARKS>1200</SMARKS>
 </STUDENT_INFO>
 <STUDENT_INFO>
 <ST_ID>10022</ST_ID>
 <SNAME>Ram</SNAME>
 <SCOURSE>MBA</SCOURSE>
 <SFEES>3000</SFEES>
 <SMARKS>1200</SMARKS>
 </STUDENT_INFO>
</ns0:THIRD_MT_OB>
I set the Xpath condition in the Receiver Determination Step and add the 3 receivers for against the conditions.
Our problem is, If we send the single record in the input file, the corresponding receiver is selected correctly and we get the output file for that receiver. But, if we send the all combination of records (MCA,BE,MBA) 3 receivers are selected and the 3 output files we get. But, the three files are having the all records (MCA,BE,MBA). Instead, we want the first file should only have MCA record, the 2nd file should only have BE record and finally the 3rd file should only have MBA record. That means each receiver should receive only one record for the above input.
Friends, I though it will work for the 'XPath Expression' against receivers in the Receiver Determination Step. But, it didn't work. (Records are not split up)
How do achieve this, friends?
Could you kindly help me to solve this problem.
Kind Regards,
Jeg P.

If you are trying to split you input msg and send it to 3 different receivers using conditional receiver determination then it will not work. Once a condition is meet in the receiver determination then the entire msg is forwarded to the corresponding receiver, that is why when you have a single row in your input file which results in a single msg in XI the conditional receiver works. Now when you have multiple rows in your input file still only one msg is being created in XI for all the rows currently so all the conditions are being meet and the msg is forwarded to all the receivers.
If you are using FCC in the sender side then use the "recordset per msg" parameter to consider each row of your input file as a separate msg in XI and the rest will automatically fall in place.
Cheer's

Requirement in receiver determination

Similar Messages

Maybe you are looking for