Solution : https://service.sap.com/sap/support/notes/11788 (SAP Service marketplace login required)
Summary :
In batch input or CALL TRANSACTION USING with screens containing variable step loops or table controls, errors such as "S00349 Field TABLE-FN1(12)2 does not exist in the screen PROGRAMM DYNR" may appear, depending on GUI screen size. This typically does not occur in background processing. Explicit scrolling in programs creating batch folders or executing CALL TRANSACTION USING can misalign lines. The recommended solution includes setting the standard screen size, especially in the background, and making sure custom programs align with the standard size. Use SY-SROWS in the ABAP debugger to check screen sizes and batch input recorder (SHDB) for OK codes.
Key words :
additional key words batch input, s00349 field table-fn1, variable line number depending, dynpro -----------------------------------------------------------module status_0100 output, create batch input sessions, /'dynpro sy-srows = ', variable step loops, variable sy-srows, prerequisites step loops, sy-srows shows
Related Notes :
| 1313810 | Batch input sessions: Default screen size does not work |
| 882856 | Number of condition lines is limited to strd screen lines |
| 68826 | Different screens in batch-input mode |
| 45507 | Processing batch input sessions in foreground |
| 41991 | Plnn. proces.: Batch input problems initial screen |