Condition for Receiver Determination

Can we write a condition,where in if the files are coming from the specific folder it has to be recieved by a particular service and if its coming from a diff folder it has to be recieved by another service

Hmm of no use..
its not recognising the condition for the folder
Ex:
The Requirement is we have 4 input folders which sends the file .we are using bpm to process them.
The reqrmnt is now that we want the same bpm to run independently for each folder.so we have imported the same bpm in the configuration scenario with four different names.and in the receiver determination we gave the condition like u201Cdirectory=D:/out/xminu201D int_bpm1 and u201Cdirectory=D:/out/xmaxu201D int_bpm2

Similar Messages

Error evaluation condition in receiver determination

Hi,
In XI 3.0 stack 11, for the incoming file, the receivers are determined based on the content of the input data.
In the receiver determination the conditions were given for each receiver and it was working fine.
Now, all of a sudden, its giving error as 'error in evaluating the condition in receiver determination' with some program name as CL_SAI_SWF_RULE_ENGINE (CX_RD_PLSRV).
Could any one help me resolving this issue? Let me know if you need any more details w.r.t the issue.
Thanks in advance!!
Regards,
Sasikumar

Hi,
I'm experiencing the same problem. See message below. Also running SP11. What might be wrong with the xpath expression? I have removed all namespaces from the xpath and the input xml message. Any suggestion is more than welcome!
Kind regards, Guy Crets
<?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 evaluating a condition: The exception occurred (program: CL_SWF_RLS_CONDITION==========CP, include CL_SWF_RLS_CONDITION==========CM00Q, line: 160)</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error when determining the receiver: Problem evaluating a condition: The exception occurred (program: CL_SWF_RLS_CONDITION==========CP, include CL_SWF_RLS_CONDITION==========CM00Q, line: 160)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

PI 7.1 - condition during receiver determination

Hi,
I am trying to do the receiver determination condition in the condition editor of integration directory but XPATH or context objects of my interface (corresponding to my software component version) do not appear in the window for maintaining the condition.
I had no difficulty when following the same process during 7.0 or earlier versions but it seems to be issue in PI 7.1.
Anyone else also faced a similar situation or is there any extra step I need to ensure before going for receiver determination (standard not enhanced)?
Your help would be appreciated.
Cheers.

My scenario is:
Source system -> PI (ccBPM) -> Target system
Now I have number of ccBPMs and there would be one picked up based on the payload from source system interface. For this my configuration objects are as follows:
Sender agreement with (source comm component and source system outbound interface)
Receiver determination - at this stage I want to figure out which ccBPM should get executed and hence condition based on payload
interface determination - goes to receiver step of ccBPM with message type same as outbound interface from source system
I have another receiver determination, interface determination for target system interfaces from ccBPM and then receiver agreement.
But in this overall scenario key part is first receiver determination step where ccBPM as receiver is to be determined.
I checked up all my objects again to find out any missing gap from my understanding. But I am not able to get the interface (source system interface) in the condition editor. I tried maintaining the XPATH manually but it ends in error during execution suggesting that receiver could not be determined.
Any more suggestions please?

Conditions in Receiver Determination

Hi
        I am doing a scenario in which we are sending PO from R3 to one of two different web-services through XI using RFC.We have already transported our scenario to Production.Using RFC we are executing Webservice.
        Now there on production we want to put conditions in receiver determination according to message data. In F4 help of condition it is not showing message feilds so I filled condition manually but it is not woking. Is there any other way to put conditions there?
       Have anyone face this problem?
       what is the soution of this problem.
       Its urgent!!
thanks in advance
Regards
Sami
Message was edited by:
        sami qureshi

Hi Sami,
Strongly suggested: Do the changes in Dev and re-transport.
in dev u may create a context obj and assign that to ur msg interface. and use this context obj for conditional routing.
Hope it helps.
Regards,
Latika.

Reg. condition based receiver Determination

Hi,
    I need to send the records to two systems based upon the value
For Ex. All the material group record letz say (1,2,3,4,5,6) Shuld go to Receiver1 and only the records which belongs to material grp shud go to Receiver2.
I am trying using Condition based Receiver Determination
   For Receiver 1 :-
              I didnot give any condition.Coz all the records have to go to Reciver1.
   For Receiver 2 :-
                 I have written the condn in the Interface determination
            i.e) Material Group = 2.
But All the records are going to these two receivers.I have tried everything.
Thanks in advance
Regards
Anandan

Anandan,
Similar situation has worked for me. Please check the condition you have mention in Interface Determination.
In the Interface determination you need to have 2 inbound interfaces. Specify the respective condition for each inbound interface.
Example: if the Response field has the value as "Success" or "Failure" the message has to go to first interface. The message has to go to second interface only if the response is "Failure". so you can provided following condition in the interface determination:
<b>Condition 1:For first inbound interface</b> (/p1:MessageType/RecordSet/Response = F) OR (/p1:MT_RESPONSE_FROM_PS_BI/RS/Response = S)
<b>Condition 2:For second inbound interface</b> (/p1:MessageType/RecordSet/Response = F)
The above condition has worked for me. Hope this would be helpful to you.
Regards,
Sridhar

Special characters conditions in receiver determination

hi there,
i have the following problem:
There are conditions in receiver determination to find the proper xsl mapping for different segments in IDocs.
That works fine.
But if there are special characters like &, the interface mappings can't be found, because for the conditions the xml is already corrupt.
So, i've tried to replace all occurrences of & with & in a java mapping that is called before the xsl mappings.
It doesn't work, because in that case conditions are processed before the java and xsl mappings.
Do you have any idea how to replace special characters before conditions in receiver determination are processed?
thx in advance
Stefan

Handling the Special Characters in XI
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/9420 [original link is broken] [original link is broken] [original link is broken]
Find out which character encoding the receiver system expects and put the same to the receiver channel.
By default the file adapter would create a file with UTF-8, which might not be useable for the receiver.
check this thread.
Handling Special Characters
check the document :
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/502991a2-45d9-2910-d99f-8aba5d79fb42
Depends upon encoding methods handling will differ,
you can use ISO-8859-1 or ISO-8859-2 instead of UTF-8 for some special characters.
check this blog:
Unicode File Handling in ABAP
*Suppress Special Character *
Suppress Special Character

Multi Mapping using condition & Dynamic Receiver determination – Used XSLT Mapping

Dear Experts,
     I am struggling to identify an error on the Technical Routing. Firstly according to my scenario, I receive an XML file with multiple PO's and I have to split the file to 2 different target messages. and also according to the source payload I have to send the file to 2 different receivers. first receiver is ABAP Proxy to the back end system and the 2nd one is to a file location. I have used XSLT to split the message into 2 target message type and I have used a XSLT mapping for receiver determination. Does any one have any idea of what I am doing wrong.
Note: some time I will only be able to fill in on target message.
I have attached my XSLT message split mapping with this post, please let me know if you have further question.
Your help is more appreciated.
Advance Thanks,
Pradeep
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:sap="http://www.sap.com/sapxsl" version="1.0">
<xsl:variable name="vFlag"/>
<xsl:variable name="vPONUM" select="POTRACKING/Lines[1]/PONumber"/>
<xsl:template match="/">
    <ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">
      <ns0:Message1>
        <ns1:MT_Tracking xmlns:ns1="http://www.findel-education.co.uk/axapta">
          <xsl:for-each select="POTRACKING/Lines">
            <sap:call-external class="ZCL_VNAP_OBJECTS" method="CHECK_PO_EXIST">
              <sap:callvalue param="IP_EBELN" select="string(PONumber)"/>
              <sap:callvariable name="vFlag" param="EP_BOLEAN" type="string"/>
            </sap:call-external>
            <xsl:if test="$vFlag = 0">
              <Lines>
                <DDate>
                  <xsl:value-of select="DespatchDate"/>
                </DDate>
                <PONumber>
                  <xsl:value-of select="PONumber"/>
                </PONumber>
                <POLine>
                  <xsl:value-of select="POLine"/>
                </POLine>
                <QTY>
                  <xsl:value-of select="Quantity"/>
                </QTY>
                <VendorMaterial>
                  <xsl:value-of select="VendorMaterialNumber"/>
                </VendorMaterial>
                <AccountRef>
                  <xsl:value-of select="AccountReference"/>
                </AccountRef>
                <ConsignNumber>
                  <xsl:value-of select="ConsignmentNumber"/>
                </ConsignNumber>
                <CarrierURL>
                  <xsl:value-of select="CarrierURL"/>
                </CarrierURL>
                <ConsignURL>
                  <xsl:value-of select="ConsignmentURL"/>
                </ConsignURL>
              </Lines>
            </xsl:if>
          </xsl:for-each>
        </ns1:MT_Tracking>
      </ns0:Message1>
      <ns0:Message2>
        <ns2:MT_Tracking xmlns:ns2="http://www.findel-education.co.uk/ecc/ax/po/ftp">
          <xsl:for-each select="POTRACKING/Lines">
            <sap:call-external class="ZCL_VNAP_OBJECTS" method="CHECK_PO_EXIST">
              <sap:callvalue param="IP_EBELN" select="string(PONumber)"/>
              <sap:callvariable name="vFlag" param="EP_BOLEAN" type="string"/>
            </sap:call-external>
            <xsl:if test="$vFlag = 1">
              <Lines>
                <DDate>
                  <xsl:value-of select="DespatchDate"/>
                </DDate>
                <PONumber>
                  <xsl:value-of select="PONumber"/>
                </PONumber>
                <POLine>
                  <xsl:value-of select="POLine"/>
                </POLine>
                <QTY>
                  <xsl:value-of select="Quantity"/>
                </QTY>
                <VendorMaterial>
                  <xsl:value-of select="VendorMaterialNumber"/>
                </VendorMaterial>
                <AccountRef>
                  <xsl:value-of select="AccountReference"/>
                </AccountRef>
                <ConsignNumber>
                  <xsl:value-of select="ConsignmentNumber"/>
                </ConsignNumber>
                <CarrierURL>
                  <xsl:value-of select="CarrierURL"/>
                </CarrierURL>
                <ConsignURL>
                  <xsl:value-of select="ConsignmentURL"/>
                </ConsignURL>
              </Lines>
            </xsl:if>
          </xsl:for-each>
        </ns2:MT_Tracking>
      </ns0:Message2>
    </ns0:Messages>
</xsl:template>
</xsl:stylesheet>

Hi Hareesh,
Please find my determination in the XSLT below, I am using enhanced receiver determination.
<xsl:transform xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:sap="http://www.sap.com/sapxsl" xmlns:p1="http://sap.com/xi/XI/System" xmlns:ns="urn:sap-com:document:sap:idoc:messages" version="1.0">
<xsl:variable name="vFlag"/>
<xsl:variable name="vAX" select="0"/>
<xsl:variable name="vSAP" select="0"/>
<xsl:variable name="vBoth" select="0"/>

<xsl:template match="/">
    <xsl:for-each select="POTRACKING/Lines">
      <sap:call-external class="ZCL_VNAP_OBJECTS" method="CHECK_PO_EXIST">
        <sap:callvalue param="IP_EBELN" select="string(PONumber)"/>
        <sap:callvariable name="vFlag" param="EP_BOLEAN" type="string"/>
      </sap:call-external>
      <xsl:choose>
        <xsl:when test="$vFlag = 0">
          
          <xsl:variable name="vAX" select="$vAX + 1"/>
        </xsl:when>
        <xsl:when test="$vFlag = 1">
          
          <xsl:variable name="vSAP" select="$vSAP + 1"/>
        </xsl:when>
      </xsl:choose>
    </xsl:for-each>
    <xsl:if test="$vSAP > 0">
      <xsl:if test="$vAX > 0">
        <xsl:variable name="vBoth" select="$vBoth + 1"/>
        <xsl:variable name="vSAP" select="0"/>
        <xsl:variable name="vAX" select="0"/>
      </xsl:if>
    </xsl:if>
    <xsl:if test="$vBoth > 0">
      <p1:Receivers>
        <Receiver>
          <Service>
            <xsl:text>BS_AXAPTA_TST</xsl:text>
          </Service>
        </Receiver>
        <Receiver>
          <Service>
            <xsl:text>BS_ECQCLNT300</xsl:text>
          </Service>
        </Receiver>
      </p1:Receivers>
    </xsl:if>
    <xsl:if test="$vAX > 0">
      <p1:Receivers>
        <Receiver>
          <Service>
            <xsl:text>BS_AXAPTA_TST</xsl:text>
          </Service>
        </Receiver>
      </p1:Receivers>
    </xsl:if>
    <xsl:if test="$vSAP > 0">
      <p1:Receivers>
        <Receiver>
          <Service>
            <xsl:text>BS_ECQCLNT300</xsl:text>
          </Service>
        </Receiver>
      </p1:Receivers>
    </xsl:if>
</xsl:template>
</xsl:transform>

Condition in receiver determination

Hi,
I am using PI 7.1. My input message is
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_EODReport xmlns:ns0="http://hsbc.com">
   <Record>
      <ReportDate></ReportDate>
      <ACHEODReportFlag></ACHEODReportFlag>
   </Record>
</ns0:MT_EODReport>
I want to put a condition in Receiver Determination to check whether   <ACHEODReportFlag> tag contains value 'X' . How should i put this condition?

>
Shilpa Korad wrote:
> Hi,
>
> I am using PI 7.1. My input message is
>
> <?xml version="1.0" encoding="UTF-8"?>
> <ns0:MT_EODReport xmlns:ns0="http://hsbc.com">
>    <Record>
>       <ReportDate></ReportDate>
>       <ACHEODReportFlag></ACHEODReportFlag>
>    </Record>
> </ns0:MT_EODReport>
>
> I want to put a condition in Receiver Determination to check whether   <ACHEODReportFlag> tag contains value 'X' . How should i put this condition?
Condition Editor of RD....Left operand select Xpath and choose the node that you want click Ok.......from the dropdown select = operator.....Right Operand select Constant and give the value as X....

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

XPATH condition in Receiver Determination in PI 7.1

Hi all,
I'm doing a Inbound 850 Scenario (no BPM involved)...based on the condition for (/LIST/S_ISA/S_GS/S_ST/S_BEG/D_353 = 00) its should either create ORDERS.ORDERS05 or create ORDCHG.ORDERS05 if (/LIST/S_ISA/S_GS/S_ST/S_BEG/D_353 = 04)...I'm giving the condition in interface determination and multiline selected in the Xpath editor
I'm using PI 7.1 and irrespective of the condition it always creats Orders.Orders05, I have 2 receiver agreements also for both receiving interfaces...
Any solution on how to debug?
Thanks,
Srini
Edited by: Srinivas Davuluri on May 12, 2009 10:56 AM

I forgot to give the prefix...mistake from my side

Routing condition in receiver determination

Hi,
In my RFC to JMS scenario, i encountered with a strange routing condition for the receiver determination.
I have routing condition like " string length (one field in Bapi)<1" .
Could any one help me how to implement this?
Regards,
Vishnu.

HI check the below links for reference
https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_all&query=transactional
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a1a0eb43-0b01-0010-23aa-908cc4eaabcd
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/pcd!3aportal_content!2fcom.sap.sdn.folder.sdn!2fco...
note:reward points if solution found helpfull.....
regards
chandrakanth.k

Generic condition in Receiver Determination

hi,
in receiver determination, we can define a Condition, but in condition editor, under "context object", we have only some standard parameters of PI adapter like "FileName" like http://sap.com./xi/XI/System/file used in Dynamicconfiguration. I saw also some of seeburger... so...
How can we define our own "_generic_" condition ? Do I need to create an Adapter ?
Note: I do NOT want to define a context object (in ESR) and affect it to a field of a service service, because it's limited to one interface , and I want a generic context which could be used for all interfaces (already developped and to be developped).
Thanks.
Mickael

hi Himadri,
thanks for your interest, but no, that's not my subject. I want neither a specific context object based on only one service interface (your blog) nor to define dynamically the receiver by using mapping functions... I would like to have my own predefined context in Context Objects like these of SAP, example: Filename from DynamicConfiguration of a FILE adapter.
I know my topic is a litle too technic... but it's a part of a more global solution (*) to do a pre-control on all my existing interfaces (!). so the solution should be as less intrusive as possible: I do not want to change in depth all my interfaces... supens...
Regards.
Mickael
(*) I'm studying different ways, and this topic is one of them

Use of range in case of XPATH for receiver determination.

Hi Experts,
I need to achieve the following using standard receiver determination.
The material number in the source message structure has to lie within a perticular range and that should decide the receiver of the message.
For example:
MT_SRC
|---- Ele1
|----
MaterialNo.
If MaterialNo is between 100000100 and 100001000 then it should be sent to BS_TGT1 else it should be sent to BS_TGT2.
Is it possible to achieve this using the standard conditional receiver determination using XPATH and if yes, how exactly?
Regards,
Amol

Hi Amol,
I think its possible. Never tried though for a range.
Go through this link and check out what is described under the section "Notes Regarding the Use of XPath Expressions"
http://help.sap.com/saphelp_nw04/helpdata/en/43/a513f2632c332ce10000000a11466f/frameset.htm
I am not sure whether it will work for two conditions though, i.e. for a range( Greater than 100000100, less than 100001000).
Just try and let us know.
Regards,
Sanjeev.

"Problem evaluating a condition" at Receiver Determination

Hi,
I've created a complex mail to rfc interface, in which, message is being send as mail attachment and service inbound interface has multiple operations (each for corresponding rfc).
at Receiver Determination, rule was created with multiple conditions, in order to determine correct "Communication Component" (multiple receiver agreement and interface determination were created to supported this "multi interfaces" scenario).
If no receiver was found message is ignored.
once in a while, bad non-xml messages (e.g., "asdfasdfasdfffdfdsasdf") are being send, is this case, while PI is trying to determining the receiver (i.e., evaluate Receiver Determination conditions) exception is being thrown, message is therefor has system error status* (at sxmb_moni) and it can not be ignored (as i wanted it to be).
how can i workaround this problematic scenario?
Regards
Uri
*Error message (sxmb_moni)
<?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 evaluating a condition: An exception has occurred.</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error when determining the receiver: Problem evaluating a condition: An exception has occurred. Problem evaluating a condition: An exception has occurred. An exception has occurred. An exception has occurred. An exception has occurred. An exception has occurred. An exception has occurred. Problem extracting values from the Payload: Check line 2 column 1 of the XML document</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

Abhishek,
10x for your replay, but as far as i understand this is exactly the case here.
conditions are:
cond1: (/rfc: RFC1 ~ *)
cond2: (/rfc: RFC2 ~ *)
this works as expected in cases of xml messages (in case no cond is satisfied) message is ignored. but, in case of non-xml message exception is being thrown while cond is assessed.
Regards
Uri

Xpath expression in Left and Right operand for Receiver determination

Hi Experts,
Is it possible to use an Xpath expression in both the Left and Right operand inside the Receiver determination e.g.
(/Message/line/IDNumber = /Message/line/IDNo)
Any help will be appreciated.
Thank you,
Brendon

in standard receiver determination you can only specify value for the right operand.
that is one of the reasons you go for enhanced receiver determination
as mentioned in the sap help
If you are using the condition editor to define receiver determinations or interface determinations, you can only use the expression editor to create an expression for the left operand. You must specify a value for the right operand.

Condition for Receiver Determination

Similar Messages

Maybe you are looking for