SAP MIGO error M7 053: posting only possible in periods X and Y
SAP MIGO M7 053 Posting only possible in periods
Also searched as
- MIGO posting only possible in periods 2026/09 and 2026/08 in company code
- SAP MMPV close period error M7053
- SAP MMRV allow posting to previous period
Short answer
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.
Applies to: SAP ECC 6.0 and S/4HANA (material ledger and non-material-ledger systems)
Resolve the period error
- 1Read the message in full. It names the two periods that are open, for example 2026/09 and 2026/08, and the company code. Compare them with the posting date in the MIGO document header.
- 2If the posting date is simply wrong, change it in the Document Date and Posting Date fields in MIGO and post again. Back-dating beyond the open periods is not allowed by design.
- 3If the date is correct and the period should be open, ask inventory or cost accounting to run MMRV (Allow Posting to Previous Period) to set the previous period, or MMPV (Close Period) to advance the current one. These are company code level actions.
- 4Check table MARV for the company code. LFGJA and LFMON hold the current period, VMGJA and VMMON hold the previous period, and XRUEV/other flags show whether a period is in transition.
- 5If the company runs the material ledger, confirm that the material ledger period (CKMLPP or the ML period control transaction) is consistent with the MM period. The ML period must be open for the posting.
- 6Check the FI posting periods in OB52 as well. A posting can pass the MM period check and still fail at FI with a different message such as F5 201 or the posting period closed error.
- 7Repost the movement. If a batch of postings failed because of this error, rerun them after the period is reopened, preserving the original posting date where policy allows.
What MARV controls
Table MARV holds the current and previous material period per company code. A goods movement is allowed only when its posting date falls in the current period, the previous period, or the last period of the previous fiscal year if the year-end flag allows it. Anything else raises M7 053.
This check is separate from the FI check in OB52. MM periods control quantity and value updates in the material master and stock tables, while OB52 controls document posting in the general ledger. Both must be open for a goods receipt with accounting entries.
-- Which periods are open for the company code
SELECT BUKRS, LFGJA, LFMON, VMGJA, VMMON
FROM MARV WHERE BUKRS = '1000';
MMPV versus MMRV
MMPV closes the current period and moves to the next one, which is the month-end step. It runs checks that block closing when there are unposted items such as open material documents or incomplete valuation runs. MMRV does something different: it lets you post in the previous period after it has already moved on, useful for late goods receipts at month end.
In S/4HANA and with the material ledger, month-end closing is more tightly sequenced: the material ledger closing steps (CKMLCP) take over a lot of what used to be separate runs, and the MM period is advanced as part of that process. Do not advance MMPV ahead of the ML closing process on a system where ML is active.
Change these settings only with accounting's agreement. Opening a previous period after reports have been issued changes inventory values that someone has already reported.
Common causes besides a wrong date
A frequent cause is an interface or a background job that posts with the document date as the posting date. If the source system sends yesterday's date on the first day of a new month, and MMPV has already advanced, the movement is fine. If it sends a date two months back, it fails.
A second cause is a copied or reversed document. A reversal in MBST uses the original posting date unless you override it, and reversing an old document in a closed period triggers the same message. Reverse with a current posting date, if your accounting policy permits.
A third cause is scheduling agreements or subcontracting components with a stale date proposed by the program. Check the date the program passes, not what you see on screen.
Common pitfalls
- !Running MMRV and forgetting to close it again, leaving the previous period open for weeks and letting late postings change reported values.
- !Advancing MMPV before the material ledger closing is complete on a system with ML active.
- !Fixing the MM period but not OB52, then hitting a second error in FI on the same posting.
- !Reversing an old document with its original posting date and assuming the system will pick the current date.
- !Asking basis to change MARV directly. It is a controlled table and direct edits corrupt period logic.
How an ERP-grounded AI assistant handles this
A grounded assistant can answer the practical question quickly: read MARV for the company code, compare it with the posting date on the failing document, and state which period needs to be open and whether the FI period is also affected. For batches of failed interface postings it can list which ones fail on date alone. The decision to open a period belongs to accounting, and any write stays behind a human approval.
Frequently asked questions
What does M7 053 mean in SAP?
It is the message that the posting date of a goods movement is outside the open material periods for the company code. SAP allows postings only in the current and previous period recorded in table MARV. The message names those two periods so you can compare them with your posting date.
Which transaction fixes it, MMPV or MMRV?
MMRV lets you post to the previous period, which fixes late postings from the last month. MMPV closes the current period and moves forward, which is a month-end task. Use MMRV for a late goods receipt and MMPV only when accounting is ready to close the month.
Why do I still get an error after the MM period is open?
The FI posting period in OB52 is checked separately for the accounting document. Material ledger period control can also block the posting if ML is active and not aligned. Check all three: MARV, OB52 and the material ledger period status.
Can I back-date a goods receipt to a closed month?
Not unless the period is opened for posting, which is an accounting decision. Back-dating changes values that may already be reported, so the usual approach is to post in the current period with a note, or reopen the previous period briefly with MMRV and close it again.
Related
SAP 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.
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.
How-toSAP GR/IR clearing account balance: reconcile with MB5S and clear with MR11
The GR/IR clearing account holds the value of goods received but not yet invoiced, and invoices not yet matched with receipts. It should trend to zero per PO item. Reconcile it with MB5S, find the PO items that are stuck, and clear true differences with MR11 or automatic clearing in F.13, after correcting the cause.
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.
How-toHow to Read MD04 Exception Messages in SAP
The exception indicator in MD04 flags procurement elements whose date or quantity no longer matches the current demand situation - it is SAP's built-in change signal, read element by element in the detail screen, not just the header icon. Triage by exception group first, then decide to reschedule, cancel, or accept each one.
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.