Description

When running a script, you get this message in the log column: "No batch input data for screen..."

Cause

This message can appear for many different transaction codes. It will come up in the following scenarios:

Pop up Screen

If the script encounters an SAP screen that it either does not have any information , or didn't expect at that point in the run.

Example

It indicates that a popup or dialog box that came up during execution and so the script has gotten off track.

New Screen

If a new screen is popping up for the current record that didn't exist for the record that was recorded (different screen flows for different data).

Example

If we populate a field on one screen for a particular data/record, a new screen might appear with fields that must be filled. As this new screen sequence was not recorded, the script returns the error.

Missing / Skipped Screen

If the script has a screen recorded that does not appear for certain data.

Example

The recording is done with a set of screen flows--but for particular data, one of the screens is not displayed by SAP. The script will navigate through that screen, which is not actually displayed by SAP, and return the error.

Solution

If you see this error, try running in step-by-step mode, and stop on each screen to see if you can identify the issue.

You can also record the scenario that is generating the error and compare it with the original script. This should illustrate what is processing differently so that you can then edit / modify the existing script to accumulate the new scenario.

Different data may have different (SAP screen) flow sequences.