No inbound interface available in interface determination.

Hi Guys,
I am doing File to web service scenario. I have completed all the steps required in Integration Repository. But in Integration directory while doing interface determination, I am not able to locate my inbound interface. It is showing message No Object found.
I have checked interface mapping and in it I am using same outbound and inbound interface.
I would appreciate yours inputs.

Hi Sunil,
You must have chosen Inbound and Outbound Interface for Interface Mapping in the Integration repository.
Also, when you do you Interface Determintaion you must have chosen sender and receiver Interface. They have to be the same as described in the Integration repostiory for the Interface mapping to come up in ID.
Please can you activate your Interface mapping again and try importing it into ID
Regards
Vijaya
Message was edited by: vijaya kumari

Similar Messages

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.

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

Error when determining the inbound interface

Hi Experts,
I have a Scenario, where i am using Multi mapping Scenario in DEBMDM IDOC from ECC to Xml_File-1(DEBMAS) and Xml_File-2(ADRMAS).
When i Execute the Scenario by sending the IDOC from ECC , i am getting the below error.
Runtime error
Error when determining the inbound interface: Inbound interface found several times (for same sender and receiver) for the outbound interface urn:sap-com:document:sap:idoc:messages.DEBMDM.DEBMDM06
Scenario Steps
1) No Condition in Interface Determination
2) 0..unbounded in Message Mapping and Operational Mapping.
3) E1KNA1 is mapped to E1KNA1
4) E1ADRMAS is mapped to E1ADRMAS
5) One Message Mapping and 1 Operational Mapping.
Thanks in Advance.
Sriram.

Hello,
I have a Scenario, where i am using Multi mapping Scenario in DEBMDM IDOC from ECC to Xml_File-1(DEBMAS) and Xml_File-2(ADRMAS).
Since your scenario makes sure that the 2 files are created, there is no need to use multi-mapping. Rather, you can use an interface determination split. To do this:
1. declare xml_file1 as service interface 1, xml_file2 as service interface 2
2. do not change target occurrence in message mapping and operation mapping, maintain it as 1..1
( 2 operation mappings)
3. in ID, add the two service interfaces in your interface determination
At runtime, it will split into two inbound interfaces.
When i Execute the Scenario by sending the IDOC from ECC , i am getting the below error.
Runtime error
Error when determining the inbound interface: Inbound interface found several times (for same sender and receiver) for the outbound interface urn:sap-com:document:sap:idoc:messages.DEBMDM.DEBMDM06
Were you able to declare the 2 xml_files as two separate service interface(different names) in your operation mapping?
Hope this helps,
Mark

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.

Interface mapping not visible in interface determination

Hi,
when i create Interface determination in ID i could see Message interface and i could not my Interface mapping in that.
It is saying no objects found.
when i select enhanced instead of standard i could see my Interface mapping
plz give some idea reg. this
Thanks

Hi,
Check if there is any Interface mapping available between the Outbound Message Interface name and Inbound Message Interface name which you are using in your Interface Determination. Check carefully.
Thanks
aMit

Condition based Interface determination

Hi ,
Environment : PI 7.1.
Scenario : File to Proxy.
In this scenario , We have a single file interface which reads a file and routes the data to two different inbound interfaces.
Steps followed to do this -
>>Defined two inbound interfaces interface1 & interface2.
>>Both interfaces are pointed to same ECC system.
>>Read the file using a single sender file communication channel.
>>Define receiver ECC in the receiver determination.
>> Define interface determination based on a value of a field in the file structure(source structure). Used XPATH to define this content based routing and selected operation mapping specific to the interface.
1 sender agreement
1 receiver determination ( not using enhaced receiver determination because we have only one receiver)
1 interface determination which has two receiving interfaces based on XPATH condition ( maintain order runtime is checked)
2 Receiver agreements.
2 Communication channels.
For example if you have 10 lines in a file , out of which if 5 lines has a value related to interface 1 & 5 lines has a value related to interface 2. It should push the data into two different proxies as configured.
We are facing a problem in this scenario -
There is no consistency in the logic. Some times it runs interface 1 & some time it executes interface 2.
based on condition 1 it routes the data to interface 1 successfully but the structure is not getting created for interface 2 so it is giving an error stating the interface 2 structure is not available.
In SXMB_MONI the branching steps show two subnodes but if you see the log it shows that in subnode 1 the sender is sender interface & the receiver is interface 1 based on the filter condition. If you see the log for subnode 2 then it shows the sender is sender & the receiver as interface 2 below that it shows another entry which shows the reciver interface is interface2.
Please evaluate and let us know if the approach we are following works or not. If there is any limitations please let us know how to achive this.
Regards,
Reddy

Hi,
Your design is correct but here you missed one point. Here the message is send either to receiver1 or receiver2 depending on the condition but not both. As this does not result in multiple messages with the same payload because only one condition can ever be true at runtime. For more details see the below link
http://help.sap.com/saphelp_nw04/helpdata/en/46/8015de950e6be3e10000000a155369/frameset.htm
If you want to create multiple message then you need do 1:n mapping :
http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3417700)ID2056393550DB10021342992851308291End?blog=/pub/wlg/2927
Shweta.

Inbound interface was found more than once

Hi All,
Currently I'm working on a scenario wherein an invoice file is generated and created on FTP server, PI system picks up invoice (xml file) and sends to customer via EDI 810. The scenario failed in sxmb_moni and below is the error message.
<SAP:Category>XIServer</SAP:Category>
<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:xyz:sap:components. 810_Outbound_Async_MI</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error when determining the inbound interface: Inbound interface was found more than once (for same sender and receiver) for outbound interface urn:xyz:sap:components. 810_Outbound_Async_MI Inbound interface was found more than once (for same sender and receiver) for outbound interface
Can anyone help me out and provide some valuable suggestions.
Regards
Faisal

Hi Abdul,
Try to run the scenario in the ID.
There is one test tool to in directory for this, login to ID --> go to Tools --> Test configuration.
This will show you the error in the exact step.
-Supriya.

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

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

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

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: &#39;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

Interface Mapping not found in interface determination

Hello experts,
I am facing a very basic problem in my scenario which is stoping me from moving forward.
In interface determination when i select the inbound interface and then try to select the interface mapping, nothing is shown in the value help.
this is happening for all my scenarios even though the IR configurations are correct and I have also refreshed the cache.
What can be the problem? some installation problem, SLd prob or IR??? Please help as i am stuck!!
Thanks a lot in advance.
Yash

Hi Yash,
This is really very strange despite of most probable solutions.
Can you do one thing delete all configuration objects in Directory and activate. Now in repostiory remove mapping programs(message mapping and interface maaping) and activate.
Check the message types and data types and message interfaces.
Specially in message interfaces check whether correct message types are assigned. If so proceed with new mapping programs and activate the objects.
Also do a fresh configuration in ID, activate and execute your scenario.
One question, can you give a arrow diagram of scenario(e.g. file>xi>JMS)
Thanks,
Gujjeti

No inbound interface available in interface determination.

Similar Messages

Maybe you are looking for