Batch Input Tips and Tricks
Batch Input Tips and Tricks
1. Tips
2. Tricks
1. Tips
• The relevant transaction specifies the screen sequence for batch input.
• Batch input data is only available for visible screens.
• There is only one processing method for a transaction in batch input.
• A transaction ends successfully with:
- ABAP keyword COMMIT WORK.
- Return to main menu
For example:
'UPDA' 4-character function code for "Save", then utility field BDC_OKCODE = 'UPDA'.
'BACK' 4-character function code for "Back", then utility field BDC_OKCODE = 'BACK',
1
Information about Data Transfer and Batch Input
For example: Cursor in line 10 and column 25, then BDC_CURSOR = '10/25'.
• Session has status "Processing", but is not running: The session was set to "Processing" due to a
system crash. You can reactivate this session using transaction SM35 and the RELEASE function
and can then process it without loss of data. (See also SAP Note 12222.)
2
Information about Data Transfer and Batch Input
• Batch input in the background runs differently than in dialog processing (see SAP Note 33319)
2. Tricks
3
Information about Data Transfer and Batch Input
• Batch input dialog processing: If a user chooses F3, F12, or F15 to cancel batch input, batch input
runtime displays a dialog box to confirm the termination (see SAP Note 16629).
• Transactions written with the list processor can run in batch input in the background (see SAP Note
19422).
• Easier session error analysis: Link from the incorrect transaction to the error message in the log.
4
Information about Data Transfer and Batch Input
- RSBDCCKA - Checks whether a TemSe object exists for every APQL entry. Table APQL is the
log administration table and table TST01 is the TemSe file administration table. Both tables must
be consistent.
- RSBDCCKT - Checks whether an APQL entry exists for every BDCLG TemSe object.