SAP NetWeaver AS ABAP Release 750, ©Copyright 2016 SAP AG. All rights reserved.
ABAP - Keyword Documentation → ABAP - Reference → Calling and leaving program units → Calling Programs → Calling Transactions → CALL TRANSACTION →
CALL TRANSACTION - USING
Syntax
CALL TRANSACTION ta WITH|WITHOUT AUTHORITY-CHECK
USING bdc_tab { {[MODE mode] [UPDATE upd]}
| [OPTIONS FROM opt] }
[MESSAGES INTO itab].
Additions
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.
In a program, a batch input table bdc_tab is the 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
... MODE mode
Effect
The addition MODE 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 called transactions, processing is terminated with sy-subrc equal to 1001. The field sy-msgty contains "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". |
... UPDATE upd
Effect
The addition UPDATE 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 are executed in the same way as if the addition AND WAIT were not specified in the statement COMMIT WORK. |
| "S" | Synchronous update. Updates of the called programs are executed in the same way as if the addition AND WAIT were specified in the statement COMMIT WORK. |
| "L" | Local updates. Updates of the called program are executed in the same way as if the statement SET UPDATE TASK LOCAL were 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.
... OPTIONS FROM opt
Effect
The addition OPTIONS 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 addition MODE. |
| UPMODE | Update mode for processing. Values as for the addition UPDATE. |
| CATTMODE | CATT mode for processing. While batch input is used mostly for data transfer, CATT processes are more complex transactions, since they are reusable tests. Values: " " (no CATT mode), "N" (CATT without single screen control), "A" (CATT with single screen control). |
| DEFSIZE | Selects whether the screens of the called transaction are displayed in the standard screen size. Values: "X" (standard size), " " (current size). |
| RACOMMIT | Specifies whether the statement COMMIT WORK 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 addition OPTIONS FROM 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 " ".
... 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.