Skip to content

ABAP Keyword Documentation →  ABAP - Reference →  Calling and leaving program units →  Calling Programs →  Calling Transactions →  CALL TRANSACTION 

CALL TRANSACTION - USING

Short Reference

Other versions: 7.31 | 7.40 | 7.54

Syntax


CALL TRANSACTION ta WITH|WITHOUT AUTHORITY-CHECK 
                    USING bdc_tab { {[MODE mode][UPDATE upd]}
                                  |  [OPTIONS FROM opt] }
                                     [MESSAGES INTO itab].

Extras

1. ... MODE mode

2. ... UPDATE upd
3. ... OPTIONS FROM opt
4. ... MESSAGES INTO itab

Effect

In the variant with the addition USING, the transaction is executed using a batch input table. The transaction is called as described under CALL TRANSACTION. The additions WITH|WITHOUT AUTHORITY-CHECK are used to control the authorization check.

bdc_tab expects an internal table with row type BDCDATA from ABAP Dictionary.. The additions control processing.

When a transaction with addition USING is called, the system field sy-binpt is set to value "X" in the called program; while this transaction is running, no other transaction can be called with this addition.

A batch input table bdc_tab is the program's internal representation of a subset of a batch input session and must be filled accordingly. The structure BDCDATA has the components shown in the table below.

Component Meaning
PROGRAM Name of the program of the called transaction
DYNPRO Number of the dynpro to be processed
DYNBEGIN Flag for the beginning of a new dynpro (possible values are "X" and " ")
FNAM Name of a dynpro field to be filled or batch input control statement, for example to position the cursor
FVAL Value to be passed to the dynpro field or to the control statement

Using the content of the internal table bdc_tab, any number of screens of the called transaction can be provided with input and user actions.

System Fields

sy-subrc Meaning
0 The processing of the called transaction was successful.
< 1000 Error in the called transaction. If a message was sent within the transaction, it can be received using the addition MESSAGES.
1001 Processing error.


Notes

  • Calling a transaction using a batch input table is not the same as executing batch input sessions in batch input. There is no exact dividing line between the two, however, since batch input-based frameworks, such as CATT and batch input management, sometimes also execute the statement CALL TRANSACTION USING internally. In this way, they can use certain options not available in genuine batch input.
  • The control options for a batch input table include the control options for batch input sessions in real batch input, plus some extra options.

Addition 1

... MODE mode

Effect

The MODE addition determines the processing mode for processing. mode can be specified as a character-like data object, whose content and purpose are shown in the following table. If one of the additions MODE or OPTIONS FROM is not used, the effect is the same as if mode had the content "A".

mode Effect
"A" Processing with screens displayed
"E" Screens displayed only if an error occurs
"N" Processing without screens displayed. If a breakpoint is reached in one of the calledtransactions, processingis terminated with sy-subrc equal to 1001. The field sy-msgtycontains "S", sy-msgid contains "00",sy-msgno contains "344", sy-msgv1 contains "SAPMSSY3", and sy-msgv2 contains "0131".
"P" Processing without screens displayed. If a breakpoint is reached in one of the called transactions, the system branches to the ABAP Debugger.
Others As for "A".

Addition 2

... UPDATE upd

Effect

The UPDATE addition determines the update mode for processing. upd can be specified as a character-like data object, whose content and purpose are shown in the following table. If one of the additions UPDATE or OPTIONS FROM is not used, the effect is the same as if upd had the content "A".

upd Effect
"A" Asynchronous update.Updates of called programs areexecuted in the same way as if the AND WAIT addition was not specified in the COMMIT WORK statement.
"S" Synchronous update. Updates of the called programs are executed in thesame way as if the AND WAIT addition had been specified in the COMMIT WORK statement.
"L" Local updates. Updates of the called program are executed in the sameway as if the SET UPDATE TASK LOCAL statement had been executed in the program.
Others As for "A".


Note

This option is not available for execution of batch input sessions in batch input. Updates are always synchronous.

Addition 3

... OPTIONS FROM opt

Effect

The OPTIONS addition covers the functions of the MODE and UPDATE additions and provides further options for controlling processing of the batch input table. The control parameters are specified in an opt structure of the type CTU_PARAMS from ABAP Dictionary. The CTU_PARAMS structure has the components displayed in the following table:

Component Meaning
DISMODE Processing mode. Values as for the MODE addition.
UPMODE Update mode for processing. Values as for the UPDATE addition.
CATTMODE CATT mode for processing. Whilebatch input is used mostly for data transfer, CATT processes are more complextransactions, since theyare reusable tests. Values: " " (no CATT mode), "N" (CATT without single screen control), "A" (CATT with single screen control).
DEFSIZE Selects whether the screensof the called transaction are displayed in the standard screen size. Values: "X" (standard size), " " (current size).
RACOMMIT Selects whether the COMMIT WORK statement terminates processing or not. Values: " "(COMMIT WORK terminates processing), "X" (COMMIT WORK does not terminate processing).
NOBINPT Selection for the system field sy-binpt. Values: " "(sy-binpt contains "X" in the called transaction), "X"(sy-binpt contains " " in the called transaction).
NOBIEND Selection for the system field sy-binpt. Values: " "(sy-binpt contains "X" after the end of the batch input table data in the called transaction ) "X"(sy-binpt contains " " after the end of the data in the called transaction).

If the OPTIONS FROM addition is not used, the values set by the additions MODE or UPDATE or the standard values specified there "A" apply to DISMODE and UPMODE. The other components are set to the value " ".

Addition 4

... MESSAGES INTO itab

Effect

Using this addition, all the messages sent during batch input processing are saved to an internal table itab of the type BDCMSGCOLL from ABAP Dictionary.

Continue

CALL TRANSACTION - Batch Input Table