topic Re: FI Inbound IDOC Error.. in Application Development and Automation Discussions

FI Inbound IDOC Error..

Former Member — Tue, 21 Sep 2010 13:28:22 GMT

HI All,

Im trying to trigeer the inbound IDOC from we19 and im not able to post the IDOC. (Using the Standard Idoc Type: FIDCCP02 and message type: FIDCC1) im getting this error (Document or line item does not exist for invoice reference: Message no. F5346).

Please let me know how to solve this issue.

Ashok.

Re: FI Inbound IDOC Error..

brad_bohn — Tue, 21 Sep 2010 13:34:00 GMT

Think about it - Read the long text of the message OR do a where-used one the message and look at the code OR put a breakpoint at the message OR use a watchpoint for debugging. Analyze the condition that's triggering the message and you'll have your answer...

Re: FI Inbound IDOC Error..

Former Member — Tue, 21 Sep 2010 13:36:49 GMT

Hi,

try this way...

even the Idoc returns error it creates a IDOC number...

GO to we02/We05 and enter idoc number and execute , Expand data records and see the red highlighted segment.

and try to pass the values in the segment and re run in BD87 .

Prabhudas

Re: FI Inbound IDOC Error..

Former Member — Tue, 21 Sep 2010 13:51:43 GMT

HI Prabhu,

Im not clear.......the process u r saying...

Ashok.

Re: FI Inbound IDOC Error..

Former Member — Tue, 21 Sep 2010 13:56:15 GMT

Hi,

go to t-code we02/we05 and enter the message type : FIDCC1 and execute.

it will display the Idocs see the Idoc number which is created by you in we19.

and doubdle click on the idoc number ..and see the data records ... in the data records one segemnet is is highlighted with diiferent color because of error.

then go to BD87 and enter the above idoc number and correct the segment data and process by F8.

Prabhudas

Re: FI Inbound IDOC Error..

Former Member — Tue, 21 Sep 2010 13:59:55 GMT

HI ,

I dont have any segment with different color. all are in same color.

Ashok.

Re: FI Inbound IDOC Error..

Former Member — Tue, 21 Sep 2010 18:34:33 GMT

Guys, you can run this a zillion times, using whatever method, but that doesn't fix the error! Read Brad's response. If your input points to document/item that's not in SAP, you're not going to get around that problem.