topic Re: Capturing IDOC Fallout in Application Development and Automation Discussions

Capturing IDOC Fallout

Former Member — Fri, 19 Jul 2013 08:22:04 GMT

Hello All,

I have got a small query / question.

Initially i had posted this quesry in ERP Financials ( http://scn.sap.com/thread/3392882), but was not helpful, then one of my colleuge sugested me that this is mostly related to ABAP, hence have posted it here again.

I have to make to a report , which will give the details of all the Inbound IDOCS, that fall out during the transfer due to invalid cost center, gl etc, or in short due to any mismatch. I did go through few of the threads , searching , if there is any Standard SAP report for the same and also did find out a response. and also a way , where in a mail will also be triggered to a generic mailbox , stating the fallout with reason(s) and at this juncture i also want another report which should capture the IDOC details , reason of fallout and this information must come out as a report on a daily basis, when it is executed.

Kindly suggest if this is possible, the way i am thinking or it cannot be done.

Findings: 1 - No standard report exist to find out fallout IDOCS and its reasons

2 - Standard Report RSEIDOCA can be used as a base to monitor, and even BD*& can be used to reprocess fallout IDOCS

3 - A program can be written to trigger a mail, when fallout occurs (http://scn.sap.com/thread/1034694 )

Questions : 1 - Report / program to capture information from mail(s) , that are triggered due to fall out and present the same as a report on a daily basis when executed.

Outcome : Better tracking of the fallouts and expedite the process on working on them and can also help in reconciliation to the number of mails received for fallouts to that produced in the report.

Thanks in advance,

Jimmy

Re: Capturing IDOC Fallout

Former Member — Fri, 19 Jul 2013 09:10:08 GMT

Hi Jimmy,

There are standard reports for the same.

Transaction WE02 and WE05.

Mention the direction as Inbound and the Message type of your Idoc and status with the error status numbers create a variant and execute the same.

If you are not statisifed with the output ask an ABAPER to enhance these transaction for the desired results.

Regards

Re: Capturing IDOC Fallout

Former Member — Fri, 19 Jul 2013 10:34:47 GMT

Hello Mohammed,

Thanks for the reply !!

Your answer is correct, but what i am looking for is, is there a tab or segment in IDOC which states that,if that if a particular Inbound idoc has failed (reason being anything, like cost center not matching or any data mismatch ), then that reason should be mention in that segment and 2nd i want that the system should trigger a mail, which this reason to a mailbox, 3rd Can a program be written to capture this data from mails and produce a SAP report ?

As far as i know, there will some place where such error(s) due to fails will be popping, so i want to catch this and make some workaround to get my desired report.

I just want to know , whether the way i am thinking is it possible or not

Regards,

Jimmy

Re: Capturing IDOC Fallout

Former Member — Sat, 20 Jul 2013 02:54:50 GMT

Yes Jimmy,

Here it goes for the solution you need.

Create a Z Program.

Read all IDocs from EDIDC table for your message type and have been there for the day

Read Table EDIDS for these selected IDoc for the status code

51 Application document not posted

52 Application document not fully posted

54 Error during formal application check

56 IDoc with errors added

60 Error during syntax check of IDoc (inbound)

61 Processing despite syntax error (inbound)

63 Error passing IDoc to application

65 Error in ALE service

68 Error - no further processing

For the message

Pass STAMID,STAMNO,STAPA1,STAPA2,STAPA3,STAPA4 From EDIDS to function module MESSAGE_PREPARE and you will get the message text.

Regards

Re: Capturing IDOC Fallout

Former Member — Mon, 22 Jul 2013 07:37:25 GMT

Hello Mohammed,

Many a thanks for the help !!!

Regards,

Jimmy