Data Interfaces

The CALL TRANSACTION Statement
© SAP AG
CALL TRANSACTION
USING
MODE
UPDATE
MESSAGES INTO
:
A Display all
E Display only if if there are errors
N Display nothing
:
S Do not continue processing until
update has finished (synchronous)
A Continue processing immediately
As with batch input, you can choose a particular display mode for processing the transaction.
Unlike batch input, you can also specify an update mode. In asynchronous update processes, the called
transaction does not wait until the database updates have been performed, but passes the update to the
update task. In synchronous update processes, it waits until the update has been completed. Although
synchronous update is slower than asynchronous update, it is also more secure because the called
transaction can then report any errors to the calling program. In batch imput, the update mode is always
'S' (synchronous).
The MODE and UPDATE parameters are optional. The default for both is ‘A’ (asynchronous).
The MESSAGES INTO option allows you to store any messages output by the called
transaction in an internal table. The internal table must have the structure BDCMSGCOLL.