MMPV and MMRV in SAP: Which Table, and What They Control
mmpv table in sap
Also searched as
- mmrv table in sap
- MMPV MMRV difference SAP
- MARV table SAP material period
- how to open previous period in SAP MM
Short answer
MMPV (Close Periods for Material Master) and MMRV (Allow Posting to Previous Period) are transactions, not tables. Both work on table MARV, the material master control record per company code, which stores the current, previous and last-year posting periods for goods movements. Read MARV in SE16N to see the open MM period; use MMPV to roll forward and MMRV to allow a posting into the previous period.
Applies to: SAP ECC 6.0 and S/4HANA on-premise. With Material Ledger actual costing, period close is driven from CKMLCP, so check your costing setup before running MMPV by hand.
How to check and change the open MM period
- 1Run SE16N, enter table MARV, and select by BUKRS (company code). Read LFGJA/LFMON (current period and year), VMGJA/VMMON (previous period and year) and VJGJA/VJMON (period in the previous year).
- 2Compare with the posting date of the failing MIGO or MB1A document. MM only accepts postings in the current period, the previous period (if allowed) and, in some setups, the previous year's last period.
- 3To move MM to the next period, run MMPV, enter the company code and the period to close into, and execute. MMPV works one period at a time and only forward.
- 4To post once into the previous period after MMPV has already moved on, run MMRV, select the company code and set the indicator that allows posting to the previous period. Post the document, then switch it off again.
- 5Check the FI side separately in OB52 (open posting periods per account type). MM and FI periods are independent controls and both must allow the posting.
- 6If MMPV refuses, read the message: usually a period-end check failed (open material documents, valuation not completed) or the target period is not the immediate next one.
- 7Never edit MARV directly with SE16N or a report. Use MMPV, MMRV or OMSY under change control, because other tables (MBEW) carry their own period stamps.
What MARV actually holds
Table MARV is the material master control record. It has one row per company code and carries the periods that inventory management uses to validate a posting date. The fields that matter are the current period and fiscal year (LFMON, LFGJA), the previous period (VMMON, VMGJA) and the last period of the previous year (VJMON, VJGJA). There is also a flag that permits posting into the previous period, which is the switch MMRV sets.
MMPV and MMRV are therefore two screens over the same record. People search for them as tables because the transaction codes appear next to table names in error threads, but there is no table called MMPV or MMRV. If you look for them in SE11 you will find nothing.
SE16N > Table: MARV Selection: BUKRS = 1000 Check fields: LFGJA, LFMON, VMGJA, VMMON, VJGJA, VJMON
MMPV versus MMRV
MMPV is the period close. It advances the current MM period by one for a company code, so the old current period becomes the previous period. After that, normal postings are only possible in the new period and, while the previous-period permission is on, in the one before it.
MMRV is the exception handler. It does not move periods. It lets users post a late goods receipt or goods issue into the previous period without rolling anything back. It is the usual answer to an urgent request from the plant to back-date one document after the month has already rolled.
Neither transaction fixes an FI period problem. If OB52 has the period closed for account type M or the relevant GL accounts, the posting still fails even though MARV looks fine.
How this ties to MIGO period errors
A MIGO message that says posting is only possible in specific periods means the posting date falls outside what MARV allows. The fix is not to change the posting date blindly: confirm whether the plant really closed the month, then either post in the current period or use MMRV for a controlled exception.
The existing MIGO M7-053 article covers that error in detail. This page is the reference for the control record itself.
Material Ledger and S/4HANA
In S/4HANA the Material Ledger is always active, and when actual costing is switched on, period closing is run through the costing run (CKMLCP) which also advances the material period. Running MMPV by hand in that setup can leave inventory valuation and period control out of step, so follow your finance team's close calendar rather than moving periods on your own.
Common pitfalls
- !Searching for MMPV or MMRV as tables: they are transactions, the data lives in MARV.
- !Closing the MM period before all goods movements, invoice receipts and the GR/IR clearing for the month are done.
- !Leaving the MMRV previous-period permission switched on after the exception posting.
- !Assuming MM and FI periods move together. They are separate controls (MMPV and OB52).
- !Editing MARV directly. It bypasses checks and desynchronises MBEW period stamps.
How an ERP-grounded AI assistant handles this
A grounded assistant on the SAP system can read MARV, OB52 settings and the failing document's posting date, then tell the user which control blocks the posting and who owns the fix, without anyone opening SE16N. For on-prem SAP, Netray runs this against your own system with an open-weight model on your GPUs, read-only, and shows the exact table read. Period changes stay a human decision in MMPV or MMRV.
Frequently asked questions
Is MMPV a table in SAP?
No. MMPV is a transaction code, Close Periods for Material Master. The table it updates is MARV, the material master control record per company code. Searching SE11 for MMPV returns nothing, which is a common source of confusion.
What is the difference between MMPV and MMRV?
MMPV moves the current MM posting period forward by one for a company code. MMRV does not move anything: it allows postings into the previous period, usually for a single late document. One closes, the other grants a controlled exception.
How do I see which MM period is open?
Open SE16N, table MARV, filter by company code and read LFGJA and LFMON for the current period, with VMGJA and VMMON for the previous one. That shows what inventory management will accept before you try the posting.
Can I reopen a period after running MMPV?
MMPV only goes forward. To post into the closed month use MMRV for the previous period. Going back further needs a controlled correction with your SAP Basis and finance team, typically via OMSY, and should not be done casually.
Related
SAP MIGO error M7 053: posting only possible in periods X and Y
M7 053 means the posting date of a goods movement is outside the two open material periods held in table MARV. Either use a posting date inside the allowed periods, or have inventory accounting open the right period with MMRV or advance it with MMPV. FI periods in OB52 are a separate check and can cause a different message.
Error fixSAP F5 060: Posting Only Possible in Periods X and Y
Message F5 060 fires when a document date falls in a fiscal period that the posting period variant has not opened for that account type. Either change the document/posting date into an open period, or have Finance open the required period and account type in OB52 for the relevant variant.
How-toSAP open purchase orders report: ME2N, ME2M, ME2L and the underlying tables
Use ME2N for a flexible open PO list, ME2M by material and ME2L by vendor, with the selection parameter Still to be delivered. The open quantity is the scheduled quantity in EKET minus goods received in EKBE, excluding deleted and delivery-completed items. For custom reports, read EKKO, EKPO, EKET and EKBE.
Error fixSAP M7 021: Deficit of SL Stock Quantity
M7 021 fires during a goods issue, delivery, or confirmation when SAP checks the unrestricted-use (SL) stock for the exact plant, storage location and batch combination and finds less than what you are trying to post out. Fix the entry (batch, storage location, quantity) first; only enable negative stock or downgrade the message to a warning if the business genuinely needs to post ahead of a receipt.
Error fixSAP IDoc Status 51: Application Document Not Posted
Status 51 tells you the IDoc reached the application layer and failed to post, but the status text itself is not the error - the real cause sits in the status record's long text or the linked application log. Fix the underlying data or configuration, then reprocess the IDoc through BD87 rather than editing the status.
Error fixSAP Short Dump TIME_OUT: Maximum Runtime Exceeded
A TIME_OUT runtime error means a dialog (or RFC) work process ran longer than the maximum allowed runtime, controlled by profile parameter rdisp/max_wprun_time (600 seconds by default). The fix is almost always to move the long-running work to background processing or tune the underlying program, not to raise the timeout.
AI for ERPAI for SAP S/4HANA, Running On-Prem or in Your Private Cloud
Run AI on SAP S/4HANA without sending ERP data to a public API. On-prem and private-cloud architecture, CDS views, OData, and honest deployment trade-offs.
AI for ERPGet AI Value From SAP ECC Now, and Use It to De-Risk the Move to S/4HANA
SAP ECC 6.0 mainstream maintenance ends in 2027. Add AI value on ECC now, using its existing BAPIs and IDocs, and use it to de-risk the S/4HANA migration.
Stuck on SAP ECC / S/4HANA?
Talk to engineers who work inside SAP ECC / S/4HANA every week, and who build private AI that answers these questions from your own ERP data.
Keep exploring
ERP fixes and how-tos
- SAP MMPV Period Closing Error: Opening and Closing MM PeriodsHow to open and close MM posting periods with MMPV, MMRV and OMSY, what the MARV table holds, and how to fix MMPV period closing errors in SAP MM.
- MMPV Date Check Error in SAP: Causes and FixWhy SAP MMPV fails its date or period check when closing MM periods, and how to fix it: MARV status, skipped periods, open documents and locks.
- SAP MIGO error M7 053: posting only possible in periods X and YMIGO error M7 053 means the posting date falls outside the open material period. How to read MARV, run MMPV and MMRV, and avoid the same error next month.