Does the problem happen when you
1) do the (initial and only) record with SHDB,
2) or is it when you execute the program generated by SHDB?
For option 1), I think it can't happen, or there is a bug in the sap standard REBDBE (one possibility is that the standard tests for the SHDB mode and works differently from normal use, and there would be a bug in that case). In that case, ask sap support.
If it's with option 2, did you try to do a screen by screen execution? (execution mode "A")
You may also try to change another flag in the launch screen, there is a flag which by default stops the call transaction after the first commit work, sometimes it is a bad option. There is also another flag which allows to make the system believe it should work as in normal use instead of "batch input" mode.
Other possibilities :
- check that you don't have custom code in the standard programs
- check that you have removed all breakpoints when you execute, it may disturb the screen processing when it displays debugger screen ; it may only happen if you use the "old debugger"
Note that business data toolset usually proposes a direct input mode (see sap documentation), but that's far more complex to use than batch input.
Bluesky
