If a system problem occurs while a session is being generated or is being
run, the session is terminated abnormally. Typical causes of an abnormal
termination might include shutdown of the R/3 System while a session is running
or termination of a SAPGUI presentation process while a session is being run
In the session queue, a session that was terminated while it was being
generated remains in the Being generated tab in the overview. A session
that was terminated while it was running remains in the Active tab.
To prevent such sessions for remaining in these statuses indefinitely, you
must intervene. You must release and either restart or delete and recreate these
Start the batch input management tool: Select
Alternate: Enter transaction SM35. Both paths take you to the session overview
of the batch input system. transaction SM35.
You can recognize that a session has terminated abnormally because the status
of the session does not change. If, for example, you find a session that was run
the previous night still in the Active list, then it is likely that the
session was interrupted.
If a session was to run in the background, you can check the status of the
session’s job in the background processing system. If the session was aborted,
then the background job log contains the reason for the abnormal termination.
Before you can restart (or start) a session that terminated abnormally, you
must release it. Releasing the aborted session sets its status to Being
processed. Reset the status by marking the session or sessions and selecting
Release in the toolbar.
You can safely restart a session that was interrupted while it was being run.
When you restart the session, all transactions that were successfully completed
before the problem occurred will be skipped. The transaction that was executing
when the problem occurred will be re-executed.
Release an active session only if you are sure that it has been
interrupted and is no longer running.. Sessions also have the status
Active while they are running.
Restarting after abnormal termination during generation: You can start a
session that was interrupted while it was being generated. The session is
guaranteed to contain only complete transactions and to be runnable.
However, there is no guarantee that the session contains all of the
transactions that were to be included in it. You may therefore wish to
delete and regenerate such a session.