topic Re: WRONG IDOC in Application Development and Automation Discussions

WRONG IDOC

walkerist79 — Fri, 13 May 2022 06:51:58 GMT

ASD

Re: WRONG IDOC

Jeansy — Fri, 13 May 2022 07:01:20 GMT

Can you please give us some more details? Which message type process are you using?

For each message type/basic type there is am inbound function module behind which can be debugged, also using WE19.

Kind regards
Jens

Re: WRONG IDOC

walkerist79 — Fri, 13 May 2022 07:18:12 GMT

jzaehringer not sure with the message type but details given were only it is an inbound document.

Re: WRONG IDOC

Jeansy — Fri, 13 May 2022 07:58:14 GMT

walkerist but how do you test this scenario in this case? Using WE19 it would be easy to copy an existing IDoc (or to fill one from scratch) and then you are able to debug it.

But how should we help w/o having the main relevant information?

Re: WRONG IDOC

walkerist79 — Fri, 13 May 2022 08:41:04 GMT

jzaehringer iDOC document number is also given. I need to know where's the source field of material.

Re: WRONG IDOC

Jeansy — Fri, 13 May 2022 08:47:02 GMT

walkerist But if you have the IDoc number for testing, then you could also tell us the message type?

Re: WRONG IDOC

walkerist79 — Fri, 13 May 2022 09:13:59 GMT

jzaehringer Status is 53, Message Type is ORDERS. Partner type is KU.

Re: WRONG IDOC

Sandra_Rossi — Sat, 14 May 2022 17:22:25 GMT

Starting the debugger is easy, but finding the reason why a given logic is applied is much more difficult.

I think only people with a lot of experience in debug can do this, but only if they connect to your system. They could advise if you give more information.

Otherwise, use an ABAP trace (SAT) with all the details (without "aggregation") and try to locate the block of subroutines or methods whose names indicate they are about fetching the materials...