SAP transaction codeObjectMMPVModuleMM_P2P

MMPV — Close Period for Material Ledger

MMPV closes the current material ledger period for a valuation area and advances it to the next period, allowing further goods movements and invoice postings to be valuated there. It does not run price determination itself and does not touch the general MM or FI posting period; those are opened separately.

This page covers MMPV, the transaction used to close a material ledger period during month-end closing. It focuses on the sequencing against periodic price determination, the tables the run touches, and the specific exception categories that block a clean close.

Reviewed by an ERPClimb SAP consultant on 15 Sept 2026· 1,115 words

Purpose

MMPV closes the current material ledger period for one or more valuation areas, moving the period pointer forward so postings can continue in the new period at the material ledger level. The structural fact behind most confusion: MMPV governs only the material ledger's own period status, which is separate from the general MM period (opened via period-opening configuration) and the FI posting period. A plant can have its MM and FI periods wide open while the material ledger period is still closed, and goods movements or invoice postings will fail with a period-related error that has nothing to do with the MM/FI period settings. MMPV also depends on periodic unit price determination having already finalised the period being closed; it will not silently skip that dependency, it will list the materials that fail the check.

When it is used

MMPV sits at the very end of the period-end closing sequence for materials under material ledger valuation: after periodic unit price determination has run and settled for the period, and before the business resumes normal goods movements and invoice postings in the new period. A consultant reaches for it once the closing team confirms the price run is clean, not before. It is not used for opening the general MM posting period, that is a separate step, and it is not an interface — there is no batch input or IDoc path for it, it is run directly or via a background job variant scheduled by basis on the functional team's instruction.

How to use it in practice

  • Confirm periodic unit price determination has completed for the period being closed, for every relevant valuation area, with no error status materials outstanding.
  • Run MMPV in test or simulation mode first for the company code or valuation area scope, never straight into update mode.
  • Review the resulting list of materials that cannot be closed and the reason given for each.
  • Resolve exceptions: rerun price determination for missed materials, clear negative stock, release blocked documents.
  • Execute MMPV in update mode, in background for plants with high material volumes.
  • Check the job log and the period status per valuation area afterward, and retry any materials still flagged.

Key data objects

  • CKMLPP - material ledger period totals record for quantities, keyed by material, valuation area and period, updated with the closed status once MMPV succeeds for that record.
  • CKMLCR - material ledger period totals record for values in the parallel currencies and valuations maintained for the material, closed in step with CKMLPP.
  • Material ledger period control per valuation area - the current and previous period pointers that MMPV advances; these are what a goods movement checks before it is allowed to post.
  • Material master accounting view - not directly rewritten by MMPV, but its valuation figures depend on the period totals being correctly closed and carried forward.

How to prove it in the data

In SE16 on CKMLPP, filter by material and valuation area and look at the period and fiscal year fields to see the last period actually closed for that record; if it lags behind the period the business thinks is open, the plant has not been fully advanced. Cross-check the period control record for the same valuation area to see the current versus previous period pointers. Where a goods movement is failing, take the material and plant from the error message and run the same filter — the mismatch between the movement's posting period and the last closed material ledger period is the proof.

ECC vs S/4HANA

MMPV itself is unchanged between ECC and S/4HANA. What changed is the context: material ledger with actual costing is standard and effectively mandatory in S/4HANA rather than an optional activation as in many ECC installations, which means MMPV closing is now part of every period-end cycle rather than a step some clients skip. A Fiori app covering material ledger period closing exists in current S/4HANA releases, but the transaction remains the reliable fallback for exception handling and background scheduling.

Common pitfalls and how to diagnose them

  • Price determination not final: MMPV refuses to close a period for any material whose periodic unit price run has not completed successfully for that period; always check the price determination log before touching MMPV, not after it fails.
  • Open documents against the period: production orders, purchase orders with unmatched GR/IR, or unsettled cost objects in the period being closed produce closing errors; the exception list names the material and document category, resolve or park before rerunning.
  • Negative stock or zero valuation: materials sitting at negative quantity or without a usable price cannot be closed cleanly; these need a correction posting or a manual price entry before MMPV will accept them.
  • Running straight to update mode: skipping the simulation step means the first sight of an exception list comes after the period is already partially closed, which is far harder to unwind than catching it in test mode.
  • Confusing ML period with MM/FI period: opening the general posting period does not unlock the material ledger period, and closing MMPV does not close the general MM or FI period; treat them as three independent switches.
  • Background job timeouts: for plants with a large material count, running MMPV online exhausts the dialog work process; schedule it in background and monitor the job log rather than assuming a silent failure means success.

Whose problem this is

Functional ownership sits with MM or CO closing specialists who sequence price determination and period closing. Basis is only involved for background job scheduling and monitoring on large runs. A good handover includes the valuation areas in scope, the last successfully closed period, the price determination run status, and the current exception list with material numbers and error reasons attached.

Related SAP objects

Reviewed pages this object connects to in the ERPClimb knowledge graph.

Source: ERPClimb — https://erpclimb.com/sap-tcodes/mmpvERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.