SAP MMPV "Posting Only Possible
in Periods X and Y":
What It Means and the Exact Fix

This error means the Materials Management (MM) posting period has not been advanced to the current month. SAP MM has its own posting calendar — separate from Financial Accounting — that must be manually advanced at the start of each month using transaction MMPV. When someone tries to post a goods receipt, goods issue, or MIRO invoice in August but the MM period is still set to July, SAP blocks the posting and shows "posting only possible in periods 07 2026 and 06 2026." The fix is to run MMPV to advance the period — a 5-minute operation.

MMPV (Close Periods for Materials Management) advances the MM posting period from one month to the next. When you run it to close period 07 (July), SAP automatically opens period 08 (August). It is a one-way, irreversible operation — once a period is closed, it cannot be reopened through standard transactions. Run MMPV at the start of each month as part of the month-end close. The underlying ABAP program is RMMMPERI, which can be scheduled automatically as a background job via SM36.

MMRV (Allow Posting to Previous Period) temporarily allows a goods movement or invoice posting in the prior MM period after MMPV has already advanced to the next month. Use it for late postings — a July goods receipt that was missed and must be posted after August opened. Process: tick "Allow Posting to Previous MM Period" in MMRV, post the document with a prior-period date, then immediately untick the setting. Never leave MMRV permanently enabled — it defeats period control and creates audit risk. MMRV only goes back one period; posting two or more months back requires Basis support.

Two separate controls. The MM posting period (MMPV, stored in MARV) covers inventory postings — goods receipts, goods issues, physical inventory, MIRO invoice verification. The FI posting period (OB52, stored in T001B) covers accounting postings — journal entries, vendor payments, asset transactions. A goods receipt creates both a material document (MM) and an accounting document (FI). Both periods must be open for the posting to succeed. Running MMPV does not open the FI period, and vice versa. Always check both when troubleshooting posting errors at month-start.

No — MMPV operates at company code level and advances the MM period for all plants within that company code simultaneously. You cannot have plant 1010 on period 08 and plant 1020 on period 07 within the same company code. If your SAP system has multiple company codes (e.g. a Canadian entity CA01 and a US entity US01 as separate company codes), each has its own MM period and you must run MMPV separately for each one.

MMPV is irreversible through standard transactions. If you advance to the wrong period (e.g. close period 08 when July is still open, or jump ahead by two months), you need to raise a request with your SAP Basis team. They can use backend tools to reset the MARV table to the correct period, but this is a database-level change requiring system access and formal approval. It is possible but not fast. This is why you always check the period shown on the MMPV screen carefully before pressing Execute — the cost of a mistake is significant.

Use OMSY (Display Current Period for Material Management) — it is read-only and shows the current open MM period for all company codes without any risk of advancing it. Alternatively, look at the MMPV screen and note the period displayed before pressing anything. Do not use MMPV just to check — pressing Execute on MMPV immediately closes the displayed period, which is the opposite of what you want when checking.

Invoice verification in MIRO creates a material document and a financial document simultaneously. The material document side checks the MM posting period — just like a goods receipt. So if the MM period has not been advanced, MIRO invoice postings for the new month fail with the same "posting only possible in periods X and Y" message. The fix is identical: run MMPV. After advancing the MM period, both MIGO and MIRO postings for the current month will succeed (assuming the FI period is also open in OB52).

Yes — schedule the ABAP program RMMMPERI as a background job using SM36. Create a job with a step of type ABAP program, enter RMMMPERI, create a variant specifying the company code, and schedule it to run on the first day of each month at midnight or before business hours. Test the variant in QA first to confirm correct parameters. Once active in production, the period advances automatically with zero human intervention and the MMPV error disappears permanently. This is the recommended approach for any live production system.

The MMPV error directly affects all MM-related postings: goods receipts (MIGO 101), goods issues (201, 261), physical inventory (MI07), and MIRO invoice verification. Direct FI postings — journal entries in FB50, bank postings — are not affected by the MM period; they are controlled separately by OB52. However, because goods receipts create accounting documents simultaneously, a closed MM period effectively blocks the entire goods receipt process even though the FI side would be fine on its own.

The ABAP program behind MMPV is RMMMPERI. To schedule it: go to SM36, create a new job, add a step of type ABAP program, enter RMMMPERI, and create or assign a variant that specifies the company code and the period handling logic. Schedule with a monthly start condition. Always test the variant in your development or QA system before activating in production — confirm the program closes the correct period and produces no errors before the scheduled run goes live.

SAP MM always keeps two periods simultaneously available for posting: the current open period and one prior period. When the current period is August (08), July (07) remains open for a short overlap window to handle late postings. The message "posting only possible in periods 07 2026 and 06 2026" tells you the system is currently set to July — August is not yet open. The two-period overlap is the standard design, not an error. The number of prior periods allowed (default: 1) is configurable in OMSY.

No — within a single company code, all plants share the same MM posting period. MMPV operates at company code level and advances the period for all plants simultaneously. If you need plants in different regions to have different close dates, the standard SAP approach is to use separate company codes for each entity. You cannot set plant 1010 to period 08 and plant 1020 to period 07 within the same company code.

OMSY (Display Current Period for Material Management) is a read-only transaction that shows the current open MM period for all company codes in a single list. You cannot advance the period from OMSY — it is display only. Use OMSY when you want to check the current period status without any risk of accidentally advancing it. It is particularly useful for SAP administrators who monitor period status across multiple company codes before giving users the go-ahead to post.

Typical sequence: (1) Complete all goods movements and MIRO invoices for the closing month. (2) Post physical inventory differences (MI07). (3) Run GR/IR clearing (MR11 or F.13) to clear unmatched goods receipt and invoice lines. (4) Run MMPV to advance the MM period — this is the hard gate. (5) Run material valuation reports (MB5L). (6) Advance the FI period in OB52. Once MMPV is run (step 4), no new goods movements or MIRO postings can be made in the closed month without using MMRV.

Yes — using MMRV. Enable "Allow Posting to Previous MM Period" in MMRV, post your goods receipt in MIGO with a prior-period posting date, then immediately disable MMRV. This works for the one period immediately prior to the current open period. If you need to post two or more months back (e.g. post in June when August is current), MMRV is not sufficient — you need Basis support to reset the period, which is a backend database operation not available through standard transactions.

The current MM posting period is stored in the MARV table (Material Management: Current Period of a Company Code). MARV holds one record per company code with the current open period (field POPER) and fiscal year (field BDATJ). When MMPV is run, it updates this record. You can check the current period via SE16N by querying MARV and filtering by company code. In an emergency where the Basis team needs to correct an accidentally advanced period, they update MARV directly at the database level — a last-resort operation requiring careful authorisation.

The "posting only possible in periods X and Y" error is not user-specific — the MM period applies to everyone in that company code. If it appears for some users but not others, the most common explanation is different posting dates. A user entering a posting date of July 31 will succeed if July is still within the allowed prior-period window. A user entering August 1 will fail if August is not yet open. Check the posting date field in the MIGO or MIRO document — it must fall within one of the two currently open MM periods. Changing the date usually resolves it for the individual posting; running MMPV resolves it for everyone.

Two ways. Fast check: open OMSY and confirm the current period matches the current calendar month. If it shows the previous month, MMPV has not been run yet. Audit check: go to CDHDR (Change Document Header), filter by object class MMPERIOD, and check the change log — it shows who ran MMPV, on which date, and for which company code. CDHDR is the reliable audit trail; OMSY gives you the current status.

Yes — MMPV, MMRV, OMSY, and the underlying MARV table are identical in SAP ECC and S/4HANA. The period advance logic and the two-period overlap window are unchanged. In S/4HANA, MMPV may appear as a Fiori tile in the launchpad rather than a SAP GUI transaction screen, but the function and parameters are the same. Background job scheduling via SM36 and RMMMPERI also works identically. No relearning is needed when migrating from ECC to S/4HANA for this process.

Yes — VoiSAP's SAP MM training covers the full procure-to-pay cycle including month-end activities: MMPV, MMRV, GR/IR clearing (MR11), physical inventory (MI01, MI04, MI07), and account determination for goods movements (OBYC) — all on a live SAP S/4HANA system. Book a free demo to discuss your background and the fastest path to your first SAP MM role.