Conditional Interface determination

Hi All,
I had a requirement for conditional interface determination...
Im using this blog
http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3414900)ID0462124050DB00225564311988524100End?blog=/pub/wlg/2973
In ID under interface determination...when I begin to add another interface..I do not get the condition tab??
Any idea y?..has ne one experienced such a strange scenario?

Hi Ravindra,
Even I face the same issue.
But I always save the interface determination after adding the second row, and then only I will be able to see the condition column for the two rows added.
Regards,
Supriya.

Similar Messages

Conditional Interface Determination with Flat Files

Hello,
I have one sender interface (dummy) which could either hold a flat file or an XML file. On receiver side there is one system with two receiver interfaces, one should be used for the XML structure and one for the flat structure.
My requirement is to have a conditional interface determination with an (exclusive) OR logic. Pseudo code:
The XML structure has "submission" as root node. So I use the condition (/submissioin) EX to determine whether it is an XML file and I check with not(/submission) EX to determine whether it is a flat file. However the condition does not work using a flat file ("Unable to find an inbound interface"). Could it be, that the conditional expression never is true in case a flat file arrives? How can I achieve this requirement?
What I additionally do with the flat file is just calling a Java Mapping that sets dynamic attributes for a file receiver, the flatfile itself is dumped on a file system without any addtional conversion logic.
Thank you for your advice.

How can I ingnore a message in case a condition applies? I am just aware of the fact that you can ignore messages in case NO condition applies.
Couldn't you simply reverse the logic and use "not equals"? Or perhaps you can use the EX operator to alter your conditions... here is more info on the EX (exists) operator
Re: ConditionEditor: Check if element is empty
What is best practice in this case? Should I use a "dummy receiver"? However if I use a dummy receiver I think I would receive a "interface determination not found" error. How would you do that?
I've never found the need to work with dummy receivers so I cannot comment there.

Enhanced and conditional interface determination, :

Experts ,
can you giv me some link/ examples of Conditional interface determination and Enhanced Interface determination.
Pls dont send me teh below link!
http://help.sap.com/saphelp_nw04s/helpdata/en/42/ed364cf8593eebe10000000a1553f7/frameset.htm
many Thanks
Arnab Mondal

HI,
U can refer this threads of same discussion:
Re: Condition In Receiver Determination Not Working
purpose of Enhanced Receiver Determination
Then refer this blogs:
Illustration of Enhanced Receiver Determination - SP16
SAP NetWeaver Process Integration: Enhanced Receiver Determination for Synchronous Scenarios

Regarding Conditional Interface Determination

Hi All,
I need small confirmation on behavior of conditional interface determination,
My source message is like below
<?xml version="1.0" encoding="UTF-8"?>
<PROS_CustInfo><Structure>
                                  <name>ABC</name>
                                   <data>100</data>
                             </Structure>
                             <Structure>
                                  <name>XYZ</name>
                                   <data>101</data>
                             </Structure>
</PROS_CustInfo>
I am having 2 Receiver RFC messages for same receiver.
If name=ABC then i need to send this data(ABC, 100) to first RFC by using 1st mapping else
if name=XYZ then i need to send that data(XYZ,101) to second RFC by using 2nd mapping.
But in my message name contains ABC and XYZ also. Now how conditional interface determination bahaves. Will it execute 1st mapping or 2nd mapping or both.
If you find any related post please share.
Thanks,
Madhusudhan

Hi Madhusudhana,
because of the problem, that only one condition can ever be true at runtime, you can avoid this by using count function. Because you can't build a Statement like count(xy) > 1 with ExpressionEditor of SAP PI, you have to use this expression with SAP PI:
/PROS_CustInfo[count(Structure[name='XYZ'])>=1] EX
This condition works on whole document.
Regards,
Alex
Edited by: Alexander Kirsch on Feb 16, 2010 4:43 PM
Edited by: Alexander Kirsch on Feb 16, 2010 4:45 PM

Receiver Determination and Interface Determination Condition conflict in ICO

Hi,
I found a strange issue today while configuring two receivers using the Receiver and Interface Determination conditions.
Sender - Proxy Service
Receiver1 - ReceiverA
Receiver2 - ReceiverB
Receiver Determination Condition : When Field1 = 100, message should flow to ReceiverA and ReceiverB
Interface Determination Condition (ReceiverA) : When Field1=100 and Field2=50 message should flow to a specific interface in ReceiverA
There is no Interface Determination condition for ReceiverB, for all messages having Field1=100, it should go to ReceiverB.
Test Scenarios:
1) Field1=100, Field2=50 : Message flows successfully to ReceiverA and ReceiverB
2) Field1=100, Field2=89 : Message fails to process from ECC itself throwing Interface Determination not found error. Ideally this is a positive scenario for ReceiverB and it should send the message to ReceiverB without any errors. But, this did not happen in this case
I tried the same by configuring the conditions completely in Receiver Determination itself without using the Interface Determination, it worked perfectly fine. But, just wanted to understand that if this is an expected behavior.

Hi Sherin,
As there are two receivers Receiver A and Receiver B.You need to create two bussiness components and two communcication channels for two receivers and one Reciver Determination, two Interface Determination,two Receiver Agreement.In Receiver Determination you need to keep the below and condition.
In the above screenshot the two receiver are Receiver B and Receiver C and Field 1 is Key_Value and Field2 is Emp_ID.
If the Key_Value=100 and Emp_ID =22 then the message should go to both the receivers B & C by keeping the following AND condition
If the Key_Value=100 and Emp_ID is not equal to 22 then the message should go only to Receiver B by keeping the following condition
You need not keep any condition in Interface Determination just create 2 Interface determination for two receivers.
Hope this helps you.
Thanks,
Durga.

Condition Based Interface Determination in ICO (AAE) - PI 7.1 EHP1

Hi Friends,
We have PI 7.1 EHP1 - SP 04.
In our scenario, we have 1 outbound interface and 2 inbound interface. Based on condition, it needs to select the first inbound interface or second inbound interface.
In the normal configuration, we are able to select. (By click + icon and add condition in the Receiver Interfaces in Interface Determination Step)
When we create configuration using ICO (Integrated Configuration), there is no option in "Receiver Interfaces" Tab to add two inbound interfaces with condition.
Could you please clarify how do we do this in ICO?
Kind regards,
Jegathees P.

IMHO, condition based interface determination is not possible in ICO.
Use Multiple inbound service interfaces... You can handle in design level .. ESR level.
Check the Abhishek's blog... This might be helpful.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/90dcc6f4-0829-2d10-b0b2-c892473f1571?quicklink=index&overridelayout=true
Note: Since in your case you need two receiver agreements, you cannot handle through ICO. The above link might be helpful to do multimapping without BPM.
Edited by: Baskar Gopal on Apr 26, 2011 9:53 AM

PI 7.1 Condition in interface-determination

Hi everybody,
I want to process interface determinations depending on payload. But when opening the condition editor in interface determination, the interface on which to apply the condition is not obtained!
What could be the reason?
Thanks
Regards Mario

Hey Mario .. that's a bug. Thanks for pointing this out. Never noticed till now
Regards,
Neetesh

XPATH to determine node name in condition of Interface determination

Hi,
does anybody out there know whether one can use a condition such as "name(/p1:Envelop/p1:Body/*)" to retrieve the name of the first element underneath the Body structure which is usually the payload. In the example below. I'd like to retrieve "ns0:BAPI_USER_GET_DETAIL" or just "BAPI_USER_GET_DETAIL" which I would like to than compare in my "=" condition.
<?xml version="1.0" encoding="iso-8859-1"?>
<sap:Envelope xmlns:sap="urn:sap-com:document:sap" version="1.0">
<sap:Header xmlns:rfcprop="urn:sap-com:document:sap:rfc:properties">
    <saptr:From xmlns:saptr="urn:sap-com:document:sap:transport">BC1</saptr:From>
    <saptr:To xmlns:saptr="urn:sap-com:document:sap:transport">BC2</saptr:To>
</sap:Header>
<sap:Body>
     <ns0:BAPI_USER_GET_DETAIL xmlns:ns0="urn:sap-com:document:sap:rfc:functions">
      <CACHE_RESULTS/>
      <USERNAME>bauerd</USERNAME>
     </ns0:BAPI_USER_GET_DETAIL>
</sap:Body>
</sap:Envelope>
I have a client that once to migrate his SAP BC interfaces to PI without having to change the sending application which is a CICS mainframe application. The mainframe application invokes various BAPI's by just passing in a different payload into the above envelope. The payload is always the request structure for the BAPI. The message is send synchronously to SAP BC which than calls the BAPI and returns the response to the caller, again in form of the above envelope and as payload the BAPI response structure.
To convert this to PI I have to be able to initiate different interface mappings depending on what BAPI is requested. This is pretty straight forward as there are no special mapping transformation taking place in SAP BC for both the BAPI request and response. However I need to determine what interface mapping to call depending on BAPI requested by the CICS application.
As said the customer does not want to change the sending application. The only part we are allowed to change is the URL which changes from SAP BC to the SAP PI Plain HTTP sender adapter. The post will always use the same outbound message interface. Therefore I can't use SAP PI's standard receiver determination. Using this adapter I will also be able to get access to the whole message envelope as outlined above.
I already got all of this working nicely with the exception that I can't determine what BAPI is requested and therefore what interface mapping I have to trigger in my interface determination.
Has anybody used a condition as above and if so how should it look like in the condition editor. The one outlined above does not seem to work. However it is also not failing in PI.
Also I don't want to change my approach for doing this. However if it is not possible to retrieve the node name using the xpath statement (as outlined above) in the condtion editor than I will have to look for a different approach to resolve this problem. Any suggestions would than be more than welcome.
Many thanks in advance.
Dieter

If the structure is not too big, you can use:
//ns0:BAPI_USER_GET_DETAIL EX
otherwise take the full path:
/p1:Envelop/p1:Body/ns0:BAPI_USER_GET_DETAIL EX
The namespaces have to be declared.
Regards
Stefan

Condition based Interface determination

Hi ,
Environment : PI 7.1.
Scenario : File to Proxy.
In this scenario , We have a single file interface which reads a file and routes the data to two different inbound interfaces.
Steps followed to do this -
>>Defined two inbound interfaces interface1 & interface2.
>>Both interfaces are pointed to same ECC system.
>>Read the file using a single sender file communication channel.
>>Define receiver ECC in the receiver determination.
>> Define interface determination based on a value of a field in the file structure(source structure). Used XPATH to define this content based routing and selected operation mapping specific to the interface.
1 sender agreement
1 receiver determination ( not using enhaced receiver determination because we have only one receiver)
1 interface determination which has two receiving interfaces based on XPATH condition ( maintain order runtime is checked)
2 Receiver agreements.
2 Communication channels.
For example if you have 10 lines in a file , out of which if 5 lines has a value related to interface 1 & 5 lines has a value related to interface 2. It should push the data into two different proxies as configured.
We are facing a problem in this scenario -
There is no consistency in the logic. Some times it runs interface 1 & some time it executes interface 2.
based on condition 1 it routes the data to interface 1 successfully but the structure is not getting created for interface 2 so it is giving an error stating the interface 2 structure is not available.
In SXMB_MONI the branching steps show two subnodes but if you see the log it shows that in subnode 1 the sender is sender interface & the receiver is interface 1 based on the filter condition. If you see the log for subnode 2 then it shows the sender is sender & the receiver as interface 2 below that it shows another entry which shows the reciver interface is interface2.
Please evaluate and let us know if the approach we are following works or not. If there is any limitations please let us know how to achive this.
Regards,
Reddy

Hi,
Your design is correct but here you missed one point. Here the message is send either to receiver1 or receiver2 depending on the condition but not both. As this does not result in multiple messages with the same payload because only one condition can ever be true at runtime. For more details see the below link
http://help.sap.com/saphelp_nw04/helpdata/en/46/8015de950e6be3e10000000a155369/frameset.htm
If you want to create multiple message then you need do 1:n mapping :
http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3417700)ID2056393550DB10021342992851308291End?blog=/pub/wlg/2927
Shweta.

Interface determination condition

Hi Experts,
I am working on File to IDoc scenario, where I want to send IDocu2019s based on source data, in flat file if order number exists then I have to send MATMAS idoc , if order number does not exists then I want send DEBMAS.
I developed 2 mapping programs and checking condition in Interface determination to check order number exists or not.
i wrote below conditions in Interface determination and not working for multiple Orders
MT_Invoice /Order/OrderNum EX u2013 to check order number exists or not.
MT_Invoice /Order[not(OrderNum)] EXu2014to check order number not exists
My Source Structure after file content conversion looks like below
<Order> 1..unbounded
    <CustomerID>
    <MaterialID>
    <OrderNum>
</Order>
Regards,
JAM

Hello,
The Interface determination condition will not filter the payload data. It can only determination whether a particular condition is true or false.
If any valid condition occurs, complete payload will be passed to the respective Interface and mapping will be executed accordingly.
Currently in your case I guess both conditions are getting satisfied for multiple records in payload.
I think you need to implement the filtering logic in message mapping using the concept of multi- mapping.
Refer blog: /people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it146s-possible
The mapping will contain 2 target structures with occurance 1...unbounded i.e. Matmas and Debmas for your scenario.
You need to apply filter logic on header nodes in the mapping.
Or you need to process single records in the payload.
-Rahul

Wildcard in interface determination condition

Hi Folks,
I tried the following condition in setting up the condition in Interface Determination, but it is not working:
Condition: /Document/Type = addLoad*
The source field has this sample [email protected]
I only need the "addLoad" and the other data that comes after the "@" changes in every transaction coming in to XI.
Your advise is very much appreciated. Thanks!
Regards,
Lex

Hi,
Try using Contains Pattern operator instead of '='.
Condition: /Document/Type ~(contains pattern operator) addLoad*
refer the below link
http://help.sap.com/saphelp_nw04/helpdata/en/42/ea20e737f33ee9e10000000a1553f7/frameset.htm

Conditional step in interface determination

Hi All,
The Scenario is a proxy to file server..
we are sending datas to different service based on File Content Conversion..
Depending on the data on a certain field the records are delivered to different location.adapter we use is a file adapter.
For this we need to give the conditional step in interface determination..
the sender is a message system and the receiver is a business service.
The issue here is when i try to give the condition in interface determination the error below appears.
"<b>Message interface does not exist in any software components installed on this business system</b>"
due to this we are not able to get the structure of the specified message type in the condition editor...
What can be done here to give the conditions in the condition step?

Hey
The error occurs if the GUID of the software component at the SLD is different to the one at the repository. Please compare the GUID at the SLD -> Administration -> Content Maintenance -> Dropdown "Component Version" -> Dropdown "Software Component Version". At the Integration Repository you select the Software Component Version at at the tab "Keys" you find the related GUID.
The error occured because the Software component has been created manually at the system. The repository content came from another system via import with own SLD (and because of that with another GUID for the software component).
source:https://forums.sdn.sap.com/click.jspa?searchID=3574640&messageID=945384
Thanx
Ahmad

Receiver determination(or Interface determination) and conditional routing

I have a flat file to flat file scenario. Based on the input file content, I want to route data to the receiver.
My source flat file contains several IDOC details. Assume two fields FIELD1 and FIELD2 in different segments of the IDOC. My requirement is if FIELD1 of an IDOC = "US" and FIELD2 of the same IDOC = "CA", then that IDOC's details needs to be passed to the receiver.
I have implemented the above condition at interface determination.
But the problem is:
Assume there are 3 idocs in the input file.
FIELD1 of IDOC[1] = 'US' and FIELD2 of IDOC[1] = 'GL'
FIELD1 of IDOC[2] = 'UK' and FIELD2 of IDOC[2] = 'EN'
FIELD1 of IDOC[3] = 'BR' and FIELD2 of IDOC[3] = 'CA' .
Now none of the IDOCs in the input satisfy my requirement and hence the message mapping should not be called at all. But in my case its failing because FIELD1 of IDOC[1] and FIELD2 of IDOC[3] together are satisfying the condition and hence the message mapping is called.
But I need to check this condition IDOCwise. Both the conditions to be satisfies in the same IDOC.
I am thinking that contexts are not being taken care.. It just see the whole file together and not IDOCwise.
Can someone help me on the same. Please let me know if more information is required.
Thanks,
Shobha

>
Shobha HB wrote:
> I have a flat file to flat file scenario. Based on the input file content, I want to route data to the receiver.
>
> My source flat file contains several IDOC details. Assume two fields FIELD1 and FIELD2 in different segments of the IDOC. My requirement is if FIELD1 of an IDOC = "US" and FIELD2 of the same IDOC = "CA", then that IDOC's details needs to be passed to the receiver.
>
> I have implemented the above condition at interface determination.
>
> But the problem is:
> Assume there are 3 idocs in the input file.
> FIELD1 of IDOC[1] = 'US' and FIELD2 of IDOC[1] = 'GL'
> FIELD1 of IDOC[2] = 'UK' and FIELD2 of IDOC[2] = 'EN'
> FIELD1 of IDOC[3] = 'BR' and FIELD2 of IDOC[3] = 'CA' .
>
> Now none of the IDOCs in the input satisfy my requirement and hence the message mapping should not be called at all. But in my case its failing because FIELD1 of IDOC[1] and FIELD2 of IDOC[3] together are satisfying the condition and hence the message mapping is called.
>
> But I need to check this condition IDOCwise. Both the conditions to be satisfies in the same IDOC.
>
> I am thinking that contexts are not being taken care.. It just see the whole file together and not IDOCwise.
>
> Can someone help me on the same. Please let me know if more information is required.
>
> Thanks,
> Shobha
The ideal solution to your scenario is to redesign the interface as below;
1. Receive the file.
2. Do a 1: N mapping (this should split your message into multiple Messages)
3. On this message you can do the required check. Now only the required field for the particular IDoc will be part of the check and it will not mix with other Idocs.
Will this do? Else please provide more details

IDoc to file- How to include conditions in Interface determinations

Hi,
In interface Determination i am trying to add the conditions based on IDoc structure field value. But when i clicked on Condition editor i don't find Idoc stucture in editor XPath.
Please suggest me how i can add the condtions in the Interface determination in IDoc to file Senario.
Thanks in Advance...
Regards
Sreeni

Hi Sudhir,
I have tried as you mentioned, but still its not working. Below i am providing my inbound payload.
Could please let me know how i have to mention in condition editor to refer the IDoc field
ZGHIER01/IDOC/Z1GLHIERH/SETNAME
<?xml version="1.0" encoding="UTF-8" ?>
- <ZGHIER01>
- <IDOC BEGIN="1">
   + <EDI_DC40 SEGMENT="1">
    - <Z1GLHIERH SEGMENT="1">
       <CATEGORY>GLHIER</CATEGORY>
       <SETNAME>PEGPL_AG</SETNAME>
     + <Z1GLHIERD SEGMENT="1">
     + <Z1GLHIERI SEGMENT="1">
     + <Z1GLHIERI SEGMENT="1">
     + <Z1GLHIERI SEGMENT="1">
     + <Z1GLHIERI SEGMENT="1">
   </Z1GLHIERH>
</IDOC>
</ZGHIER01>
Thanks & Regards
Sreeni
Edited by: Sreenivasulu Reddy jonnavarapu on Dec 12, 2008 10:39 PM

Condition in Interface Determination giving problem - URGENT!

Hello experts,
In my scenario I have one idoc posted from the SAP R/3 and I need to write max of 3 files in the same receiver file system based on some condition i.e. based on the value of some field in the incoming idoc.
What I have done is in my interface determination, I have given that condition for all the 3 inbound interface. that is in the condition field in interface determination, for each inbound interface I chose that perticular field in idoc and gave the condition for which that interface should run.
Now when I am pusing an idoc, if that idoc contains only one condition than my interface is working fine by creating only that file. I have checked this for all 3 files by sending 3 different conditions in 3 idocs. It creates 3 different files for 3 idocs.
But if I send all 3 conditions in one idoc (since idocs can have multiple segments - in few segments i am giving one condition and in few others the 2nd conditon and in the rest the 3rd condition), I expect all 3 files to be created in my file system with data fulfilluing only that perticular condition. but this is not happening. In interface determination only one of the 3 is getting executed. Rest 2 is ignored and i cannot trace it anywhere (RWB, SXI_MONITOR etc)
I have tried all possible combinations but this is not working if i send in 1 single idoc?
Please help me in solveing this as this is a production issue and they cannot send 3 diffent idoc for 3 conditions. Where am i going wrong?
Waiting for your responses.
Thanks,
Yash

Hi Jakub,
My scenario is one idoc say IDOC 1 and 3 files says FILE1, FILE2 and FILE3. Now the target message type for these three files are MT_FILE1, MT_FILE2 and MT_FILE3 (3 different message types).
The only catch point here is i have 2 different interface for creating FILE3 (same message type but different mapping, interface etc). Each interface is based on a condition.
Now when I send one doc which includes condition for only FILE1 and FILE2, it creates 2 file.
If I have condition of only FILE3 (one condition of FILE 3 as FILE3 has 2 conditions) and FILE2, it creates both files.
If I have both condition for FILE3 and FILE2, it creates FILE3 with only one condition and FILE2.
If i have condition for FILE1, FILE2 and both conditions for FILE3, it creates FILE1 and FILE2 both no FILE3 at all.
I guess the problem might be that I have same message type for both conditions for FILE3 but I m not sure. Let me try by creating seperate message type for both and see. But is there any other problem?
Yash

Conditional Interface determination

Similar Messages

Maybe you are looking for