topic error tracking in batchinput method in Application Development and Automation Discussions

error tracking in batchinput method

Former Member — Fri, 09 Mar 2007 15:08:05 GMT

hello abapers,

)how to handle errors in call transaction and session , what is the procedure to correct those errors , which technique frequently used .

Re: error tracking in batchinput method

Former Member — Fri, 09 Mar 2007 15:52:16 GMT

Hi,

the better way of handling error's in call transaction, first is to collect the call messages. You should use the statment ...MESSAGES into itab. in the Call Transaction.

Second, you should only care about the errors type 'E'(error) and 'A'(abort) in the messages tab.

Finally, (i'm suposing that we are talking about processs error's and not Abap error's) shoud analize the each of the error's and try to finding the error reason (for example a customizing error's) and after that, run the program again for the bad registrys.

I not sure if this answers your question , not sure i understand the problem...

regards,

Re: error tracking in batchinput method

Former Member — Fri, 09 Mar 2007 15:54:01 GMT

hi Praveen,

Batch Input

Errors occured during Batch input sessions can corrected manually, when we re-process the session from SM35. Also you can analyze the errors from SM35 itself, before you re-process the same session.

1->goto SM35, select the session which resulted in error.

2->choose button Analysis or Log to see the errors

30>choose button Process to re-process the session

and manually enter the faulty values

Call transaction

you have to collect the error messages into an internal table of structure BDCMSGCOLL and output/download the errors so that the end user can know which records are giving error. There is no option to re-process these records directly.

But you can do it in a different way. collect the records which are gives error and generate a session for these records only. Now the user can run the session online and correct the entries.

data itab type table of BDCMSGCOLL
Call transaction 'XK01' MODE 'A'  UPDATE 'S' MESSAGES INTO itab

*mode A = display all screens. (E = errors only, N = no display)

Hope this helps,

Sajan Joseph.