Interface determination Issue in PI7.1

Hi ,
I am working on PI 7.1
Problem 1:
I am not able create any interface determination objects. There is a lock object created everytime I use the wizard. Unlocking the object and run the cache refresh has not helped..
I am able to create the interface determination manually after removing the lock. But now I am not able to associate a operation/interface mapping to the Interface determination . After I selected a message/service interface in the Interface determination, I clicked on the mapping option. The possible mapping was showed up on the list. But once I select one option from the list it does not show up in the interface determination. The field remains blank.
Problem 2:
I am unable to open the existing interface determination also. These interface determinations are present in the DEV environment.I have taken the system copy of the dev environment on the UAT environment.I am getting the below error when i try to open the interface determination
====================================================================
= Root Exception ===================================================
====================================================================
Thrown:
com.sap.aii.utilxi.swing.toolkit.ServerCallCancelledException: Unexpected exception.
     at com.sap.aii.ib.clsif.gen.BeanAccessHandler.handleRuntimeExInBusinessMethod(BeanAccessHandler.java:87)
     at com.sap.aii.ib.clsif.oa.ObjectAccess.read(ObjectAccess.java:112)
     at com.sap.aii.ib.client.oa.ObjectHandler.read(ObjectHandler.java:119)
     at com.sap.aii.ib.gui.editor.DefaultPersistenceHandler.load(DefaultPersistenceHandler.java:94)
     at com.sap.aii.ib.gui.editor.XiDocument.load(XiDocument.java:249)
     at com.sap.aii.utilxi.swing.framework.cmd.OpenCommand.load(OpenCommand.java:353)
     at com.sap.aii.utilxi.swing.framework.cmd.OpenCommand.localOpen(OpenCommand.java:273)
     at com.sap.aii.utilxi.swing.framework.cmd.OpenCommand.execute(OpenCommand.java:211)
     at com.sap.aii.utilxi.swing.framework.ExecutionContext.execute(ExecutionContext.java:198)
     at com.sap.aii.utilxi.swing.framework.ExecutionContext.executeSafe(ExecutionContext.java:154)
     at com.sap.aii.ib.gui.operations.OperationsServiceProvider.executeDefaultOperation(OperationsServiceProvider.java:295)
     at com.sap.aii.ib.gui.nav.HierarchyNode.executeDefaultOperation(HierarchyNode.java:59)
     at com.sap.aii.utilxi.swing.framework.navigation.tree.DefaultTreeCard.handleHierarchyEvent(DefaultTreeCard.java:198)
     at com.sap.aii.utilxi.swing.framework.navigation.tree.ThreadedTree.fireHierarchyActionEvent(ThreadedTree.java:542)
     at com.sap.aii.utilxi.swing.framework.navigation.tree.ThreadedTree.executeStandardOperation(ThreadedTree.java:2264)
     at com.sap.aii.utilxi.swing.framework.navigation.tree.ThreadedTree$DblClickHandler.mouseReleased(ThreadedTree.java:2196)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.Component.processMouseEvent(Unknown Source)
     at javax.swing.JComponent.processMouseEvent(Unknown Source)
     at java.awt.Component.processEvent(Unknown Source)
     at java.awt.Container.processEvent(Unknown Source)
     at java.awt.Component.dispatchEventImpl(Unknown Source)
     at java.awt.Container.dispatchEventImpl(Unknown Source)
     at java.awt.Component.dispatchEvent(Unknown Source)
     at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
     at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
     at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
     at java.awt.Container.dispatchEventImpl(Unknown Source)
     at java.awt.Window.dispatchEventImpl(Unknown Source)
     at java.awt.Component.dispatchEvent(Unknown Source)
     at java.awt.EventQueue.dispatchEvent(Unknown Source)
     at com.sap.aii.utilxi.swing.toolkit.Guitilities$EventProcessor.dispatchEvent(Guitilities.java:319)
     at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.run(Unknown Source)
====================================================================
== Content from the LogHandler =====================================
====================================================================
#300 11:56:48 [AWT-EventQueue-2] WARNING com.sap.aii.utilxi.swing.toolkit.ButtonPanel: Special button of type 4 was not added in order (class com.sap.aii.utilxi.swing.toolkit.ButtonPanel)
#299 11:56:48 [AWT-EventQueue-2] ERROR com.sap.aii.utilxi.swing.toolkit.ExceptionDialog: Throwable
Thrown:
com.sap.aii.utilxi.swing.toolkit.ServerCallCancelledException: Unexpected exception.
     at com.sap.aii.ib.clsif.gen.BeanAccessHandler.handleRuntimeExInBusinessMethod(BeanAccessHandler.java:87)
     at com.sap.aii.ib.clsif.oa.ObjectAccess.read(ObjectAccess.java:112)
     at com.sap.aii.ib.client.oa.ObjectHandler.read(ObjectHandler.java:119)
     at com.sap.aii.ib.gui.editor.DefaultPersistenceHandler.load(DefaultPersistenceHandler.java:94)
     at com.sap.aii.ib.gui.editor.XiDocument.load(XiDocument.java:249)
     at com.sap.aii.utilxi.swing.framework.cmd.OpenCommand.load(OpenCommand.java:353)
     at com.sap.aii.utilxi.swing.framework.cmd.OpenCommand.localOpen(OpenCommand.java:273)
     at com.sap.aii.utilxi.swing.framework.cmd.OpenCommand.execute(OpenCommand.java:211)
     at com.sap.aii.utilxi.swing.framework.ExecutionContext.execute(ExecutionContext.java:198)
     at com.sap.aii.utilxi.swing.framework.ExecutionContext.executeSafe(ExecutionContext.java:154)
     at com.sap.aii.ib.gui.operations.OperationsServiceProvider.executeDefaultOperation(OperationsServiceProvider.java:295)
     at com.sap.aii.ib.gui.nav.HierarchyNode.executeDefaultOperation(HierarchyNode.java:59)
     at com.sap.aii.utilxi.swing.framework.navigation.tree.DefaultTreeCard.handleHierarchyEvent(DefaultTreeCard.java:198)
     at com.sap.aii.utilxi.swing.framework.navigation.tree.ThreadedTree.fireHierarchyActionEvent(ThreadedTree.java:542)
     at com.sap.aii.utilxi.swing.framework.navigation.tree.ThreadedTree.executeStandardOperation(ThreadedTree.java:2264)
     at com.sap.aii.utilxi.swing.framework.navigation.tree.ThreadedTree$DblClickHandler.mouseReleased(ThreadedTree.java:2196)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.Component.processMouseEvent(Unknown Source)
     at javax.swing.JComponent.processMouseEvent(Unknown Source)
     at java.awt.Component.processEvent(Unknown Source)
     at java.awt.Container.processEvent(Unknown Source)
     at java.awt.Component.dispatchEventImpl(Unknown Source)
     at java.awt.Container.dispatchEventImpl(Unknown Source)
     at java.awt.Component.dispatchEvent(Unknown Source)
     at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
     at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
     at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
     at java.awt.Container.dispatchEventImpl(Unknown Source)
     at java.awt.Window.dispatchEventImpl(Unknown Source)
     at java.awt.Component.dispatchEvent(Unknown Source)
     at java.awt.EventQueue.dispatchEvent(Unknown Source)
     at com.sap.aii.utilxi.swing.toolkit.Guitilities$EventProcessor.dispatchEvent(Guitilities.java:319)
     at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.run(Unknown Source)

Hi Shilpa,
Ask your basis guys to check the SP level of JAVA components in system component information of your PI7.1 system............ask them to check for patches for your SP level of PI7.1 or upgrade to a higer SP level...........
Also try this from your PI IB webpage, go to Administration - JAVA web start administration - then click on execute link in the status window and do a reinitialization of your JAVA web start...........then close your ID and reopen your ID........then create your interface determination again in ID...........
Regards,
Rajeev Gupta
Edited by: RAJEEV GUPTA on Apr 29, 2009 9:05 AM
Edited by: RAJEEV GUPTA on Apr 29, 2009 9:25 AM

Similar Messages

  • Interface determination issue.

    Hi Experts,
    We are using Idoc(Matmas) to file scenario wherein we are facing the below issue
    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="IF_DETERMINATION">NO_IIF_CASE_ASYNC</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Unable to find an inbound interface</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    The condition used in Interface determination is /Zmatmas05/idoc/e1maram/mstae=mw
    Please let me know how to rectify this issue.
    Thanks & Regards,
    Ranganath.

    Hello,
    Try using double slash in your xPath (for PI7.1) instead of just one, so from
    /Zmatmas05/idoc/e1maram/mstae=mw
    to
    //Zmatmas05/idoc/e1maram/mstae=mw
    Hope this helps,
    Mark

  • 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 <b>not </b>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.
    <b>MONI for RD</b>
    - <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.
    <b>MONI for ID</b>
    <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

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

  • EOIO Problem in the Interface Determination

    Hi All,
    I have two different source systems (BUSSYS111 , BUSSYS222) and one target system BUSSYS999 (SAP System). I have two different mappings in each interface
    Interface 1:
    BUSSYS111 -> BUSSYS999 (file1 -> RFC, file1 -> JDBC, without BPM, split mapping)
    Interface mappings:
    Flow1 : BUSSYS111_File_To_BUSSYS999 (FILE -> RFC)
    Flow2 : BUSSYS111_FILE_TO_BUSSYS111 (File -> JDBC)
    Flow2 should execute only if the Flow1 is successful (RFC call is successful).
    Interface Determination for Interface 1
    Sender: BUSSYS111
    Interface: Source Interface1
    Receiver : BUSSYS999
    Maintain Order at runtime Checked.
    Receiver Interfaces
    BUSSYS111_File_To_BUSSYS999 (Result of Flow1 & Flow2)
    BUSSYS111_FILE_TO_BUSSYS111
    The queue that is getting generated is *XISERIALIZE0011_BUSSYS999*_ (EOIO)
    Interface 2:
    BUSSYS222 -> BUSSYS999 (file1 -> RFC, file1 -> JDBC, without BPM, split mapping)
    Interface mappings:
    Flow1 : BUSSYS222_File_To_BUSSYS999 (FILE -> RFC)
    Flow2 : BUSSYS222_FILE_TO_BUSSYS111 (File -> JDBC)
    Flow2 should execute only if the Flow1 is successful (RFC call is successful).
    Interface Determination for Interface 1
    Sender: BUSSYS222
    Interface: Source Interface1
    Receiver : BUSSYS999
    Maintain Order at runtime Checked.
    Receiver Interfaces
    BUSSYS222_File_To_BUSSYS999 (Result of Flow1 & Flow2)
    BUSSYS222_FILE_TO_BUSSYS222
    The problem here is in both the cases above, the interfaces seems to be independant. But sometimes for some messages the same queue *XISERIALIZE0011_BUSSYS999*_ is used and for some, a different queue is generated.and if the same queue is used in both the cases, the first interface fails, then the second one is going into holding state.
    Can any one help to resolve this issue without going for the BPM (as it would be a design change) and it is already in production.
    Thanks in Advance
    Anil

    Hi,
    in the documentation
    Interface Determination - Enabling Application-to-Application Processes - SAP Library
    its mentioned as
    You specify manually to which inbound interface at the receiver the message is to be forwarded. You can also specify the mapping that is to be executed. If you specify more than one inbound interface, you can specify conditions for forwarding the message to the inbound interfaces. These conditions are evaluated at runtime.
    so better to raised it to SAP.
    Reg,
    avinash M

  • 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

  • Interface Determination doubt

    Hi guys,
    I have a file with the following example source:
    80
    80
    56
    25
    32
    80
    56
    … The target is an R/3 and the interface is IDoc. All lines with value “80” should map to RPLMAS02 and the others values to ARTMAS 05. So, is two different mappings based on content field for the same target service “R/3”.
    I already have two different mappings for each IDoc type, and I’m using the function “createIf” to exclude the lines that I don’t want to add in each IDoc. But, I can’t do it using XPath conditions in the Interface Determination, because both mappings are always performed…
    Which is the best way to achieve this issue?
    Thanks in advance,
    Ricardo.

    Hi folks,
    Thanks a lot for your prompt answers.
    Aamir: Take my source code as an example, I have several lines with different key field values. Based on these key field values I want to route both contents to different mappings. The lines with 80 value to RPLMAS mapping and the rest (different from 80) to ARTMAS mapping. But, from my understanding, at Interface Determination level, one message is considered and the XPath conditions only checks where 80 value exists or not. As I've a message with both values 80 and !=80), both mappings are performed and the last one is generated empty with error.
    Saravana: I didn't understood where this "workaround" solve my issue above?
    Resuming: I want to route lines for two different mappings and not an entire message. I mean, I want to put lines 80 in one mapping and the rest in another every thing at the same execution time.
    Thanks in advance,
    Ricardo.

  • Dynamic interface determination based on file content

    Dear all,
    I am trying for a while to solve my issue, but wasn't able to find the answer. Maybe you could point me in the right direction whether using standard or BPM...
    I've got one file with multiple entries. Dependend on a field value, I would like to call the right interface and Idoc.
    Sample message:
    <customers>
         <customer>
              <name>ABC</name>
              <city>XYZ</city>
              <trigger>A</trigger>
         </customer>
         <customer>
              <name>DEF</name>
              <city>QRT</city>
              <trigger>A</trigger>
         </customer>
         <customer>
              <name>GHI</name>
              <city>JKL</city>
              <trigger>B</trigger>
         </customer>
         <customer>
              <name>MKN</name>
              <city>TZG</city>
              <trigger>A</trigger>
         </customer>
    </customers>
    Dependend on the content of field "trigger" I would like to send the message to the correct interface (Idoc). I was able to trigger the interface selection in my interface determination based on a condition. So I am looking for field trigger and if = A -> Interface A is called and if = B -> interface B is called. However, it seems it is only checking for the first entry of my payload and then sending all customers to the same interface, no matter what I've got in the trigger field. What I would need is a message split and then only posting the correct rows to the selected interface.
    Any ideas would be highly appreciated.
    Thanks a lot,
    Jens

    Hi Jens,
    I can think of two options:
    1) The logical expression (condition) in the Interface Determination can hold a XPath expression. In your case, it could be complex, as one single XPath has to loop at all the line times for an occurrance.
    Some XPath help is available at: http://www.w3schools.com/xpath/xpath_functions.asp#sequence
    /people/shabarish.vijayakumar/blog/2006/06/07/customise-your-xpath-expressions-in-receiver-determination
    The objective will be to remove the contexts on the trigger node to get a sequence consisting only of the trigger values, and then performing an 'index-of' function on value 'A'. If the result is a null value, then that trigger does not exist and the interface determination will not pass for 'A'. Similar condition can be used for other values of trigger.
    2) Create a separate receiver system / service for each interface A, B etc. Then you can use the enhanced Receiver Determination feature in the IR itself if you are on SP16. Check this:
    /people/venkataramanan.parameswaran/blog/2006/03/17/illustration-of-enhanced-receiver-determination--sp16
    Good luck,
    Bhanu

  • 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

  • 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

  • Abap proxy with attachments in enhanced interface determination/mapping

    Hi guys.
    We were receiving a abap proxy from ECC with a pdf attached in the header.
    This was the scenario PROXY ---> FILE
    We used the PayloadSwapBean Module in a Receiver File Adapter to get this document and put it in a FTP Server.
    Now we have to make and improvement in the scenario and we have to generate two receiver interfaces so the scenario looks like this:
    PROXY ---> FILE and JDBC.
    So we have to use an enhanced interface mapping and an enhanced interface determination.
    The problem is that with this enhanced interface determination/mapping the attached document is lost.
    Any solution?
    Thanks a lot.
    Regards.

    > The problem is that with this enhanced interface determination/mapping the attached document is lost.
    I know there was an issue in early PI 7.1 SP versions. maybe you find a bug fix for this?
    Otherwise report to SAP.

  • Error in enhanced interface determination...

    Hi All,
    we have a file to file and to mail scenario.
    We have created one sender CC , one file receiverCC and one MailCC.
    In enhanced interface determination the respective interface mapings are specified .now the issue we are facing is if the processing of the file fails mail should not be sent.
    but in our scenario even if the file processing fails the ail is being sent.
    pls suggest wat might be the problem.
    regards,

    Hi,
    In Receiver Determination, the File receiver and Mail Rceiver works independently.
    There will not be such sequence maintained in Receiver determination that the failure of one receiver should affect to other one.
    Although there is one option in Receiver determination that if the receiver determination get failed then you could stop the processing.
    This will help you out.
    If in case this will not work for you then BPM will the confirmed solution for it.
    Thanks
    Swarup

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

  • Error while opening the Interface determination

    Hi,
    I am working on PI system(unix platform) which is a system copy(from a windows platform).
    When i tried opening few interface determinations which are already present in ID,  it gives me following Error.
    ====================================================================
    = Root Exception ===================================================
    ====================================================================
    Thrown:
    com.sap.aii.utilxi.swing.toolkit.ServerCallCancelledException: Unexpected exception.
         at com.sap.aii.ib.clsif.gen.BeanAccessHandler.handleRuntimeExInBusinessMethod(BeanAccessHandler.java:87)
         at com.sap.aii.ib.clsif.oa.ObjectAccess.read(ObjectAccess.java:112)
         at com.sap.aii.ib.client.oa.ObjectHandler.read(ObjectHandler.java:119)
         at com.sap.aii.ib.gui.editor.DefaultPersistenceHandler.load(DefaultPersistenceHandler.java:94)
         at com.sap.aii.ib.gui.editor.XiDocument.load(XiDocument.java:249)
         at com.sap.aii.utilxi.swing.framework.cmd.OpenCommand.load(OpenCommand.java:353)
         at com.sap.aii.utilxi.swing.framework.cmd.OpenCommand.localOpen(OpenCommand.java:273)
         at com.sap.aii.utilxi.swing.framework.cmd.OpenCommand.execute(OpenCommand.java:211)
         at com.sap.aii.utilxi.swing.framework.ExecutionContext.execute(ExecutionContext.java:198)
         at com.sap.aii.utilxi.swing.framework.ExecutionContext.executeSafe(ExecutionContext.java:154)
         at com.sap.aii.ib.gui.operations.OperationsServiceProvider.executeDefaultOperation(OperationsServiceProvider.java:295)
         at com.sap.aii.ib.gui.nav.HierarchyNode.executeDefaultOperation(HierarchyNode.java:59)
         at com.sap.aii.utilxi.swing.framework.navigation.tree.DefaultTreeCard.handleHierarchyEvent(DefaultTreeCard.java:198)
         at com.sap.aii.utilxi.swing.framework.navigation.tree.ThreadedTree.fireHierarchyActionEvent(ThreadedTree.java:542)
         at com.sap.aii.utilxi.swing.framework.navigation.tree.ThreadedTree.executeStandardOperation(ThreadedTree.java:2264)
         at com.sap.aii.utilxi.swing.framework.navigation.tree.ThreadedTree$DblClickHandler.mouseReleased(ThreadedTree.java:2196)
         at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
         at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
         at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
         at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
         at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
         at java.awt.Component.processMouseEvent(Unknown Source)
         at javax.swing.JComponent.processMouseEvent(Unknown Source)
         at java.awt.Component.processEvent(Unknown Source)
         at java.awt.Container.processEvent(Unknown Source)
         at java.awt.Component.dispatchEventImpl(Unknown Source)
         at java.awt.Container.dispatchEventImpl(Unknown Source)
         at java.awt.Component.dispatchEvent(Unknown Source)
         at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
         at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
         at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
         at java.awt.Container.dispatchEventImpl(Unknown Source)
         at java.awt.Window.dispatchEventImpl(Unknown Source)
         at java.awt.Component.dispatchEvent(Unknown Source)
         at java.awt.EventQueue.dispatchEvent(Unknown Source)
         at com.sap.aii.utilxi.swing.toolkit.Guitilities$EventProcessor.dispatchEvent(Guitilities.java:319)
         at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
         at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
         at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
         at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
         at java.awt.EventDispatchThread.run(Unknown Source)
    Caused by: com.sap.engine.services.rmi_p4.P4RuntimeException: Unexpected exception.
         at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:643)
         at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:612)
         at com.sap.engine.services.rmi_p4.reflect.P4InvocationHandler.invokeInternal(P4InvocationHandler.java:160)
         at com.sap.engine.services.rmi_p4.reflect.AbstractInvocationHandler.invoke(AbstractInvocationHandler.java:52)
         at $Proxy26.read(Unknown Source)
         at sun.reflect.GeneratedMethodAccessor48.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
         at java.lang.reflect.Method.invoke(Unknown Source)
         at com.sap.engine.services.ejb3.runtime.impl.StatelessRemoteStubInvocationHandler.invoke(StatelessRemoteStubInvocationHandler.java:89)
         at $Proxy27.read(Unknown Source)
         at sun.reflect.GeneratedMethodAccessor48.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
         at java.lang.reflect.Method.invoke(Unknown Source)
         at com.sap.aii.ib.clsif.login.BeanProxy.invoke(BeanProxy.java:114)
         at $Proxy27.read(Unknown Source)
         at com.sap.aii.ib.clsif.oa.ObjectAccess.read(ObjectAccess.java:101)
         ... 39 more
    Caused by: java.io.InvalidClassException: com.sap.aii.ib.bom.gen.container.ContainerElementState$XsdSimpleState; local class incompatible: stream classdesc serialVersionUID = 42, local class serialVersionUID = -6470496719860432109
         at java.io.ObjectStreamClass.initNonProxy(Unknown Source)
         at java.io.ObjectInputStream.readNonProxyDesc(Unknown Source)
         at java.io.ObjectInputStream.readClassDesc(Unknown Source)
         at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
         at java.io.ObjectInputStream.readObject0(Unknown Source)
         at java.io.ObjectInputStream.defaultReadFields(Unknown Source)
         at java.io.ObjectInputStream.readSerialData(Unknown Source)
         at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
         at java.io.ObjectInputStream.readObject0(Unknown Source)
         at java.io.ObjectInputStream.defaultReadFields(Unknown Source)
         at java.io.ObjectInputStream.readSerialData(Unknown Source)
         at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
         at java.io.ObjectInputStream.readObject0(Unknown Source)
         at java.io.ObjectInputStream.defaultReadFields(Unknown Source)
         at java.io.ObjectInputStream.readSerialData(Unknown Source)
         at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
         at java.io.ObjectInputStream.readObject0(Unknown Source)
         at java.io.ObjectInputStream.readObject(Unknown Source)
         at java.util.Hashtable.readObject(Unknown Source)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
         at java.lang.reflect.Method.invoke(Unknown Source)
         at java.io.ObjectStreamClass.invokeReadObject(Unknown Source)
         at java.io.ObjectInputStream.readSerialData(Unknown Source)
         at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
         at java.io.ObjectInputStream.readObject0(Unknown Source)
         at java.io.ObjectInputStream.defaultReadFields(Unknown Source)
         at java.io.ObjectInputStream.readSerialData(Unknown Source)
         at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
         at java.io.ObjectInputStream.readObject0(Unknown Source)
         at java.io.ObjectInputStream.defaultReadFields(Unknown Source)
         at java.io.ObjectInputStream.readSerialData(Unknown Source)
         at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
         at java.io.ObjectInputStream.readObject0(Unknown Source)
         at java.io.ObjectInputStream.defaultReadFields(Unknown Source)
         at java.io.ObjectInputStream.readSerialData(Unknown Source)
         at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
         at java.io.ObjectInputStream.readObject0(Unknown Source)
         at java.io.ObjectInputStream.readArray(Unknown Source)
         at java.io.ObjectInputStream.readObject0(Unknown Source)
         at java.io.ObjectInputStream.defaultReadFields(Unknown Source)
         at java.io.ObjectInputStream.readSerialData(Unknown Source)
         at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
         at java.io.ObjectInputStream.readObject0(Unknown Source)
         at java.io.ObjectInputStream.defaultReadFields(Unknown Source)
         at java.io.ObjectInputStream.readSerialData(Unknown Source)
         at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
         at java.io.ObjectInputStream.readObject0(Unknown Source)
         at java.io.ObjectInputStream.readObject(Unknown Source)
         at com.sap.engine.services.rmi_p4.reflect.P4InvocationHandler.readResult(P4InvocationHandler.java:303)
         at com.sap.engine.services.rmi_p4.reflect.P4InvocationHandler.invokeInternal(P4InvocationHandler.java:138)
         ... 52 more

    Hi,
    This is the problem with the XI system. You have to add some patches.
    For that check this link same problem solved here.
    PI 7.1 : Java exception creating new "Integration process"
    Thanks.

  • Interface determination : How to populate an Operation Mapping parameter

    Hi experts,
    I'm creating an interface determination, I have an Operation Mapping in it. This operation mapping has an inbound parameter. When Configurating this parameter I can choose between putting a constant or getting the value from a "container". Does anybody knows where this container will be? Is it  possible to take the parameter from an export parameter from Integration Process(BPM)?
    My interface:
    BPM->IDOC
    Regards
    Gonzalo

    Hi Stefan,
    What I wanted is leaving the mapping outside the BPM, instead that I can leave it inside and the result will be the wanted. What you mean implies something similar.
    I'm going to explain why, from the process dessign point of view, I want to leave the mapping outside.
    1.-I send an IDOC from my ERP
    2.-This IDOCs starts a BPM who, in a synchronous way, makes some updates in a DB.
    3.- Functionally speaking this updates could return a 0 if OK or a -1 if NOK
    4.-The BPM have to return an ACK to the ERP.
    For constructing this ACK I need my original IDOC and the result of the updates (-1 or 0).
    -If I put the mapping inside the BPM it will work (and that will probably be the final solution).
    -But, for a better performance and dessign, I wanted to leave the mapping outside.
    -I also want to know if the container in the interface determination we talked before can be used or what it means. (So let me know if you find out something about)
    -The third reason is that I find interesting speak about this topics in the forum if you know what I mean :-D
    Regards
    Gonzalo

Maybe you are looking for