Solution : https://service.sap.com/sap/support/notes/33319 (SAP Service marketplace login required)
Summary :
Batch input behavior may differ in background processing compared to an online environment due to several factors: 1) Batch inputs run under the user specifications set during folder creation in BDC_OPEN_GROUP, visible in SM35 transaction. 2) Inactive Dynpros may lead to cursor issues since there is no GUI in background jobs, requiring manual setting of BDC_CURSOR. 3) Background processing might read system flag SY-BATCH differently, affecting application transaction flows, which can be simulated in dialog mode using ABAP debugger. 4) Frontend controls in application transactions may not process correctly in the background. For solutions, refer to the actions described above.
Key words :
additional key words batch inputshdbtransaction recorder, error message 'batch input data, system flag sy-batch, batch input runs, note 311440 batch input, function module bdc_open_group, service field bdc_cursor, normal dialog operation, application transaction behaves, batch input
Related Notes :
| 1355047 | Batch input for CFM2/3 |
| 721791 | Dump when running a batch input session in OM |
| 634956 | Batch input: Starting sessions indep. |
| 592896 | PPM maintenance: Mass maintenance of PPM plans |
| 554139 | FAQ 2: Batch input |
| 491055 | Report RHXPE_EXPIRED_QUALI does not generate any spool list |
| 433137 | Batch input: Simulating background mode |
| 370958 | Consulting note:Frequnt problems during batch input |
| 311440 | Batch input and controls |
| 68826 | Different screens in batch-input mode |
| 45507 | Processing batch input sessions in foreground |