Posting only possible in periods 2025/12 and 2025/11 in company code 5000 Message No. M7053 - SAP MM

[Sridevi51]

I checked in MMRV and it is not in current period like April,2025, showing directly Nov,2025 & Dec,2025 as shown below in the screenshot. I even checked in MMPV/ OB52/OBY6/OMSY/MMPI everywhere the settings are right.

Material Ledger is also in activate mode.

MMRV

Tried the all possible ways, but not resolve the issue yet. It has to come current period April,2025. Can anyone please help on this.

[DominikTylczyn]

Does your fiscal year follow calendar year or do you have any offset? If it follows, how you did you manage to open December in April?

[RaymondGiuseppi]

Questions:

• Does it happen in a productive system,
• Is material ledger activated,
• Can you display table changes on MARV or V_001_MARV with SCU3,
• Did someone use MMPV (RMMMPERI), MMRV (SAPMM03Y) or OMSY (SAPL0MM2).

Read carefully KBA 2042164 - MMPV Period shifted by error to future period for Material Ledger active plant (transaction MMPI or report RMMMINIT )

[DominikTylczyn]

I'm afraid the note won't work as the periods are already shifted X+8 i.e. December opened in April.

[RaymondGiuseppi]

Start the report month after month and keep your fingers crossed. Personally, I'd rather raise a problem/case to OSS than shoot a remake of Back to the Future.

• Also the OP should read carefully the support page at Inconsistency in Material Management - Inventory Management 
• Then the OP should apply steps from 1082841 - MMPV/Close Periods : Prevent shifting to a future period by mistake 

Waiting for the PO to answer questions 😴

[DominikTylczyn]

Hello @Sridevi51 

The only way I'm aware of to shift periods back is the one described here: SAP MM Period Opening Withdrawal It worked for me then, when I wrote the article. I don't know if it still works - probably. So no guarantees here.

Best regards

Dominik Tylczynski

[RaymondGiuseppi]

Personally, I haven't updated SAP with SE16[n] this century 🙄.

I don't want to read 3202191 - How to solve DBSQL_DUPLICATE_KEY_ERROR dump under transaction MMPV ...