ACK for receiver determination with 2 interface determination

Hi Forum,
I have a XI scenario, with a BPM, where i have a Send step,
this send step corrsponds to a receiver determination in Configuration, and this receiver determination has 2 interface determination,
because the send step is like,
BPM to Receiver1, through sender message interface MI_Sender1, but there are 2 different receiver message interface namely MI_receiver1, and MI_receiver2,
.......hence 2 interface determination and 2 interface mappings accordingly,
and now when in BPM, i choose "transport acknowledgement" for this send step, my BPM stucks while waiting for the acknowledgement, but...in MONI, i am receivng both the acknowledgement, but in PE, workflow descrition, it waits for acknowledgement and finally fails,
what's the reason,

check the workitems of both sender/receiver (ack) in moni (problem might be in BPM config).

Similar Messages

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

Extended receiver and enhanced interface determination

Hi,
Can somebody list me the business cases when we use the extended receiver and enhanced interface determination.In which scenarios we have to use them?
Where we can use these features and whom they can replace?
Regards,
Anoop

Hi Anoop
have alook at thses URl's also
http://help.sap.com/saphelp_nw04/helpdata/en/43/01322a7af25285e10000000a1553f7/frameset.htm
:Dynamic file and variable substitution
Similarly Extended Receiver determination is used to determine the receiver at runtime.
Refer my reply:Re: Condition In Receiver Determination Not Working
enhancement in ID
Enhanced Receiver Determination:
You use an enhanced receiver determination to have a mapping program determine the receivers of the message dynamically at runtime. Instead of creating the receivers in the receiver determination manually, you assign a mapping to the receiver determination and this returns a list of receivers at runtime.
http://help.sap.com/saphelp_nw04/helpdata/en/43/a5f2066340332de10000000a11466f/content.htm
Enhanced (Mapping-Based) Interface Determination
In an enhanced interface determination you do not enter the inbound interfaces manually, but instead first select a multi-mapping. You get the inbound interfaces from the target interfaces of the multi-mapping. The inbound interfaces are determined at runtime during the mapping step.
You typically use an enhanced interface determination if the source message has an element with occurrence 0 ... unbounded (for multiple items of a data record) and you want multiple messages (for the individual items) to be generated at runtime.
http://help.sap.com/saphelp_nw04/helpdata/en/42/ed364cf8593eebe10000000a1553f7/frameset.htm
enhanced interface determination
/people/robin.schroeder/blog/2006/11/15/using-dynamic-receiver-determination-with-sync-interface
/people/venkataramanan.parameswaran/blog/2006/03/17/illustration-of-enhanced-receiver-determination--sp16
List of receivers can be dyamically determined and assigned at runtime using enhanced receiver determination .
http://help.sap.com/saphelp_nw04/helpdata/en/43/a5f2066340332de10000000a11466f/content.htm
Thanks
Pls reward if useful

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.

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

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

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

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 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,

Several partner recipients for Automatic action with partner determination

Hi everybody
I did define one action inside my Lead action profile to inform several employees about the Lead details.
I did customize the action with:
-Processing time: 1 Processing Using selection report
-Processing times not permited: No restriction
-Schedulle automatically
-Changeable in dialog
-Executable in dialog
PARTNER DEPENDENT:Partner Function Z3
action Mergin:Set Highest Number of Processed Actions
In the tab Action Merging i did choose One unprocessed action for each partner
I would like to send the same mail to several recipients,(each partner with the same partner function in the "Parties involved" tab).
My problem is that although there are as many actions generated as partner with Z· partner fuction, the mail is sended always to the main partner. (the first one with z3 partner function).
Can anyone help me with this?
Thanks.

Thank you very much for those quick answers.
I did try yet this customizing and it generates as many activities as partners with the same partner function. But when you execute them, the mail is sended to the first Partner introduced mail recipient althoug all them has the same partner Fuction.
For example:
Lead 111:
-Parties Involved:
Partner Function: "Employee Responsible" Employee: Frank Ellis
Partner Function: "Z3 Mantain Informed to" Employee: Michael Smith
Partner Function: "Z3 Mantain Informed to" Employee:Sara Ferguson
Actions:
Action 1 E mail to "Mantain Informed Partners"
Action 2 E mail to "Mantain Informed Partners"
When the action is executed both actions send the email to Michael Smith.
Why? I dont´t Know.
I can confirm yo that I did customize the action merging:
Action Merging: Set Highest Number of Processed Actions
Number of unprocessed actions: Une unprocessed action for each partner and processing type.
Thanks Again
Edited by: ribes marga on May 27, 2009 1:49 PM

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

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

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 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.

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.

ACK for receiver determination with 2 interface determination

Similar Messages

Maybe you are looking for