SAP NetWeaver AS ABAP Release 740, ©Copyright 2014 SAP AG. All rights reserved.
ABAP Keyword Documentation → ABAP − Reference → Calling and leaving program units → Calling ABAP Programs → Calling Transactions →Syntax Forms
Simple transaction call
1. CALL TRANSACTION ta
WITH|WITHOUT AUTHORITY-CHECK [AND SKIP FIRST SCREEN].
Transaction call usingbatch input table
2. CALL TRANSACTION ta WITH|WITHOUT AUTHORITY-CHECK
USING bdc_tab { {[MODE mode][UPDATE upd]}
| [OPTIONS FROM opt] }
[MESSAGES INTO itab].
Effect
The statement CALL TRANSACTION calls the transaction whose transaction code is contained in data object ta. The calling program and its data are retained. After the end of the transaction call, program execution of the calling program resumes after the CALL TRANSACTION statement.
The data object ta must be character-like, flat and contain the transaction code in uppercase letters. If the transaction specified in ta cannot be found, a non-handleable exception is raised.
In both variants, an authorization check can be performed on the called transaction.
When the transaction is called, the ABAP program associated with the transaction code is loaded in a new internal session. The session of the calling program and the current SAP LUW are retained. The called program runs in its own SAP LUW.
Notes
Security Note
If used wrongly, dynamic calls of program units can present a serious security risk. Names of program
units that are passed to a program from the outside must be checked thoroughly before being used in dynamic calls. The system class CL_ABAP_DYN_PRG, for example, can be used to do this. See
Dynamic Calls.
Catchable Exceptions
CX_SY_AUTHORIZATION_ERROR
Non-Catchable Exceptions