topic Re: Batch-input: debugging tip in Application Development and Automation Discussions

Batch-input: debugging tip

yes_sapteam — Tue, 01 Feb 2011 07:14:39 GMT

Hi All.

I'm looking for a way for better debugging of a Batch-input session.

Usually, to debug a Batch-input problem, you have to run it in Mode=A, but that means you are going through all the screens until you reach the problematic one.

I'm looking for a way to control the Batch-input, so I can tell it when to stop the background processing and switch to foreground.

Of course, I can always change the BDCDATA table in debug, just before I send it to the CALL TRANSACTION, to have an error I can recover from (like setting wrong OK code for a certain screen), but I'm looking for a better way.

Regards.

Ayal Telem.

Re: Batch-input: debugging tip

yes_sapteam — Tue, 01 Feb 2011 09:01:07 GMT

Hi.

This is the way I found to set a "break-point" in a Batch-input:

First you need to know which screen causes the problem.

Than, at the loop which fills the BDCDATA with the desired screen's details, insert a new record to BDCDATA and set field "FNAM" with any text you want.

This would stops the Batch-input with error "Field <any text> does not exist for screen...".

After the Batch-input stops at your error, type "/BDA" at the session's Command-line, to switch to Foreground processing, and hit Enter to resume in Mode=A.

NOTE: Make sure you are in Mode=E, so the Batch-input stops at your error.

Enjoy.

Ayal Telem.