Kurumsal Finans ve Strateji Rehberi | Finance & Strategy Insights

Closing and opening accounting periods in SAP is a fundamental control mechanism that ensures data integrity across Finance (FI), Controlling (CO), and Material Management (MM) modules. Among these, the period change in Material Ledger (MM) via transaction code MMPV is a critical yet often misunderstood process. Executed incorrectly, it can halt logistics operations and distort financial statements.

This guide provides a comprehensive, step-by-step explanation of how to change the current period in SAP MM safely, why it matters, and what controls you must observe before executing it.

Why Change the Current Period in SAP MM?

SAP enforces strict period management to protect data accuracy and ensure auditability.

• Operational Integrity: Once a period (e.g., December 2024) is closed, no stock movements—such as goods receipts, issues, or adjustments—can be posted in that period.
• Financial Consistency: Prevents users from altering historical costs or inventory balances after reporting.
• Readiness for Next Cycle: Opens the next period (January 2025), enabling new procurement, production, and sales postings.
• Cross-Module Synchronization: Keeps FI, CO, and MM modules aligned for continuous posting and reconciliation.

Step-by-Step: How to Change the Current Period Using MMPV

1. Verify the Current Period

Transaction Codes: OMSY or MMRV

Check the existing period for your company code.

Example: If the system displays 011.2024, the next period to open is 012.2024.

Tip: MMRV also allows configuration of whether postings to the previous period are permitted, which is useful for minor corrections after closing.

2. Execute the Period Change

Transaction Code: MMPV

Steps:

1. Enter Company Code.
   Input the code of the entity whose material ledger you are updating.
2. Specify the New Period.
   Select the period following the current one (e.g., open 012.2024 if 011.2024 is current).
3. Select “Check and Close.”
   SAP runs consistency checks before execution. If open documents or unposted entries exist, it issues error messages preventing the close.
4. Run the Program.
   Click Execute (F8). Once the checks pass, the system updates the current period.

3. Validate the Results

If successful, SAP updates the Material Ledger period and locks the previous one.

If errors appear—open material documents, incomplete cost estimates, or unposted goods movements—review them with relevant teams (logistics, accounting) and correct before retrying MMPV.

Critical Considerations and Risk Controls

1. No Rollback:
   MMPV has no native reversal function. Always perform system and database backups before executing.
2. Cross-Module Alignment:
   • FI periods → OB52
   • CO periods → OKP1
   • MM periods → MMPV
     Misalignment among these causes posting failures between logistics and accounting.
3. Posting Lock Risk:
   If a period is closed but a new one is not opened, no postings can occur—halting all material movements.
4. Late Adjustments:
   Posting in a closed period is only possible if authorized and temporarily reopened via OB52 or through controlled SAP Basis intervention.

Best Practices Before and After MMPV

Checklist Item	Status
All material documents posted to accounting (FI)?	✅
Material price changes via MR21 completed?	✅
Material Ledger closing (CKMLCP) finalized?	✅
Current period verified in OMSY/MMRV?	✅
FI (OB52) and CO (OKP1) periods synchronized?	✅
Stakeholders (Finance, Procurement, Production) informed?	✅

Timing Recommendation: Execute MMPV on the first business day of the new month, before operational postings begin.

Authorization: Restrict MMPV access to senior finance users or SAP key users trained in period-end processes.

Common SAP Period Management Transactions

Transaction Code	Purpose
OMSY	View current MM period (basic view)
MMRV	Advanced period view and configuration
MMPV	Execute period change (Check & Close)
OB52	Manage FI period blocks
OKP1	Manage CO period blocks

Conclusion

Changing the current period in SAP MM using MMPV is more than a technical routine—it is a governance checkpoint that safeguards operational continuity and financial accuracy.

When executed with discipline, coordination, and documented controls, it becomes a cornerstone of reliable enterprise reporting.

For finance, logistics, and SAP professionals, mastering this process means mastering the backbone of period-end integrity in ERP systems.