Unable found inbound interface

hi,
i am facing below problem please help me.
Unable to find an inbound interface
IF_DETERMINATION">NO_IIF_CASE_ASYNC
Thanks & Regards,
veera

Veeru,
Please check this threads where they alreay solved this issue:
Re: "Unable to find inbound interface"
Error in interface determination wiht condition
Regards,
---Satish

Similar Messages

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.

"Unable to find inbound interface"

Hi all,
I have an error in sxmb_moni. Everytime I click on the red flag, I get the error, "Unable to find inbound interface". I already checked namespaces and SCV in IR. I also checked Interface Determination in ID. They are all correct. I have already tested my config in QAS, and everything went well. I'm having problems right now in PRD. Can somebody help me? thanks.
When I run Test Tool Config, I get the following error:
Interface Determination
Thanks.
Regards,
IX

Error when determining the inbound interface: Problem evaluating a condition: Exception
CX_SWF_RLS_RULE occurred (program: CL_SWF_RLS_CONDITION==========CP, include:
CL_SWF_RLS_CONDITION==========CM00Q, line: 160).
Payload problem check these solved threads:
Error
Error in Receiver Determination
regards,
Abhishek

Inbound interface found more than once for outbound interface

Hello everybody,
i have a simple problem.
I build a interface with XI3.0
File to idoc
for each file i need crate 2 idoc.
It's not a problem when Idoc type is different, but in my case i need crate 2 idoc of same type but with a different mapping.
so when i upload the file i have this error:
Inbound interface found more than once for outbound interface
how can i solve this problem? can i force this step?
i thought to create a different idoc type or create the 2 idoc in same mapping , but there is not my favourite solution because in case of error , both idoc will be not created.
any suggestion?
thanks in advance
alex

Hi,
Instead of exporting and changing the occurrence as suggested by Ravi,
use the same Idoc twice in mapping as well as Interface mapping.
Coming to ID part, do every thing as usual.
The only thing to note is instead of using normal Interface determination, use extended Interface Determination.
This will solve your problem. The error will not come again. I'm sure.
Try out and update the thread.
Regards,
Jeevan.

XML message error "No inbound interface found "

Hi,
I have inbound file adapter and mine is standalone XI box,
and idoc outbound adapter, when i start the file adapter im getting the folloing error message in SXMB_MONI .
Error when determining inbound interface. No inbound interface found for sender XI1 and outbound interface FILE2IDOC.FILEINBOUND
pls help me.
thankx

The message is telling you the exact problem - you do not have a receiver identification configured in the Integration Directory for this combination of inbound interface, namespace, and business system. Make sure your file adapter is configured to send with the correct outbound interface/interface namespace.
HTH,
Paul Medaille

Unable to find an inbound interface

Hi masters,
I have an error in sxmb_moni. I get 'Unable to find an inbound interface' everytime i click on the red flag. How can I remedy this problem. thanks!!!

>
Ignatius - Xavier Bazar wrote:
> Hi masters,
> I have an error in sxmb_moni. I get 'Unable to find an inbound interface' everytime i click on the red flag. How can I remedy this problem. thanks!!!
Hi,
1. Check the Inbound message payload in sxmb_moni.
2. If your payload is invalid, it wont be displayed in moni. So check the msg content in RWB- Message Monitoring.
3. Let me know if you are using condition in the Reciever Determination.
Regards,
Chandra

File name with latest time stamp for inbound interface

Hi experts,
I have a requirement to develop an inbound interface in which I need to fetch the all files from the physical directory, and then retrieve the one with the latest timestamp. I found out the FM 'SUBST_GET_FILE_LIST', but this FM does not gives me the timestamp.
Is there any other FM/table through which this can be achieved?
Thanks,
Mohit.

Can you please try with these functionmodules???
1)ITS_DIRECTORY_LIST_FILES
2)CL_GUI_FRONTEND_SERVICES=>DIRECTORY_LIST_FILES

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.

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

Execution of Inbound Interfaces in EOIO for separate messages

Hello XI Experts
We have a proxy to jdbc scenario. The rquirement is like we have to delete all the data from the oracle table, insert the data records into the table,and call a stored procedure from xi which will be done sequentially. We will be sending the message in chunks of 10,000 records from the source i.e from the proxy i.e there will be different messages with unique messageids creted , directed to the receiver. we have thought of the following design to execute the messages in EOIO.There will be 3 inbound interfaces DeleteDataMsg,InsertDataMsg(0 to n), CallStoredProcMsg and three different mapings corresponding to the inbound interfaces with different condition rules.There will be always one outbound interface which will be triggered from proxy .
Is our design correct to implement the requirement?
Thanks & Regards
Sabyasachi

Hi all.
After taking some hints from this thread, we have found out that the problem lied some where in the installation part of PI.
We've set up a basic script, local and not remote, and still the system would not execute that command.
The RWB logs showed successful processing but the Application Server logs were full of errors and stack traces regarding the execution of any command. A support note was raised with SAP support in order to trace these errors.
I'm therefore closing this question as the original question is not related with remote scripting.
Thanks all for your help.
Best regards,
Romeu

"No Objects found" in Interface Mapping

Hi,
I am working on a simple BPM synchronous scenario as follows
File>XI>RFC (request)
RFC (Response)>XI>File
I have done almost everything fine, but while configuring the Receiver determination, I am able to choose the Inbound interfcae, but when I try to select the "Interface Mapping" for the same inbound interface,
it says "No Objects found".
Can anybody help me out in this regard?
I would very much appreciate your help in this regard.
Thanks in advance.
Regards,
Rambabu

Hi Shravan,
I have resolved the issue. In fact there is no mistake done in Repository. In Configuration, I haven't selected the appropriate service, because of this, I wasn't able to see the objects.
Thanks & Regards,
Rambabu

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

Error. in WS Navigator - no endpoints found for interface

Dear Friends,
I have created a new Enterprise Service Interface and implemented in ABAP. After the implementation I used SOAMANAGER to create the endpoint and publish the service using WSPUBLISH to Service Registry. When I tested this service from SOA Management application(SOAMANAGER), the endpoint is working very good, but when I am testing this service from Service Registry, it is now showing any endpoint in the 'Enter Input Parameters' Step. Also when I am trying to search the Service by using 'Search by Logical Destination', it shows the Service and when I select it, it shows an error message, "no endpoints found for interface (<namespace>/document)<Service Interface Name>_Document".
If some one knows about this issue, please advice me to do next steps.
Also I am planning to call this service from Visual Composer, I have configured the two logical destinations over there, also the service registry, even though, when i am searching the service, it shows an error like "Could not complete search".
Please advice me for the above issue also.
Thanks in advance
Vipindas

Hi,
If you have configured and tested from SOAMANAGER (which opens WSnavigator) then it is configured correctly. May be you are using wrong WSDL address.
Copy url of wsdl from SOAMANGER test screen and use it directly in WSnavigator for testing.
Regarding publishing of service WSPUBLISH should be able to publish correct service into service registry, but if for any reason it is not working then you can "publish" it directly from service registry by using publish option and provide url of wsdl from above option.
If for any reason VC is unable to search service registry then create destination template for your every service by providing WSDL and use it in VC.
Regards,
Gourav

Inbound Interface error

Hi, I have configured everything as it should be in XI and I get the message into sxmb_moni but it is redflaged and the error message is "Unable to find inbound interface". I have the Inbound message in Interface Mapping so I don't know what the problem is...do you?
Thanks

Hi,
But I have like 20 different solutions...how can I in the testconfiguration specify which solution I want to test? is that possible? - See for one sender system and one sender interface you can have only one reciver determination, in that you can add as many recivers as you want........but still the configuration test tool can be invoked by just specifying your sender system and sender interface and if you keep receiver system blank, then it will be executed for all reciver systems.............then you can see for which scenario it is erroring.
Regards,
Rajeev Gupta

Several inbound interfaces in intagrated configuration

Hi all,
I want to use an intagrated cnfiguration object for scenario with several inbound interfaces on a receiver side. As for now, I have a usual condition-based interface determination for my receiver system. I've studied all features of "Revceiver Interfaces" tab in IC object as well as corresponding documentation, but found no way to use 2-3 inbound interfaces with conditions for same receiver.
So the question is: how can we use IC object to have several interfaces on receiver system? I'm talking not about message split, since it's impossible for IC, but about interface determination based on message content.
Thanks!
Dmitriy

Hello
So the question is: how can we use IC object to have several interfaces on receiver system? I'm talking not about message split, since it's impossible for IC, but about interface determination based on message content.
Yes, it is possible to use several interfaces on a receiver system. The key here is to group your message types/ed/wsdl under a single outbound interface. You can do this by:
1.) In your outbound service interface, use Stateless as your interface pattern
2.) Then under the operations tab, add as many operations as you need. For example, operation1 uses mestype, operation2 uses xsd, and operation 3 uses wsdl and so on...
3.) Configure your inbound service interface, you can separate them or group them as you like (it depends if they will be using different comm channels) For example, operation 1 can use inbound service interface 1, operations 2 and 3 can use inbound service interface 2
4.) Configure operation mappings (per operation).
5.) After cofiguring your comm channels, create the integrated configuration
6.) Make sure you have a value under the Select Component Version of Sender Interface.
7.) Your created operation mappings will appear under the receiver interfaces
8.) And under outbound processing, there will appear the inbound service interfaces
I hope I have explained this clearly.
Regards,
Mark
Edited by: Mark Dihiansan on Aug 23, 2011 9:15 AM

Unable found inbound interface

Similar Messages

Maybe you are looking for