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.

Similar Messages

Receiver Determination and Interface Determination

Hi,
Please, can anyone explain what is the concept of 'Receiver determination' and 'Interface Determination'?
Thanks,
Harikumar. S

Hi,
>>>>Receiver determination
its about finding the receiver system for particular source system and outbound interface.
Suppose,you want to send data from file->XI->SAP and CRM based on some condition
in this scenario you need to determine whether to send file data to SAP or CRM system,this decision you will do in Receiver determination
in Receiver determination screen you need to provide the following details
1.Source system(ex: File system)
2.Outbound Interface(File Message Interface)
3.condition and receiving system(ex:if some x field value in source payload is 1 go to SAP elseif '0' go to CRM system)
>>>>>>Interface Determination
suppose in above scenario you determined the receiver i.e SAP,you will have number of IDOCs (Inbound Interfaces)in SAP.
so to which IDOC you will send file data?This decision you will make in Interface determination(we can it as Inbound Interface determination).if you find the IDOC is CREMAS then how will transfer file structure data to IDOC structure? answer is Message Mapping
From all the above decisions you need to provide following details in Interface determination screen
1.Source System
2.Outbound Interface
3.Receiver System
4.Inbound Interface(IDOC type)
5.Message Mapping(i.e file to IDOC)
Even in Interface determination you can specify the condition to select Inbound Interfaces(ex.IDOCs)
if you have any doubts please lets know.
Cheers,
Jag

Extended Receiver Determinatipon and Interface Determination?

Hi,
Where exactly (In which business cases) we can implement or required Extended Receiver Determination and Interface Determination?
Thanks,
Naidu.

Hi,
There are only two modes standard and Extended, Enhanced receiver determinatrion is Extended receiver determination only.
Enhanced(Extended) receiver determination -->
Whenever list of receivers is determined dynamically at runtime, using a message mapping then it is called enhanced.
Enhanced Interface Determination--> It is when you want the target interfaces to be defined dynamically based on the multimapping, that is called enhanced interface determination.
Refre SAP help for more detail
http://help.sap.com/saphelp_nw04s/helpdata/en/42/ed364cf8593eebe10000000a1553f7/frameset.htm
Thanks!
Edited by: Sudhir Tiwari on Dec 5, 2008 6:34 AM

Need of creating receiver determination and interface determination

what is the need of creating interface determination where as providing all the details in Receiver determination?

Hi,
The loose coupling between the Interface mapping and receiver determination have provided the compatibility for reusability.
The Interface determination maintained and just linked to receiver determination so you could have multiple receiver determinations with common interface determination or vice-versa.
If you provide all the information in receiver determination then, it would be very dfficult to have the various mappins for multiple receivers maintained in receiver determination.
Interface determination is applied at runtime to all messages to be processed. Thus from security point of view of transaction of data. its preferable.
Thanks
Swarup

Receiver Agreement and Interface determination

Hi
I have an input file that generates two output files. The two output files go to the same interface. One output file will have header and the other will have details. I want to kow how many receiver determination, interface determination, sender agreement and receiver agreements we need to create
Regards

Hi Ajith,
As perception, I understand that you would like to like to split the input file into two as Header and Details. For this requirement, you should need Integration Directory (Configuration) as below:
1. Need to Two Receiver agreements.
2. One Receiver determination.
3. One sender agreement.
4. One Interface determination ( Type: Enhanced)
Thanks,

Receiver determination Vs Interface determination

Hi Experts,
What is the difference between Receiver determination and Interface determination?
In both the case we specify sender -> outbound interface -> Receiver Service -> Interface mapping
Can't we use only interface mapping? Why SAP is providing these two determinations?
Thanks
Gopal

Hi,
>In both the case we specify sender -> outbound interface -> Receiver Service - Interface mapping
In receiver determination you only mention the Sender Service, Sender Interface and Reciever Service. You do not mention the Inbound Interafce and interface mapping. You do this in the Interface Determination.
The split between Receiver Determination and Interfacedetermiantion is so that you can add send the same message to Multiple Receivers and then fior each of the receivers , if needed you can add multiple Inbound Interafces / mappings!!
And you can add multiple conditions as well!! makes sense to me!
regards
Bhavesh

Output determination and Printer determination for both PO and GR

Dear all,
Can anyone please help me in congiguring the output determination and printer determination for both PO and GR. please give me detailed configuration including the paths as i am stuck with the configuration.
Thanks & Warm Regards
Somashekar Anand

hi Somashekar
follow he steps
Output of Purchase Order
1. Condition Table
SPRO > Material Management> Purchasing -> Message -> Output Control->Condition Tables->Define Condition Table for Purchase Order
Select:
Purchasing Doc. Type,
Purch. Organization,
Vendor
2. Access Sequences
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Access Sequences->Define Condition Table for Purchase Order
3. Message Type
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Types->Define Message Type for Purchase Order
*4. Message Determination Schemas*
4.1. Message Determination Schemas
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Maintain Message Determination Schema
4.2. Assign Schema to Purchase Order
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Assign Schema to Purchase Order
5. Partner Roles per Message Type
SPRO -> Material Management-> Purchasing -> Message -> Output Control-> Partner Roles per Message Type ->Define Partner Role for Purchase Order
6. Condition Record
Navigation Path: SAP Menu-> Logistics -> Material Management -> Purchasing-> Master data->Messages-> Purchase Order-> MN04-> Create
Now you create PO (ME21N) and save it. Go to ME22N and print the PO by giving output type.
Output of GR
After setting table, access sequence and output type for GR,run MB02 transaction, enter material document number. Double click one line item and select messages. Separate screen will be opened to configure outputs. Give the required fields and save the document. Now Run MB90, you can take printout. Output Type: WE03 or WE01 or WE02
Reward points if helpful
Thanks and regards
Ravikant Dewangan

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

Receiver and Interface determination

Hi,
My senario is File to IDOC and mail.
The condition here is the count of Idoc generated has to be sent as a mail and the mail has to be sent only after the IDoc has been generated successfully.
So i am using two receiver services one is for IDOC and other is for mail and in one receiver determination I am refering TWO reciver Service without any condition.
now i have to use only one interface determination to maintain the order at runtime. so that the interface mapping for mail will be triggered only after the Idoc interfacemapping is successfull.
but in receiver agreement i am not able to refer the Receiver channel for Mail. because the receiver service is still poiting to the Idoc Serveice.
Plz advice.

Hi!
I think the above requirement will also work by using a simple BPM. just try with below steps.
Steps in BPM::
1. Receive step to receive File from a third party by using File Sender CC.
2. SEND ASYNCH step to send IDOC generated Structure data.
3. Before going to next step please find any constant value which will be coming into IDOC from file that
    means for example if your IDOC cotnains any field like ORDER_Generated_By or
    GENERATED_BY:: AMAR name is same in all the data that is coming into IDOC remember that Field
    Name name and insert it in the swtich statement condition editor.
4. Now Insert Switch Condition with 2 branches A & B,
     a) Branch A contains control statement and this branch executes only if the condition statisfies with
        If that IDOC Field lets say name XXXX is equal to constant value AMAR then raise/throws an alert
        mail by uising Control Step.
    b) In Branch B also you ill be including Control Step but this control Step will says that MAIL
        INDICATION No IDOC is generated by using another control step.
5) Remaining all other configurations like 2 receiver agreements and every thing aare same.
6) But you need to confgure ALert configuration settings okay.
You can also achive this by using without BPM.::
In ID part:: you need to enter a condition in Receiver Determination with two receiver business systems and that condition will be once the IDOC field like XXXXX(generated_by is equal to some constant like AMAR ) then it needs to active the Mail Business System.
but this would be little but confusion and but u can achive the above requirement by using simple BPM.
Note:: Only diadvantage will be some performance issue will come if goes through BPM but it works
          very 100 systamatic way because you can review where exactly your Scenario strucks and also
          u can check whether your IDOC generated or not whether mail sent or not in the BPM WORK
           FLOW in the BUSINESS PROCESS ENGINE.
Regards::
Amar Srinivas Eli

Receiver and Interface Determination, Sender and Receiver Agreement

Hi Experts,
Could you please tell me, what Receiver Determination, Interface Determination, Sender Agreement and Receiver Agreement we have to use for the below blog.
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1403 [original link is broken] [original link is broken] [original link is broken]
Regards
Sara

Hi Sara,
WS->BP
Receiver Determination: Sender IF, Sender NS, Sender BS determine the BP
Interface Determination: Sender IF, Sender NS, Sender BS determine your start msg IF (abstr IF) and IF mapping
Sender Agreement: SOAP sender channel for that Sender IF, Sender NS, Sender BS
Receiver Agreement: not reqired
BP->DB
Receiver Determination: BP IF (abstr), BP IF NS, BP determine the 3rd party BS (DB)
Interface Determination: BP IF (abstr), BP IF NS, BP determine Inbound-IF and IF mapping
Sender Agreement: not reqired
Receiver Agreement: JDBC receiver channel for that Inbound IF, NS and 3rd party BS
BP->File
Receiver Determination: BP IF (abstr), BP IF NS, BP determine the 3rd party BS (File)
Interface Determination: BP IF (abstr), BP IF NS, BP determine Inbound-IF and IF mapping
Sender Agreement: not required
Receiver Agreement: File receiver channel for that Inbound IF, NS and 3rd party BS
Regards,
Udo

Multiple Interface Determination

Hello everybody,
I am working on the following szenarion:
- one sender and sender interface (incoming IDOC).
- one receiver with two different receiver interfaces (outgoing BAPIs). For one of these interfaces there exit two different interface and message mappings. So, 1 incoming interface => 3 outgoing with 2 different interfaces
So in the interface determination I want to rout the message by use of XPath expression to use one of the two interface (no problem at all), but also to choose one of two interface mappings for the same interface. If I try this by creating three lines in the interface determination and using different XPaths, the last entered interface always is deleted automatically.
Thanks for your help.

Hi,
To do what you want you may have to use both Receiver Determination and Interface Determination. XPath expressions can be used in both places.
In Receiver Determination, you will have 2 receiver services. Then, in one of the receiver services, you will have 2 Interface Determinations. So, you will end up with something like the following:
Receiver service1: interface1
Receiver service2: interface1, interface2
Regards,
Bill

Interface Determination causing issue in Receiver Determination

Hi
I am having an issue with interface and receiver determination as follows:
- Inbound message may be sent to two receivers.
- Message gets sent to first receiver, fails during interface determination. There are multiple inbound interfaces found based on a set of XPATH conditions. This creates an error 'Inbound interface found more than once for outbound interface '. That is itself is not the issue.
- Issue is that the message is stopped from going to the other receiver even if there are no issues in the interface determination for that receiver.
Is there a way to resolve this? Appreciate any help. Thx, Duncan

Again, thanks for the replies.
MONI for RD
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Start without given receiver</Trace>
<Trace level="2" type="T">Classic Receiver Determination via Rules.</Trace>
<Trace level="2" type="T">Check conditions for rule line no. 1</Trace>
<Trace level="3" type="T">...create rule engine</Trace>
<Trace level="3" type="T">...call rule engine for Condition %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice")% EX and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% CE COSTCENTRE or %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice")% EX and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% CE INTERPLANT or %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice")% EX and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% CE INTERPLANT_ONESTEP or %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice")% EX and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% CE INTRAPLANT or %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice")% EX and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% CE INTRAPLANT_ONESTEP or %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:receivingAdvice")% EX or %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:inventoryActivityOrInventoryStatus")% EX</Trace>
<Trace level="2" type="T">......extracting (new) for Extractor: XP /p2:despatchAdvice</Trace>
<Trace level="2" type="T">......extracting values found: 0</Trace>
<Trace level="2" type="T">......extracting (new) for Extractor: XP /p2:receivingAdvice</Trace>
<Trace level="2" type="T">......extracting values found: 1</Trace>
<Trace level="2" type="T">...valid Receiver with Condition: - GLR430</Trace>
<Trace level="2" type="T">Check conditions for rule line no. 2</Trace>
<Trace level="3" type="T">...call rule engine for Condition %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice")% EX and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% NE COSTCENTRE and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% NE INTERPLANT and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% NE INTERPLANT_ONESTEP and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% NE INTRAPLANT and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% NE INTRAPLANT_ONESTEP</Trace>
<Trace level="2" type="T">...invalid Receiver: P_3PL_XML_ME_ODTH - despatchAdviceToE1EDT20</Trace>
<Trace level="2" type="T">Check conditions for rule line no. 3</Trace>
<Trace level="2" type="T">...valid Receiver w/o Condition: P_3PL_XML_ME_ODTH - S_HTTP</Trace>
<Trace level="2" type="T">No Receiver found behaviour: 0</Trace>
<Trace level="2" type="T">Number of Receivers:2</Trace>
</Trace>
</Trace>
</Trace>
Here, you see that both receivers are found.
MONI for ID
<Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION" />
- 
<Trace level="1" type="Timestamp">2007-02-26T20:06:49Z CET Start of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_ID_PLSRV</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
- <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) GLR430 WMMBXY.WMMBID01</Trace>
<Trace level="3" type="T">...create rule engine</Trace>
<Trace level="3" type="T">...call rule engine for Condition%CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p1:inventoryActivityOrInventoryStatus/inventoryDocumentType")% CE INVENTORY_STATUS</Trace>
<Trace level="2" type="T">......extracting (new) for Extractor: XP /p1:inventoryActivityOrInventoryStatus/inventoryDocumentType</Trace>
<Trace level="2" type="T">......extracting values found: 0</Trace>
<Trace level="2" type="T">...invalid InbIf: WMMBXY.WMMBID01</Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) GLR430 WMMBXY.WMMBID01</Trace>
<Trace level="3" type="T">...call rule engine for Condition%CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p1:inventoryActivityOrInventoryStatus/inventoryDocumentType")% CE INVENTORY_ACTIVITY</Trace>
<Trace level="2" type="T">......extracting (new) for Extractor: XP /p1:inventoryActivityOrInventoryStatus/inventoryDocumentType</Trace>
<Trace level="2" type="T">......extracting values found: 0</Trace>
<Trace level="2" type="T">...invalid InbIf: WMMBXY.WMMBID01</Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) GLR430 WMMBXY.WMMBID01</Trace>
<Trace level="3" type="T">...call rule engine for Condition%CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:receivingAdvice/receivingAdviceItemContainmentLineItem/purchaseOrder/documentReference/uniqueCreatorIdentification")% EX</Trace>
<Trace level="2" type="T">......extracting (new) for Extractor: XP /p2:receivingAdvice/receivingAdviceItemContainmentLineItem/purchaseOrder/documentReference/uniqueCreatorIdentification</Trace>
<Trace level="2" type="T">......extracting values found: 2</Trace>
<Trace level="2" type="T">...valid InbIf with Condition: WMMBXY.WMMBID01</Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) GLR430 WMMBXY.WMMBID01</Trace>
<Trace level="3" type="T">...call rule engine for Condition%CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:receivingAdvice/carrier/additionalPartyIdentification/additionalPartyIdentificationValue")% CE SHUTTLE</Trace>
<Trace level="2" type="T">......extracting (new) for Extractor: XP /p2:receivingAdvice/carrier/additionalPartyIdentification/additionalPartyIdentificationValue</Trace>
<Trace level="2" type="T">......extracting values found: 1</Trace>
<Trace level="2" type="T">...valid InbIf with Condition: WMMBXY.WMMBID01</Trace>
</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 002</Trace>
<Trace level="3" type="T">Message version 002</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="3" type="System_Error">Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="3" type="T">Persisting message Status = 014</Trace>
<Trace level="3" type="T">Message version 003</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</SAP:Trace>
Here, you see that the ID runs for the first receiver. It hits an error because two conditions on the ID for the first receiver are satisfied. However, it then stops rather than allow the processing for the other receiver to continue.
Any ideas? Thx, Duncan

Enhanced Interface Determination in PI 7.1

Hi All,
My scenerio will work as follows
The changes in the process order will triggered by the client system .I will get the already converted XML file.I have used the file adapter in the sender side to pick the file.At the receiver side I am using the 3 custom BAPIs.I have used 3 message interface instead of multi-mapping as the inbound interfaces.
The Logic is like that:
If the Process order status is = 1 then call BAPI 1,if it 2 then call BAPI 2 & call BAPI 3.
Please tell me the following
1.Is there Enhanced Interface Detrmination option available in PI 7.1?If so then can I mention or call 2 BAPIs in one condition over there?Do I need to write ABAP condition?
2.Is Enhanced interface Determination possible when I have used 3 inbound interfaces instead of multi-mapping?
3.From my point of view I need the following in my scenerio
- 3 message mappings(Graphical Mappings),
- 3 interface mappings,
- 1 sender agreement,
- 1 receiver determination,
-1 interface determination(with 2 conditions in it),
-3 receiver agreements.
Am I right?
4.How many sender and receiver agreements do I need?
5.Do I need to go for Enhanced receiver determination?
Thanks in advance.

the same status node in the source file on which I will impose check will call the selective inbound interface based on the
status node.Is it?If so,then do I need to mention anything other than the check condition in XPATH e.g.do I need to mention any
mapping program or inbound interface (though I dont thing so but I am still confused) ?
Yes, apart from specifying the condition in the Condition Editor you also should mention the corresponding Inbound Service Interface and Interface Mapping (if any).
Condition will only cause the execution of that particular line and wont automatically call the mapping/ interface (unless these are specified in the Interface Determination).
Is XPATH the alternative option in condition editor which can be skipped though I would surely like to go through it as
much as possible?
XPATH is the easiest option to specify a condition....other option includes the use of a Context Object.
So as of now think that you cannot skip XPATH (for this particular requirement).
Once you become an expert in using a XPATH (which you can in a days period) you can try out for Context Objects.
Regarding Test Case:
There is no standard template for this.....i would suggest check with peers in your company.....many a times companies have their own templates for test cases alongwith the possible cases....then referring to those test cases you can build the cases for your scenario. Avoid a direct copy of the test cases.....many wont be relevant for your case.
Regards,
Abhishek.

Problem in Interface determination for multiple MM

Hi experts,
i designed an IDOC to Jdbc scenario.
The particular thing is that I have TWO message mappings to apply for the same source and same target.
Hence, I have in my directory two scenarios with :
- same Reveicer Determination
- same Interface Determination
- differents Receiver agreements (i have two Communication Channels)
In my interface determination, I have configured a standard Interface determination with my two interface mappings to apply.
My problem is when I send an idoc, the result should be for my two interfaces differents payloads to inject to the database, but I get the same payload for both interfaces with the same namespace...it looks like it only use one Interface mapping instead of both...
It is driving me crazy...
Any help would be greatly appreciated
Kind regards,
Jamal

Hi,
i have the same receiver.
I do have two interface mappings in my interface determination. The problem is that it uses the same for both interface.
If I use enhanced ID, i can only specify one Interface mapping.
What I want :
- sender A - Message mapping 1 - receiver A
- and also sender A - Message mapping 2 - receiver A
when the idoc is sent.
what I have right now (though my configuration seems to be right) :
- sender A - Message mapping 1 - receiver A
- and also sender A - Message mapping 1- receiver A
Thanks a lots,
Jamal

Meaning of multiple interface determination

I'm still starting with XI and some doubts are appearing while I get deeper into it. My doubt here is what's the sense in configuring more than one inbound interface in interface determination.
As you specificy sender and receiver services, and interface, how does it makes sense? I mean, the specified interface is forcing implicitily the inbound interface, so it doesn't make sense to define two different inbound interfaces.
Unless of course you choose the same inbound interface more than once, with different interface mappings, but then, which one would be chosen for an actual communication?
Thanks in advance.
(Environment XI 7.0)

I don't think you answered my question. I'm talking about configuration of two inbound interfaces in a single interface determination object.
In this image you can see one of my interface determinations:
[picture|http://img26.imageshack.us/my.php?image=interfacedet1ju7.jpg]
Sender service and sender interface are set and can't be modified, just as receiver service. This configuration is making mandatory that in the "configured interfaces" section, the inbound interface is BAPI_MATERIAL_GETALL, because that is the output message type of MI_OUT_S_0422_BAPI_MATERIAL_GETALL.
So what's the sense of adding a new line in the "configured interfaces" section?
It would only make sense using BAPI_MATERIAL_GETALL as inbound interface (is mandatory as I wrote before), and specify a different interface mapping. However, in that case, which one of those two would be used in runtime?
(Please answer directly to my questions and not just a general paragrafh. Otherwise I don't think we will get a successful communication. If what I write can't be understood please ask me.)
Thanks.

Receiver Determination and Interface Determination Condition conflict in ICO

Similar Messages

Maybe you are looking for