Get Example source ABAP code based on a different SAP table
CALL TRANSACTION, Batch Input Table A batch input table of the line type BDCDATA, which is specified after the addition USING of the statement CALL TRANSACTION in transaction calls, must have the following content, which is achieved by appending lines to an initial table in this order:
For each new dynpro, a new line with
A program name in the column PROGRAM
A dynpro number in the column DYNPRO
A flag X in the column DYNBEGIN
For each input field to be filled, a line with
The name of the dynpro field in the column FNAM
The value to be passed in the column FVAL If the field is part of a table control or step loop, the desired line number must be appended to the field name. If the dynpro contains subscreens, their fields are assigned to the including dynpro. This can produce multiple fields with the same name, which are then all filled.
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 desired line 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 in a line that are not listed remain initial.
Latest notes:
Transaction Recorder (transaction SHDB) records executed transactions as batch input tables. The resulting batch input tables can be displayed and edited. Programs and function modules can be generated for their use.
In batch input folders, multiple field names of subscreens can be distinguished by specifying the special value BDC_SUBSCR in a preceding line in the column FNAM and in the column FVAL of the subscreen. ABAP_HINT_END
