This section explains how to correct errors in faulty transactions in a
session.
Prerequisites
Start the batch input management tool: Select
System �
Service �
Batch input
� Sessions.
Alternate: Enter transaction SM35. Both paths take you to the session overview
of the batch input system. transaction SM35.
Procedure
When a session is run in background-processing
mode, the system marks transactions that contain errors as incorrect. All other
transactions in the session are completed. The session itself is kept in the
session queue in the Errors section of the list.
A transaction contains an error if it generates
an error message of type E (error) or type A (abnormal termination). Messages of
other types are ignored and do not affect the execution of a session.
You can correct and re-execute the incorrect
transactions in an "Errors" session. There are two ways to do so:
Re-run the session in display-all or error-display mode. These modes
offer the following advantages:
- The
system skips transactions that were successfully completed. Only incorrect
transactions or transactions that have not been executed are run.
- You
can change inputs and add missing screens interactively as incorrect
transactions run. The system logs all such changes.
The following topic provides more information
on using display-all mode or error-display mode to correct a transaction.
As an alternative, you can analyze the session to determine what the
error was. With the analysis displays, you can check the screen that
contained the error and the values that were entered in it. You can then
correct the program that generated the session and regenerate the session.
You must ensure that the new session does not
include transactions that were successfully completed. Otherwise, the
updates made by the transactions will be performed again.
Using Display-All Mode
When you use display-all mode to re-start a
session that contains an incorrect transaction, the system skips to the first
screen of the incorrect transaction. Completed transactions are not re-executed.
To correct a transaction, you can:
use the
ENTER
key to step through the screens recorded in the
session
As in normal operation, pressing the
ENTER
key starts a dialog step. As long as you simply press
ENTER ,
the system processes the screens and data recorded in the session.
change or add values in any screen
When you press
ENTER ,
the system processes the data as altered by you. All of your changes are
logged; you can review them at a later date if required.
branch off from the transaction flow recorded in the session
You can use any function that you wish within
the transaction that is currently running. You can, for example, branch off
to enter data on a screen that was omitted from the session.
To resume executing the session, return to
the screen that was expected by the session.
It holds the data for the screen recorded in
the session until you have returned to that screen. It then resumes normal
execution of the session.
Interrupting a Session
You can interrupt the interactive execution of a session by entering the
/bend OK code on any screen. /bend terminates the transaction
currently being executed in the session and marks the transaction with the
status Incorrect. The session is kept in the queue and is displayed in
the Errors section of the list. Changes made by the interrupted
transaction are rolled back as long as the transaction uses only the R/3 update
facility. Direct database changes made by the transaction are not rolled back.
You can use /bend when testing sessions. For example, you may wish to run the
first transactions of a large session in display-all mode to make sure that the
session has been generated correctly.
If the transactions are correct, you can then terminate the run with /bend
and then submit the session for background execution. The transactions that have
already been run will not be run again.
Restarting a Transaction
You can restart processing of a transaction by
entering the /bbeg OK code on any screen. /bbeg terminates the
transaction that is currently being processed and then restarts the transaction
fresh, as it is recorded in the batch input session. Any changes made by the
transaction are rolled back, as long as they were made only by way of the R/3
update facility. Changes made directly to the database are not rolled back.
Deleting a Transaction
You can delete a transaction from a session during interactive execution by
entering the /bdel OK code. The transaction is removed from the session.
The deleted transaction cannot be run even if you restart the session, and you
cannot take back the deletion.
The transaction is, however, available for analysis if the session was
generated with the KEEP option set. The transaction is marked with the status
Deleted in the analysis display. The deletion also is recorded in the log
generated by the session.
Result
Correcting and re-running faulty transactions in a batch input session lets
you finish the processing of a session and complete the data transfer.
