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.

Similar Messages

  • INTERFACE DETERMINATION AND RECEIVER DETERMINATION DOUBTS???

    Hi Team
    I am having doubts regarding the Interafce Determination and the receiver determination. In pur landscape in our objects, some times i am seeing a Condition is being defined in the Interafce Determination  and sometimes  am seeing a Condition is being defined in the receiver determination . could you please let me know the differences between the above two.
    thanx in advance.

    Hi Nabhinav,
    Condtions in receiver determination - These conditions are evaluated and executed to determine the receivers for this incoming message.
    Condtions in Interface determination - These conditions are evaluated and ececuted to determine the Interface mapping to be called in order to map the source message to the target message.
    Please take a loot at these links for more details:
    http://help.sap.com/saphelp_srm50/helpdata/en/26/5ccd3bb4560f01e10000000a11402f/content.htm
    http://help.sap.com/saphelp_nwpi711/helpdata/en/48/ce2a8e3a8e5430e10000000a42189b/content.htm
    Also, search the SDN before posting you query.
    Regards, Gaurav.

  • 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

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

  • 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

  • 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

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

  • When we  will go for Ectended Interface Determination

    extended interface determination example give me any one...
    Regards,
    Vinay

    Enhanced (Mapping-Based) Interface Determination 
    Use
    In an enhanced interface determination, you do not enter the inbound interfaces manually, but 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.
    For example, you want to split an overall booking for a trip comprising connecting flights into individual booking orders (for each leg of the trip).
    You cannot realize this usage case with a standard interface determination (without using an integration process). A standard interface determination does allow you to specify multiple (N) inbound interfaces (with different mapping). In this case, N messages with the same payload and different receiver interfaces are generated from the source message before the mapping step; these are then transformed differently depending on the receiver interface. Therefore it is conceivable to write the mappings in such a way that the first mapping from the source message generates a message that only contains the first item, the second mapping generates a messages that only contains the second item, and so on. However, this no longer works if the number of items can vary with each new source message.
    You can use an enhanced interface determination to configure a mapping-based message split for this usage case. You assign the interface determination a multi-mapping that has a target interface with an element with occurrence 0...unbounded. At runtime, the individual messages (for the individual items) are calculated in the mapping step. First, the individual messages are grouped into a bulk message. Then, the bulk message is transferred to the Adapter Engine. The Adapter Engine then splits the bulk message up into the individual messages (see figure).
    Procedure at Runtime During Message Split
    Note that both the bulk message and all individual messages each have a message header with a receiver interface (see figure).
    Receiver Interfaces of Bulk Messages and Individual Messages
    The header of the individual messages contains the relevant receiver interface. It is based on the definition of the multi-mapping. Note that the receiver interfaces of the individual messages may be different. The receiver interface of the bulk message is always InterfaceCollection (namespace http://sap.com/xi/XI/System).
    If the message split only results in one message, the original message structure remains the same. In this case, a bulk message containing just one individual message is not created.
    You can also assign a multi-mapping with multiple different target interfaces to an enhanced interface determination (1:n transformation). Each target interface can contain elements with occurrence 0 ... unbounded.
    Messages cannot be sent by using different Adapter Engines in a mapping-based message split. This affects configuration thus: All receiver agreements that have a receiver interface from the mapping entered in the key must only be assigned communication channels with the following adapter types:
    -          RFC adapter
    -          SAP Business Connector adapter
    -          File/FTP adapter
    -          JDBC adapter
    -          JMS adapter
    -          SOAP adapter
    -          Marketplace adapter
    -          Mail adapter
    -          RNIF adapter
    -          CIDX adapter
    The adapters also have to all run on the same Adapter Engine.
    Adapters developed by partners also support a mapping-based message split if they run on the same Adapter Engine.
    Attachments from the original message are not appended to the messages resulting from the message split.
    Activities
    To execute a mapping-based message split, perform the following steps:
           1.      Integration Repository: Define the multi-mapping (see Developing Multi-Mappings for Message Splits).
           2.      Integration Directory: Define the interface determination.
    Note the following:
    ○     The outbound interface of the multi-mapping must be entered as the sender interface in the key of the interface determination.
    ○     The interface determination type must be set to Enhanced.
    ○     Select the multi-mapping you defined previously from the Integration Repository.
    To select the interface mapping, use the input help ( ).
    The target interfaces of the interface mapping are displayed in the Inbound Interfaces frame.
    The number of messages (for an inbound interface) created in the mapping step is displayed in the Occurrence column.
    regards,
    Raj

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

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

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

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

  • PI 7.1 Condition in interface-determination

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

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

  • No interface mapping in interface determination.

    Hi ALL,
    I am doing a simple File to File scenario. i have created all repository elements and activated them.
    Now while configuring them in Directory at interface determination level I can enter
    inbound Interface but in interface mapping i can´t see my Interface mapping object so i am getting error while testing scenario in Directory. 
    Can anybody tell me where exactly can be problem_
    Please note that i have created interface mapping object in repository.
    Thanks,
    Atul

    Hi Atul,
    After creating your business system or business service, click on your BS and include  the sender and receiver interfaces.
    Regards,
    Ramesh P

  • Complex interface determination fails for 0-N mappings

    We have a mapping question for the following scenario in PI 7.1: One message needs to be mapped into two target structures, it comes from the same sender and goes to same receiver. We need to call two different BAPI in the same SAP end system simultaneously.
    This is set up in one interface determination (same sender & receiver) where we use two different operation mappings with different receiver interface names. If the mapping have multiplicity 1, everything works fine and the message gets mapped to both receiver interfaces simultaneously. But, when the multiplicity of the mappings is 0-N (split mapping), then we get error message during interface determination phase:
    Error when determining the inbound interface: Inbound interface found several times (for same sender and receiver) for the outbound interface http://sending/namespace.sndInterfaceName
    How can we set up our scenario with two 0-N mappings without getting error message? One option would be combining two mappings in one, but this can not work in our case because of the high complexity.
    Any comments appreciated. Thanks, Sanjay.
    Edited by: Sanjay Gupta on Oct 21, 2010 10:50 PM

    Thanks for taking the time to look into this. See my comments below.
    1. Are you using multi mapping? Source Message type 1 and Traget message types 2 (added from messages tab in the mapping)
    We have two mappings, both create only a single output type, however, they are split mappings, meaning the mapping result message multiplicity is 0-N. So the answer is NO, this are no multi mappings
    2. At any time, can both the target messages be created or are they mutually exclusive?
    both targets will always be created, they are NOT mutually exclusive
    3. With in each message type that gets generated on the target side, is the occurance 1..1 or 1..unbounded?
    Don't fully get the question, but I assume you ask if the mapping is defined as a 1:1 or 1..N mapping. The latter is true.
    4. Is there any condition in the interface determination?
    Answer is No.
    5. How many operation mappings did you design.
    We have two operation mappings, each containing a different mapping to the different receiver interface type.
    Being said that, the ideal way should be, You need to create only one message mapping by adding multiple message types on the target side. I fully understand and agree with this statement, but due to the complexity of the mapping we need to separate it out into two mappings.
    It is confusing, that the described scenario works if the multiplicity of the mapping objects used is 1, but as soon as the multiplicity is 0-N (when using a split mapping instead), we start getting the error message.

  • Interface determination not found

    Hi,
    I am reading a file and trying to send it through a SOAP adapter.
    I am getting the below error
    Error when determining the inbound interface: No interface determination found for outbound interface http://test.com.testFlies_OB: Error while determining root tag of XML: BOM / charset detection failed
    No interface determination found for outbound interface http://test.com.testFlies_OB: Error while determining root tag of XML: BOM / charset detection failed
    Error while determining root tag of XML: BOM / charset detection failed
    Error while parsing an XML stream: 'BOM / charset detection failed&#39
    Need help.

    Hi,
    just check in ID, whether in receiver determination, you have specified interface determination.........if yes, then check whether it is activated or not............if not activated, then activate it...........
    if it is activated and still you get this error, then ask your basis guys to do a full CPACache refresh using XIDIRUSER..........then re-run your scenario.
    Regards,
    Rajeev Gupta

Maybe you are looking for

  • Error on sending email: this._attachmentWidgets

    Error on sending mail. Under Opera 12.12 and Windows 7, whenever I send a message through Verizon's web email, I get the message "Cannot convert 'this._attachmentWidgets to object" I get this message with or without attachments on the email.

  • [SOLVED] Questions on Acer Aspire One netbook resolution

    I've been digging through the wiki and googling everything, but I just can't figure out how to get the dang resolution right! I've got an Acer Aspire One (D257, model ZE6) and technically, it should be 1024 x 600. Everything seems like it's the right

  • Accrual Balance is not getting for particular leave

    on 11.5.10.2 we have defined four leave in leave management system but on of the leave is not working properly in regards of getting accrual balance while using this function "per_accrual_calc_functions.get_net_accrual", although all plan getting bal

  • Subcontract raw material consumption adjustment

    Dear All, I have made GR for subcontract material as below 1) out put material 100 pcs (101 mov type)         Input materisl 10 kgs (543 Mov type) but later i got to know that what ever input mateirial was consumed in actual is higher so actully coun

  • How do i stop yahoo hijacking my searches

    I have deleted yahoo from my search options and it no longer shows up under choices but still is the default. How do i remove keyword.url