CALL TRANSACTION - bdc_options
Syntax
... { {[MODE mode] [UPDATE upd]}
| [OPTIONS FROM opt] }
[MESSAGES INTO itab] ... .
Extras:
Effect
Control of batch input processing with the USING addition.
Addition 1
... MODE mode
Effect
The MODE addition determines the processing mode for batch input processing. As
mode, you can specify a character-type data object. Its possible content and effect is displayed in the following table. Without use of one of the additions
MODE or
OPTIONS FROM, the effect is the same as if
mode had the content "A".
| mode | Effect |
| "A" | Processing with display of screens |
| "E" | Display of screens only if an error occurs |
| "N" | Processing without display of screens. If a breakpoint is reached in one of the called transactions, processing is terminated with sy-subrc same as 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 display of the screens. If a breakpoint is reached in one of the called transactions, the system branches to the ABAP Debugger. |
| Others | Like "A". |
Addition 2
... UPDATE upd
Effect
The UPDATE addition determines the processing mode for batch input processing. You can specify a character-type object for
upd. Its possible content and its effect are displayed in the following table. Without use of one of the additions
UPDATE or
OPTIONS FROM, 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 in the COMMIT WORK statement the AND WAIT addition was not specified. |
| "S" | Synchronous processing. Updates of the called programs are executed in the same way as if in the COMMIT WORK statement the AND WAIT addition had been specified. |
| "L" | Local update. Updates of the called program are executed in such a way as if the SET UPDATE TASK LOCAL statement had been executed in it. |
| Other | As for "A". |
Note
This option is not available for execution of actual batch input sessions. There the update is always synchronous.
Addition 3
... OPTIONS FROM opt
Effect
The OPTIONS addition covers the functions of the
MODE and
UPDATE additions. It provides further options for controlling batch input processing. The control parameters are specified in an
opt structure of the type CTU_PARAMS from the ABAP Dictionary. The CTU_PARAMS structure has the components displayed in the following table:
| Component | Meaning |
| DISMODE | Processing mode for batch input processing. Values as for the MODE addition. |
| UPMODE | Processing mode for batch input processing. Values as for the UPDATE addition. |
| CATTMODE | CATT mode for batch input processing. CATT means Computer Aided Testtool. While batch input is mostly used for data transfer, CATT processes are to be viewed as 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 | Selection as to whether the screens of the called transaction are displayed in the standard screen size. Values "X" (standard size), " " (current size). |
| RACOMMIT | Selection as to whether the COMMIT WORK statement terminates batch input processing or not. Values: " " (COMMIT WORK terminates processing), "X" ( COMMIT WORK does not terminate processing). |
| NOBINPT | Selection for the symbol field sy-binpt. Values: " " (sy-binpt contains in the called transaction "X"), "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 data in the called transsaction ) "X" (sy-binpt contains " " after the end of the batch input data in the called transaction). |
Without use of the OPTIONS FROM addition,the values set by the additions
MODE or
UPDATE or the standard values specified there apply to DISMODE and UPMODE"A". 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 stored in an internal table
itab of the type BDCMSGCOLL from the ABAP Dictionary.