Use report RM07RRES to generate a batch input session for reservations. You must process the session in a second step in order to post the reservations.
The data for the batch input session are imported from an external dataset as a sequential file. The structure of this sequential file is predefined in table BRESB and cannot be changed. You can display this structure via the information system in the data dictionary (object class fields).
Requirements
Before you start the report, make sure that the file entered on the selection screen is stored in the specified directory at operating system level.
As with online entry, the system expects certain data (e.g. requirement date, material, quantity, account assignment) for each reservation. Any attempt to create a reservation for a material that has not yet been maintained in the system will lead to an error when the session is run, causing the latter to be interrupted.
Any errors that may occur are documented in the log file of the relevant batch input session.
Running a session with test data
Before the sequential file is imported, a session should be run with test data. In this case, the data is not imported from the sequential file, but from table T159A. You must thus maintain test data for this report (SAP transaction MB21) in table T159A.
Reservations for the following goods movements are allowed for test purposes:
- movement type 201 (goods issue for cost center)
- movement type 501 (goods receipt without PO)
Output
The system generates a batch input session which you can process via options System -> Services -> Batch input -> Sessions.
When processing the batch input session for testing purposes, you should set the Display errors only indicator.
When importing the actual productive data, you should always use the Background indicator.
If data expected by the system (required-entry fields) does not exist, an error will occur during the batch input session which will interrupt processing.
An error will also occur during the batch input session if you try to maintain data not expected by the system (fields not ready for input). However, processing will not be interrupted. The system writes a comment in the session log.
