Errors occur when you process or record batch input sessions if the application uses frontend controls such as the ALV grid or three. Typical cases:
- The batch input recorder does not record any actions or frontend control data.
- When you process batch input sessions in the background, a termination or an ABAP short dump with the exception condition CNTL_ERROR occurs. The exception condition is caused in the control framework (program SAPLOLEA or also CL_GUI_*).
- When you process batch input sessions in the background, a termination occurs with the message
Editor could not be initialised' in the batch input log.
Processing a Call Transaction ... Using (processing mode N) in the background, a termination occurs with the message:
'Exception condition ERROR_DP initialized'
Cause and prerequisites
1. Frontend controls are generally not capable of batch input. Therefore the batch input recorder does not record any data for them and they cannot be supplied with data or actions during a BI session run.
2. Frontend controls cannot be accessed from a background process because it does not have an active SAPGUI connection. If such a communication is attempted by the application nevertheless, an exception condition is triggered by the control framework which causes a termination if it is not caught by the application.
This also applies to the background batch input (mode E) or a Call Transaction ... Using (mode E or N or P, respectively) in dialog processing.
3. The application uses a frontend textedit control. As with all other frontend controls, it cannot be accessed in batch input. If you try to run an application which uses this control in batch input, the system will terminate with the message BMEN 802, as for point (2). This occurs with the PFCG Transaction, for example.
Solution
1. If an application is to be capable of batch input, you must make sure that the desired functions can also be executed without participation of the existing frontend controls.
If this is not possible or cannot be achieved without investing considerable time and effort, you must use alternative methods for the data transfer (direct input, BAPIs).
2. If an application is running in the background or is processed in the background in dialog operation, no frontend controls may be generated and called (query on sy-batch and sy-binpt!).
The application developer should check whether the action that caused the termination was designed to be capable of batch input. If it was not, the batch input session must be changed accordingly. If it was, the application must make sure that no communication with frontend controls is attempted in the background or during batch input. This can be achieved with a consistent query.
3. As for problem (1), the user needs to check whether another editor can be used in the application instead of the edit control. For example, the editor must be based on a step loop or table view control, so that it can also be accessed in batch input. This question will be answered by the relevant development department.
Additional information on problems (1) and (2)
The question that is usually asked in practice is "Can I operate a transaction in batch input if it uses frontend controls?"
Although the batch input cannot run actions on controls, this does not necessarily mean that you can no longer run a transaction via batch input. This would only be the case if the controls were absolutely necessary for navigating in the transaction. A particular transaction can include several simultaneous actions that can be executed via batch input and some that cannot be executed this way at all.
One particular problem associated with this is that batch input can allow a transaction to run in the background. In this case, the application must ensure that no controls are created and used, in order to enable batch input.
(All statements in this note also apply to applications that use fast input or CALL TRANSACTION USING.)