FAQ: Batch Input
1. General information
1.1 Question: Why does the batch input session behave differently when running in the background than when it runs in the dialog?
Answer: There are several explanations for this phenomenon:
The batch input session always runs in the dialog using the authorizations and settings of the logging user, whereas in the background, the batch input session runs with the user assigned as a USER parameter in the BDC_OPEN_GROUP function module (visible in transaction SM35).
If the background processing terminates with the error message indicating that the batch input data for screen XXXXXXXX does not exist, your session contains screens that are switched to completely inactive, which measns that they do not contain input fields, active checkboxes or selection fields (for detailed information, see notes 113310, 433137 and 370958).
The application transaction behaves differently in the background than in the normal dialog mode (see note 33319 and 433173).
The application transaction uses front-end controls that cannot be processed in the background (for a detailed description and help, see note 311440).
1.2 Question: Can I also simulate background processing?
Answer: As of Release 6.20, you can specify the 'Simulate background mode' option during the recording in the transaction recorder (for detailed information, see note 433137).
1.3 Question: What must I consider when running a batch input session in the foreground?
Answer: Running batch input sessions in the foreground is a correction mode. In this case, we deliberately gave the operator more freedom. For example, you can branch to other functions and then return to the original screen, you can edit data, you can delete data records from the session and so on. As a result, sessions running in the foreground are very prone to operating errors (for detailed information, see note 45507).
1.4 Question: Why can I not scroll in the background mode with P*?
Answer: For technical reasons, we cannot support scrolling in the background mode with P+, P++, P - and P- -. You must therefore use the "Edit -> Position" function (see note 370958 and 117673 for detailed information).
2.Special system response
2.1 Question: How do I react to the message "Please select valid row"?
Answer:Here, you must distinguish between the system response in the foreground and in the background:
In the foreground, the session fails with "Please select valid row" if, for example, you are supposed to carry out an action on an object in the list in an overview.
If the cursor in the background is not explicitly set using BDC_CURSOR, it is set in the first field in the top left side of the screen. However, the first field on the top left side contains header information and is not normally an overview field.
In addition, it generally makes sense to select the desired line in the overviews by setting the selection flag (if available).
2.2 Question: Why do I receive the error message "Batch input data for SAPLCJWB 0300 not filled"?
Answer: This error can have several causes;the most common cause as of Release 4.0 is the following:
You use a template to create a project in transaction CJ01 and start the "Search and Replace" function from the menu instead of using the function key. In this case, the LETV OK code from Release 3.0/3.1 is used by mistake instead of the new LETC OK code (see note 164526).As of Release 4.0, you must always use LETC instead of LETV as a BDC_OKCODE in the batch input session.
2.3 Question: Are fields set using SET/GET parameters automatically copied to the session during recording?
Answer: Up to and including Release 4.5, fields set using SET/GET parameters are not automatically copied to the session during the recording, instead, you must maintain them manually.