Symptom
This note answers frequently-asked questions concerning inconsistencies in inventory management.
Questions
1. What should I do if differences between material stock and stock accounts occur with transaction MB5L or with report RM07MBST?
2. How do SAP correct inconsistencies?
3. What do I have to take into account if I want to create a customer message concerning inconsistencies?
4. Are inconsistencies corrected in test systems and/or development systems?
5. Two MM documents were posted for a delivery. What should I do?
6. After the period closing program runs, data inconsistencies occur in the previous period, although the data of the current period is consistent. What causes this?
Answers
1. Question:
What should I do if differences between material stock and stock accounts occur with transaction MB5L or with report RM07MBST?
Answer:
Repeat the activity until you receive a consistent result. Different results are caused by postings during the run. If the runtime of the activity is long, use report RM07MMFI. If this report does not yet exist in your system, you can obtain it from SapservX. See Note 198596 for further information.
2. Question:
How do SAP correct insonsistencies?
Answer:
Note 34440 explains in detail our procedure for correcting inconsistencies.
3. Question:
What do I have to take into account if I want to create a customer message concerning inconsistencies?
Answer:
Make sure that the most recent versions of the analysis tools have been imported into your system (see Note 32236). Provide us with the following data (see Note 76926): System, client, user (with SAP_ALL authorization), telephone number (on which the password and access to the system can be requested), company codes, plants and/or materials affected by inconsistencies.
4. Question:
Are inconsistencies corrected in test systems and/or development systems?
Answer:
No. The analysis and correction of inconsistencies is very time-consuming, so we only correct production systems.
5. Question:
Two MM documents were posted for a delivery. What should I do?
Answer:
Use report ZZWASTOR in Note 424414. This report cancels the MM document duplication and ensures that the document flow for the delivery is updated correctly.
Duplicate postings can result in the moved materials having negative stocks, even though negative stocks are not allowed. In Customizing, allow negative stocks for the period of the adjustment postings.
In most cases, the stocks and values are consistent, that is, the stocks match the quantities belonging to the MM documents.
This type of error usually occurs due to illegal commands in a user exit of delivery processing, for example, COMMIT WORK. See Note 415716 for further information about user exits. We do not correct these errors as part of our normal product support.
6. Question:
After the period closing program runs, data inconsistencies occur in the previous period, although the data of the current period is consistent. What causes this?
Answer:
The following example describes a rare case that causes a large amount of data inconsistencies. During the period closing program run, the processing of a small MM document overtakes the processing a large MM document.
* Constellation:
- In Customizing for materials management, "Late Lock" is activated.
- In period closing for the material master (transaction MMPV), periods are closed during the interval between the last day of the old period and the first day of the new period.
* Example
o Date July 30, 2005, time 23:59
- You begin processing MM document 1, an IDoc consisting of 1200 items.
- Its posting date is July 30, 2005 and posting should occur in the current period.
o Date July 31,.2005, time 00:00 - 00:01
- The period closing program runs a day before the current period 07 is finished and changes the current period from 07 to 08.
- Therefore, all future goods movements and price changes with a posting date of July 31, 2005 are posted in the previous period.
o Date 31.07.2005, time 00:02 - 00:03
- The system processes and updates the next MM document (2), an IDoc with 100 items.
- MM document 2 contains goods movements that have combinations of material and plant that are the same as for MM document 1.
- The posting date is to 31.07.2005, that is, MM document 2 is posted in the previous period 07.
- The posting of MM document 2 causes the system to create history tables of the material masters that are to be posted for period 07.
- During the posting of the previous period, the quantities and values are updated simultaneously in the history tables of period 07 and the tables of the current period 08.
o Date July 31,.2005, time 00:04
- MM document 1 is posted and its processing is complete.
- At the start of processing, the system determined that this document, with a posting date of July 30, 2005, is to be posted into the current period.
- During the processing of this document the period is closed, but the posting program does not know this.
- MM document 2 has updated the entries for the current period, however this is now 08.
- The data in the history table of period 07 is now inconsistent as is the data for all the combinations of material and plant that are contained in MM documents 1 and 2.
* Conclusion
To avoid this constellation, do not allow any postings to occur whilst the period closing programs is running.
Before the period closing program runs, check in transaction SM13 whether outstanding update terminations of goods movements are still displayed. These must be cleared and closed before the period closing program runs.