The report RM07MMBL is used to create batch input sessions for goods movements. In a second step, you must process the BTCI sessions, in order to post the material documents for the goods movements.
The data for the BTCI session is imported from an external dataset as a sequential file. The structure of this sequential file is predefined in table BMSEG. You can display this structure via the Data Dictionary information system (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.
Similar to entering data online, the system expects certain data for each goods movement (for example, posting date, document date, material number, quantity). If this data is not made available, an error will occur when the BTCI session is processed.
Via batch input, you can post material documents with reference to purchase orders or reservations only if the reference documents exist in the system.
Procedure using test data
Before data is imported for the production system, a run should be performed using test data. In this case, data is not imported from the sequential file but from the Customizing system. This means that you have to maintain test data for the Customizing system of Inventory Management (under Tools -> Adopt data) -> Stocks -> Test data.
For testing purposes, the following goods movements are allowed:
- SAP transaction MB01, movement type 101 (goods receipt for PO)
For this movement, the order number and order item are required (not the material number). - SAP transaction MB11, movement type 501 (goods receipt w/o PO)
For this movement, the material number is required. - SAP transaction MB11, movement type 201 (goods issue for cost center)
For this movement, the material number and the account assignment (cost center) are required.
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.
