Material Master Period closing:

Question

Hey Gurus,
Currently we are running MMPV globally which causes few issues regularly.
Hope running MMPV locally would fix these.
Splitting the MMPV transaction event (by world time zones) would be a major piece of work to establish the impacts on other processess (such as billing, intercompany accounting, consolidation, standard costing runs and actual costing runs). Needless to say, such a change would need to involve multiple functions (Procurement, sales, finance).
Immediate response in this regard in highly appreciable,
Regards,
KK

Answer 1

You may refer to  note 520010 that has a FAQ on period closing, which recommends not to allow posting while period closing is being done.
(My comments: You may trying closing the period following the Sun, However you may want to monitor the inter-company transaction closely to avoid any inconsistencies.)
The note's content is reproduced below.
"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
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.
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.
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.
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
<b>To avoid this constellation, do not allow any postings to occur whilst the period closing programs is running.</b>
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.