Interface Determination/BPM Error

Hi,
i have a idoc to file scenario,i am using a BPM.
In ID when configuring the Interface determination, i am not able to select any interface mapping? is this b`se i am using a BPM and since the trnsformation step in the BPM already refers a interface mapping??
Also i have 6 steps in my BPM :
1.receive -idoc
2.transformtaion
3.send
4.switch
5.transformation
6.send
which are in a block and i am throwing an alert for this block in case of exception.
when i try to execute the scenario, when i view PE in moni, the start of the process itself shows error, but then my 3rd and 4th step gets execeuted succesfully,
I am not sure why does the start of the process shows
error status? is it b`se of my alert in the exception handler??

Hi Harsha,
Use the document below to get the exact error message from mapping trace.
https://websmp104.sap-ag.de/~sapdownload/011000358700003141152005E/HowTo_Monitor_ccBPM.pdf
Also test your mapping in IR test tab using actual payload from the message in BPM(you can download the message from the failed step to test).
Regards
Anand

Similar Messages

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.

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.
"Message interface does not exist in any software components installed on this business system"
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

BPM interface determination error

Hi All,
i have BPM scenario. scenario like three files coming from the sender once picking the all file i have to merge these file based on the common filed in three files.
for this i used correlation in BPM
i followed the below steps:
1) i creatd three out bound service interfaces for the sender three files
2) one inbound service interface for the receiver.
3) four abstract service interfaces for the BPM.
5) Operation mapping between the abstract interfaces.
ID objects creation :
imported the integration process in ID from IR.
communication componets created for the sender & receiver
4 receiver determinations created 3 RD between Sender bussiness component & BPM ,1 RD between BPM & receiver business component
4 Interfaces determinastion created as per as RD
3 sender agreements
1 receiver agreement
while testing i got this error in SXMB_MONI
RCVR_DETERMINATION">CX_RD_PLSRV</SAP:Code>
<SAP:P1>Problem while determining receivers using interface mapping: No operation with XML root tag
i got confusion while creatin the Interfaces Determination i.e weather do we need mention Operation mapping between outbound service interface & abstract service interface
please correct what is the correct process to create the Interface determination in BPM like this scenario.
thanks in advance

Are you doing any content conversion in Sender file Adapter then check whether the Flat file properly converted to XML file or not?
You need to create Interface determination but if source and target interface message type is same then no need to specify operation mappinhg in Interface determiination.
So interface determination should be there without any operation mapping

Error with Enhanced Interface determination

Hi Experts,
In enhanced interface determination for message splitting w/o BPM, i have given the interface mapping.
But while testing the configuration.......... i am getiing an error at Interface Determination & Mapping which is not showing any processing log.
My mapping program works fine.
could anyone tell me where the problem is....

Hi,
Can you post the error message that you are getting....it will help experts solve your problem accurately.
Regards,
Abhishek.

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.

Error when trying multiple inbound interface determination for IDOC

Hi !
I have this scenario: File -> XI -> IDOC.
For each source file, I need to send multiple idoc packages, all to the same business system, but each package should be the result of different interface mappings.
All mappings have same source and target message types...e.g. source: MT_MyFile, target: CREMAS04.
To avoid creating a generic mapping program, we need to duplicate the current mapping program, make it handle the new case, and then add it as second interface mapping in Interface Determination, with same inbound interface, but different interface mapping, without conditions. All interface mapping should execute.
We are receving this error:
<SAP:Code area="IF_DETERMINATION">CX_ID_PLSRV</SAP:Code>
<SAP:P1>Inbound interface was found more than once (for same sender and receiver) for outbound interface urn:xxxxx/xxxx:.MI_xx_xxxxxxxx_xxx_xx</SAP:P1>
<SAP:Stack>Error when determining the inbound interface: Inbound interface was found more than once (for same sender and receiver) for outbound interface urn:xxxxx/xxxx:.MI_xx_xxxxxxxx_xxx_xx Inbound interface was found more than once (for same sender and receiver) for outbound interface urn:xxxxx/xxxx:.MI_xx_xxxxxxxx_xxx_xx</SAP:Stack>
Any clues?
Regards,
Matias.

Hi Satish !
Thanks.
I need to send different IDOCs to SAME business system.
In Interface determination I need this:
Inbound Interface -
Condition -
Interface Mapping
IF_1 no condition M_1
IF_1 no condition M_2
I need to send BOTH IDOC packages to same business system.
But it keeps throwing the posted error.
Regards,
Matias.

RFC to BPM - Error in receiver interface

Hi everybody,
I have created the scenario below.
i imported the ZStart_Job rfc from R/3
i created the MI_Start_Abs (abstract and async) - message type is same from ZStart_Job
i created the BPM_Job where the send interface is MI_Start_Abs.
i configured the sender and receiver agrameent, receiver and interface determination and others.
i actived everything.
When i execute the "call function ZStart_Job", the execution dosent return error in Message Monitoring, but appears one green flag with hit "Scheduled".
In XML body show the error below
<Trace level="1" type="T">--start receiver interface action determination</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface</Trace>
<Trace level="1" type="T">select interface namespace</Trace>
<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
Can anybody help me?

Guys,
I used the Configuration Wizard for create configuration again.
But occurs the same error below
<Trace level="1" type="T">--start receiver interface action determination</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface</Trace>
<Trace level="1" type="T">select interface namespace</Trace>
<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
PLEASE, can anybody helpe me?

Non BPM process - no mapping object found in interface determination

I'm working on a non BPM synchronous process of kind HTTP=>XI=>RFC
I completed my design and onto config now. I created receiver determination for HTTP (no sender agreement) and receiver determination for RFC. In my interface determination I cannot find mapping objects.
I included in HTTP service, the request, sync and response message and RFC shows up naturally with RFC objects.
Any ideas. I've been struggling with this for over a day now.
Thanks.

Hi Parimala -
Just to clarify, for this scenario, here's what you need:
Design
1. One Message Interface (outbound/synchronous) corresponding to your HTTP request/response. You don't need a Message Interface nor Message Type for your inbound/synchronous RFC.
2. Request Mapping corresponding to request
- HTTP request Message Type to imported RFC (request)
3. Response Mapping corresponding to response
- RFC.response to some Message Type for the response
4. Interface Mapping
- interfaces: your outbound/sync Message Interface corresponding to HTTP request to imported RFC
- at bottom request tab, select your Request mapping (#2 above)
- at bottom response tab, select your Response mapping (#3 above)
Config
When you say the following:
>>>I completed my design and onto config now. I created receiver determination for HTTP (no sender agreement) and receiver determination for RFC.
Don't know if that's a typo, but there should only be one receiver determination based on your sending system/service, sending interface (HTTP one), and interface namespace.
Confirm the above steps and see if that helps.
Regards,
Jin

Enhanced interface determination IN BPM

Hello experts,
Question is in the title.
I'm in PI 7.0 and i think it's not possible. Can you confirm it ?
Thank you for your responses.
Regards.

Yes ! ;o)
But, i have a scenario with BPM : file -> synchronous call bapi -> 2 split mapping (using enhanced interface determination) -> possibility 4 files.
It's not a problem for me, because i will 'stop' BPM afterthe Bapi call, but i have to create most CC.
It was just an quastion for me.
Thanks.

Reg: Error at Interface Determination

hi friends
i have designed a scenario for MS SQL to R3 i.,e JDBC to RFC adapters. i have designed and activated but while monitoring communication channels it was showing error at sender as INTERFACE DETERMINATION have not been configured, but i have checked it , it was configured correctly .so, what might be the problem .
with regards
suman

Hi,
check in bottom of receiver determination screen under receiver business system wheather interface determination inbound message interface and interface mappings are visible.
also try making some dummy changes and activate it again.
also check in sxi_cache ur interface determination.
thanks.

ERROR occured at Interface Determination

Hi all,
     Ths is satya our senario is RFC to FILE but the problem is sender RFC is already configuerd to another interface.How can i assign that sender RFC to my interface.Hear i am using Sender service instead of sender system for testing purpose.
But when i am testng the test configuration an error is getting triggered in interface determination in bound interface not found at test configuration tools. Give me solution
Thanks & Regards,
satya.T

Hi Satya,
-->You are dealing with the Scenario RFC to FILE.
-->So it is not mandatory to create the Message interface for Sender (in your case for RFC)because RFC it self is an interface.
-->so create Message Interface for File.
-->Coming to ID:
                You are using the Business Service so,for that you need to maintain the Logical system and Details of the R/3 system.
                Double click on your Business service and from Menu-->Click on Adapter Specific Identifiers and check the details if not maintain the details as said above.
Thanks

Error while specifying condition in Interface Determination

Hi all,
I am facing a typical problem
It's a proxy to file scenario with mutiple receivers.
In the interface determination when we are trying to specify the condition, it gives the following error.
"Message interface does not exist in any software components installed on this business system".
Detailed solution would be highy helpful.
regards.
younus

Hi Yonus,
It seems that u have made changes in SWCV after doing the configuration.
Try out thess:
STEP1->In ID
Go to menu :--> Enviorment->clear SLD cache
Step2->In IR
Go to menu :-->Tools->Transfer from SLD->Update application component and then step 1
Step3->IN SLD
Check the the SWCV u r using is associated with the Business system u are using. Check for the checkbox for SWCV in Business System.
Sachin
Message was edited by:
Sachin Dhingra

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

Creating interface determination error

Hi Experts,
I upgrade the our PI system to
XI TOOLS 7.10 SP006 11
XI PCK 7.10 SP006 11
After that, i cant create interface determination with wizard. When i finish the wizard, interface determination isnt created and there is a lock in the integration builder.
I tried to make manual interface determination but i cant select the operation mapping..
im waiting ur answers
thanks

Hi,Arvind:
Did you upgrade to SPS06 with the whole SP stack or just upgrade several components of PI?
If you just upgrade several components of PI,it is not recommended by SAP.
If you upgrade the whole components with SPS06,try to upgrade to SPS07 and take a look at NOTES:1259837&1263112, or the java component "ESPFRAMEWORK07_0-20001918" can not be deployed successfully.
regards
yu ming

Interface Determination/BPM Error

Similar Messages

Maybe you are looking for