Documentation View

We are hiring and constantly growing! Have a look through our vacancies to find the right role for you!

ABAPCALL_TRANSACTION - CALL TRANSACTION

ABAPCALL_TRANSACTION - CALL TRANSACTION

General Material Data   BAL Application Log Documentation  
This documentation is copyright by SAP AG.
SAP E-Book

CALL TRANSACTION

Short Reference



Simple transaction call

1. CALL TRANSACTION ta WITH$|WITHOUT AUTHORITY-CHECK $[AND SKIP FIRST SCREEN$].

Transaction call using batch 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 the data object ta. The calling program and its data are preserved. After the transaction call, the program execution of the calling program is resumed after the statement CALL TRANSACTION. The data object ta must be character-like, flat and contain the transaction code in uppercase letters. The following can be specified for ta:

  • Literal or constant
If the data object ta is specified as a text field literal or as a constant, it is evaluated as a static specification by tools such as the extended program check or the where-used list.
  • Variable
If the data object ta is specified as a variable, it is specified only dynamically, and the content is not evaluated statically.

When the statement is executed, ta is not evaluated until runtime in both cases. If the transaction specified in ta is not found, a uncatchable exception is raised.

  • In the first variant, the display of the initial dynpro can be suppressed.

In both variants, an authorization check can be performed for the called transaction.

When the transaction is called, the ABAP program linked to the transaction code is loaded in a new internal session of the current call sequence. The session of the calling program and the current SAP LUW are retained. The called program runs in its own SAP LUW.

  • If the called transaction is a dialog transaction, the event LOAD-OF-PROGRAM is raised after the ABAP program is loaded and the dynpro defined as the initial dynpro of the transaction is called. The initial dynpro is the first dynpro of a dynpro sequence. The transaction is finished when the dynpro sequence is ended by encountering the next dynpro with dynpro number 0 or when the program is exited using the statement LEAVE PROGRAM.
  • If the called transaction is an OO transaction, then, after all programs other than class pools are loaded, the event LOAD-OF-PROGRAM is raised and the method linked to the transaction code is called. If the method is an instance method, an object of the corresponding class is generated implicitly and referenced by the runtime framework. The transaction is finished when the method is finished or when the program is exited using the statement LEAVE PROGRAM.

Notes

  • The number of internal sessions in a call sequence is restricted to nine. If this is exceeded by CALL TRANSACTION, the program is terminated and the entire call sequence is deleted. See Dynamic Calls.

Example

Call of the transaction DEMO_TRANSACTION in the executable example program DEMO_CALL_TRANSACTION_SPA_GPA.

Transaction Call - Examples

Exceptions

Catchable Exceptions

CX_SY_AUTHORIZATION_ERROR

  • Cause: No authorization for this transaction.
    Runtime Error: CALL_TRANSACTION_NO_AUTH

Non-Catchable Exceptions

  • Cause: Transaction not found.
    Runtime Error: CALL_TRANSACTION_NOT_FOUND
  • Cause: Transaction is an area menu and cannot be called.
    Runtime Error: CALL_TRANSACTION_IS_MENU
  • Cause: Transaction is locked.
    Runtime Error: CALL_TRANSACTION_LOCKED
  • Cause: Error in internal memory management.
    Runtime Error: CALL_TRANSACTION_MSG_NO_PAGING
  • Cause: Recursive call of a transaction using the addition USING.
    Runtime Error: CALL_TRANSACTION_USING_NESTED





BAL_S_LOG - Application Log: Log header data   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 9932 Date: 20221203 Time: 162207     sap01-206 ( 122 ms )