Diagnosis The transaction sent a screen that was not expected in the batch inputsession and which therefore could not be supplied with data. Possible reasons: 1. The batch input session was created incorrectly. The sequence ofscreens was recordly incorrectly. 2. The transaction behaves differently in background processing in abatch work process than when running in dialog (SY-BATCH is queried andchanges the screen sequence). 3. The transaction has undergone user-specific Customizing andtherefore certain screens may be skipped or processed differently,according to the current user. If the person who created a batch inputsession is not the same as the person now processing it, this problemmay occur frequently. System Response None. Procedure For 1: Either re-create the session or process it in expert mode.Correct the batch input program. For 2. It is very difficult to analyze this problem, particularly inthe case that the screen sequence or the display-only options of fieldsdiffer according to whether the transaction is being processed in thebackground or as an online dialog. It could also be that this kind oftransaction cannot run with batch input. For 3: Have the creator of the session process it. If no error occursnow, then this is a program with user-specific Customizing. |