call transaction

7/29/2019 Call Transaction

1/3

CALL TRANSACTION - bdc_options

Syntax

... { {[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

Control of batch input processing with the USING addition.

Addition 1

... MODE mode

Effect

TheMODE addition determines the processing mode for batch input processing.

Asmode, you can specify a character-type data object. Its possible content andeffect is displayed in the following table. Without use of one of the

additionsMODE orOPTIONS FROM, the effect is the same as ifmode had thecontent "A".

mode Effect"A" Processing with display ofscreens

"E" Display of screens only if an error occurs

"N"

Processing without display of screens. If a breakpoint is reached in one of the calledtransactions,

processing is terminated with sy-subrc same as 1001. The field sy-msgty contains "S", sy-

msgidcontains "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.

OthersLike "A".
http://help.sap.com/abapdocu_70/en/ABAPCALL_TRANSACTION_BDC_OPTIONS.htm#&ABAP_ADDITION_1@1@http://help.sap.com/abapdocu_70/en/ABAPCALL_TRANSACTION_BDC_OPTIONS.htm#&ABAP_ADDITION_1@1@http://help.sap.com/abapdocu_70/en/ABAPCALL_TRANSACTION_BDC_OPTIONS.htm#&ABAP_ADDITION_1@1@http://help.sap.com/abapdocu_70/en/ABAPCALL_TRANSACTION_BDC_OPTIONS.htm#&ABAP_ADDITION_2@2@http://help.sap.com/abapdocu_70/en/ABAPCALL_TRANSACTION_BDC_OPTIONS.htm#&ABAP_ADDITION_2@2@http://help.sap.com/abapdocu_70/en/ABAPCALL_TRANSACTION_BDC_OPTIONS.htm#&ABAP_ADDITION_2@2@http://help.sap.com/abapdocu_70/en/ABAPCALL_TRANSACTION_BDC_OPTIONS.htm#&ABAP_ADDITION_3@3@http://help.sap.com/abapdocu_70/en/ABAPCALL_TRANSACTION_BDC_OPTIONS.htm#&ABAP_ADDITION_3@3@http://help.sap.com/abapdocu_70/en/ABAPCALL_TRANSACTION_BDC_OPTIONS.htm#&ABAP_ADDITION_3@3@http://help.sap.com/abapdocu_70/en/ABAPCALL_TRANSACTION_BDC_OPTIONS.htm#&ABAP_ADDITION_4@4@http://help.sap.com/abapdocu_70/en/ABAPCALL_TRANSACTION_BDC_OPTIONS.htm#&ABAP_ADDITION_4@4@http://help.sap.com/abapdocu_70/en/ABAPCALL_TRANSACTION_BDC_OPTIONS.htm#&ABAP_ADDITION_4@4@http://help.sap.com/abapdocu_70/en/ABENSCREEN_GLOSRY.htmhttp://help.sap.com/abapdocu_70/en/ABENSCREEN_GLOSRY.htmhttp://help.sap.com/abapdocu_70/en/ABENSCREEN_GLOSRY.htmhttp://help.sap.com/abapdocu_70/en/ABENTRANSACTION_GLOSRY.htmhttp://help.sap.com/abapdocu_70/en/ABENTRANSACTION_GLOSRY.htmhttp://help.sap.com/abapdocu_70/en/ABENTRANSACTION_GLOSRY.htmhttp://help.sap.com/abapdocu_70/en/ABENTRANSACTION_GLOSRY.htmhttp://help.sap.com/abapdocu_70/en/ABENSCREEN_GLOSRY.htmhttp://help.sap.com/abapdocu_70/en/ABAPCALL_TRANSACTION_BDC_OPTIONS.htm#&ABAP_ADDITION_4@4@http://help.sap.com/abapdocu_70/en/ABAPCALL_TRANSACTION_BDC_OPTIONS.htm#&ABAP_ADDITION_3@3@http://help.sap.com/abapdocu_70/en/ABAPCALL_TRANSACTION_BDC_OPTIONS.htm#&ABAP_ADDITION_2@2@http://help.sap.com/abapdocu_70/en/ABAPCALL_TRANSACTION_BDC_OPTIONS.htm#&ABAP_ADDITION_1@1@


2/3

Addition 2

... UPDATE upd

Effect

The UPDATE addition determines the processing mode for batch input

processing. You can specify a character-type object forupd. Its possible

content and its effect are displayed in the following table. Without use of one

of the additions UPDATE orOPTIONS FROM, the effect is the same as ifupdhad thecontent "A".

upd Effect

"A"Asynchronous update.Updatesof called programs are executed in the same way as if in

theCOMMIT WORKstatement theAND WAIT addition was not specified.

"S" Synchronous processing. Updates of the called programs are executed in the same way as if inthe COMMIT WORKstatement theAND WAIT addition had been specified.

"L"Local update. Updates of the called program are executed in such a way as if theSET UPDATE

TASK LOCALstatement had been executed in it.

OtherAs for "A".

Note

This option is not available for execution of actual batch input sessions. Therethe update is always synchronous.

Addition 3

... OPTIONS FROM opt

Effect

The OPTIONS addition covers the functions of theMODE 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 fromthe ABAP Dictionary. The CTU_PARAMS structure has the componentsdisplayed in the following table:

Component Meaning

DISMODE Processing mode for batch input processing. Values as for theMODE 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. Whilebatch input is mostly used for data transfer, CATT processes are to be viewed as more

complextransactions, 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 thescreensof the called transaction are displayed in the standard
http://help.sap.com/abapdocu_70/en/ABENUPDATE_GLOSRY.htmhttp://help.sap.com/abapdocu_70/en/ABENUPDATE_GLOSRY.htmhttp://help.sap.com/abapdocu_70/en/ABENUPDATE_GLOSRY.htmhttp://help.sap.com/abapdocu_70/en/ABAPCOMMIT.htmhttp://help.sap.com/abapdocu_70/en/ABAPCOMMIT.htmhttp://help.sap.com/abapdocu_70/en/ABAPCOMMIT.htmhttp://help.sap.com/abapdocu_70/en/ABAPSET_UPDATE_TASK_LOCAL.htmhttp://help.sap.com/abapdocu_70/en/ABAPSET_UPDATE_TASK_LOCAL.htmhttp://help.sap.com/abapdocu_70/en/ABAPSET_UPDATE_TASK_LOCAL.htmhttp://help.sap.com/abapdocu_70/en/ABAPSET_UPDATE_TASK_LOCAL.htmhttp://help.sap.com/abapdocu_70/en/ABENTRANSACTION_GLOSRY.htmhttp://help.sap.com/abapdocu_70/en/ABENTRANSACTION_GLOSRY.htmhttp://help.sap.com/abapdocu_70/en/ABENTRANSACTION_GLOSRY.htmhttp://help.sap.com/abapdocu_70/en/ABENSCREEN_GLOSRY.htmhttp://help.sap.com/abapdocu_70/en/ABENSCREEN_GLOSRY.htmhttp://help.sap.com/abapdocu_70/en/ABENSCREEN_GLOSRY.htmhttp://help.sap.com/abapdocu_70/en/ABENSCREEN_GLOSRY.htmhttp://help.sap.com/abapdocu_70/en/ABENTRANSACTION_GLOSRY.htmhttp://help.sap.com/abapdocu_70/en/ABAPSET_UPDATE_TASK_LOCAL.htmhttp://help.sap.com/abapdocu_70/en/ABAPSET_UPDATE_TASK_LOCAL.htmhttp://help.sap.com/abapdocu_70/en/ABAPCOMMIT.htmhttp://help.sap.com/abapdocu_70/en/ABENUPDATE_GLOSRY.htm


3/3

screen size. Values "X" (standard size), " " (current size).

RACOMMITSelection as to whether theCOMMIT WORKstatement terminates batch input processing or

not. Values: " " (COMMIT WORKterminates processing), "X" ( COMMIT WORKdoes not

terminate processing).

NOBINPTSelection for the symbol field sy-binpt. Values: " " (sy-binpt contains in the called

transaction "X"), "X" (sy-binpt contains in the called transaction " ").

NOBIENDSelection 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 FROMaddition,the values set by the

additionsMODE orUPDATE or the standard values specified there apply toDISMODE and UPMODE"A". The other components are set to the value " ".

Addition 4

... MESSAGES INTO itab

Effect

Using this addition, all themessagessent during batch input processing are

stored in an internal table itab of the type BDCMSGCOLL from the ABAPDictionary.
http://help.sap.com/abapdocu_70/en/ABAPCOMMIT.htmhttp://help.sap.com/abapdocu_70/en/ABAPCOMMIT.htmhttp://help.sap.com/abapdocu_70/en/ABAPCOMMIT.htmhttp://help.sap.com/abapdocu_70/en/ABENMESSAGE_GLOSRY.htmhttp://help.sap.com/abapdocu_70/en/ABENMESSAGE_GLOSRY.htmhttp://help.sap.com/abapdocu_70/en/ABENMESSAGE_GLOSRY.htmhttp://help.sap.com/abapdocu_70/en/ABENMESSAGE_GLOSRY.htmhttp://help.sap.com/abapdocu_70/en/ABAPCOMMIT.htm

call transaction

Documents