CALL TRANSACTION statement is used for calling and executing another program using its transaction code inside an ABAP program. The transaction code for that program is used for calling. The current data of the program will kept and the called transaction will be processed in another internal session. After the execution of called transaction, the current program will continue its processing from the point where the call occurred.
The Syntax for CALL TRANSACTION
CALL TRANSACTION <tcod>
[AND SKIP FIRST SCREEN]
[USING <itab>]
[MODE <mode>]
[UPDATE <f>]
[MESSAGES INTO <itab>].
AND SKIP FIRST SCREEN: This addition will suppress the display of initial screen of the called program.
USING <itab>: This addition specified the internal table name which contains the data to be passed to the called program. Normally used for passing BDCDATA for batch input processing.
MODE <mode>: This addition specified the display mode.The display modes are
- ‘A’: Display screen
- ‘E’: Display screen only if an error occurs
- ‘N’: No display
UPDATE <f>: This addition specifies the update mode. The updates modes are
- ‘A’: Asynchronous update
- ‘S’: Synchronous update
MESSAGES INTO <itab>: This addition specifies the internal table where the returned messages should store.
The main runtime errors are
- CALL_TRANSACTION_NOT_FOUND
- CALL_TRANSACTION_IS_MENU
- CALL_TRANSACTION_LOCKED
- CALL_TRANSACTION_MSG_NO_PAGING
- CALL_TRANSACTION_USING_NESTED
Also Read : View Other ABAP Keywords & Syntax -> ABAP Transaction codes