on 11-28-2007 3:35 PM
Hello,
I am trying to send file to idoc. I get the following error.
Trace level="3" type="T">Persisting message Status = 001</Trace>
<Trace level="3" type="T">Message version 000</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface MI_Material_Async_Out_9*</Trace>
<Trace level="1" type="T">select interface namespace http://dsouza.com</Trace>;
<Trace level="1" type="T">no interface found</Trace>
<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 interface found</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>
- <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
<Trace level="3" type="T">Trace object available again now. OK.</Trace>
I have done the following.
1. CPA Cache refresh and all available cache refresh.
2. Test configuration - with payload and everything is green checked.
I have substantial time in searching sdn and unable to figure out the problem. Could you please help me.
Thank you.
William
Hi,
Can you check you interface name once(As it is case sensitive)
fill the idoc in interface name.
it will work unless follow the below links
Troubleshooting File-to-IDOC Scenario in XI.
/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
Also have a look on this
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters - IDoc to File
file to idoc
**Reward points if useful*
Refards,
Sumit
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you all,
MIchal's blog helped to resolve the problem.
So I have completed RFC. FILE, IDOC inbound and outbound.
Onto ABAP proxy. I will be back.
Warm regards
William
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi WILLIAM DSOUZA ,
In our production support we face same issue frequently, follow these steps which we follow to trace the error and solve that:-
1) In transaction SXMB_MONI in the very right of your message select your message then right click and copy all details of your message on a notepad
2) go to integration directory , click on the search button situated in the above left pan, then in the search window in the drop down meenu select interface determination, as you will select interface determination then in the bottom down window fillup the entries like sender service interface and receiver service and click on the button find
it will search your receiver determination click on the interface determination a new window will open, there you can find in the interface determination that is any condition? check that condition in your message payload and you will get the eroor
generally found errors in this case are as follows
a)when you will fill sender and receiver details in the receiver determination serach window then search comes with result that "No Interface found"
in that case you remove the receiver details and again search with only sender details then you will find what is the receiver service configured for this sender service. in case different receiver service is configured for this sender match it with your configured scenario
b) second error comes when you have given some condition on any tag for receiver determination and your payload is not satisfying that condition then it will give you no receiver error. then edit your payload and restart it again (for quality of service EO or EOIO)
Hope it may solve your problem
Thanks
Sandeep sharma
PS: if helpful reward points
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Sumit,
The last thread does not work. Could you please send the correct link.
thank you
William
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Are u using the IDoc as the message interface or u have created a new inbound message interface for Idoc? Please use the IDoc name direclty.
Regards,
Prateek
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello William,
Use the IDoc as the interface instead of creating MI_Material_Async_Out_9 interface and attaching the IDoc into it..
Also refresh IDX2.
regards
Mustafa
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
91 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.