SAP BATCH INPUT TABLE documentation, setup help and example usage

ARTICLE

CALL TRANSACTION - Batch Input Table
A batch input table of the type row type
BDCDATA specified after the addition USING of the statement
CALL TRANSACTION when transactions are called must have the following content (achieved by appending rows to an initial table in this order):

For each new dynpro, a new row with

a program name in the column PROGRAM

a dynpro number in the column DYNPRO

an "X" in the column DYNBEGIN

For each filled input field, a row with

the name of the dynpro field in the column FNAM

the passed value in the column FVAL

If the field is part of a table control
or step loop , the required row number must be appended to the field name.

If the cursor is to be positioned on a screen element

the value "BDC_CURSOR" in the column FNAM

the name of the screen element in the column FVAL

If the cursor is to be positioned on a screen element in a table control or step loop, the required row number must be appended to the name of the element.

For each dynpro, the function code

the value "BDC_OKCODE" in the column FNAM

a function code in the column FVAL

Any columns not used in a row remain initial.

Note
Transaction Recorder records executed transactions as batch input tables . The resulting batch input tables can be displayed and edited. Programs and function modules can be generated to use these tables.

Example
Transaction call, BDC table