Force Close Material Ledger for Previous Periods

Material Ledger Closing (CKMLCP) won't run in current period unless all previous periods were closed, situations arise when one old period or more were not closed when:

> Users  forget to run the CKMLCP for one period or more

> Users/Consultant finds out that ML is already activated a time ago and none was aware

In this case you must force close the previous ML periods to be able to go one with the periodic closing cycle, there are 2 options

Option 1: Close the previous periods one by one (the safest option)

Follow this SAP Note 361236 - CKMLCP: No period-end closing operations after period shift

Here's the Note details:

Single-level price determination:

==> Go to the 'Change parameters' screen for the single-level price determination.
==>Enter "MUST_SETTLE" in the OK code (Transaction code field).
==> Choose ENTER.
==> A single-level price determination is carried out for the run.

Multi-level price determination:

==> Go to the 'Change parameters' screen for the multi-level price determination.
==>Enter "MUST_MULTI" in the OK code (Transaction code field).
==> Choose ENTER.
==> A multi-level price determination is carried out for the run afterwards.

Revaluation of single-level consumption (as of Release Enterprise)

==> Go to the 'Change parameters' screen for the revaluation of single-level consumption.
==>Enter "MUST_COGS" in the OK code (Transaction code field).
==> A revaluation of single-level consumption is carried out for the run afterwards.

WIP revaluation (as of Release Enterprise, Ext.Set 2.00)

==> Go to the 'Change parameters' screen for the WIP revaluation.
==>Enter "MUST_WIP" in the OK code (Transaction code field).
==> A WIP revaluation is carried out for the run afterwards.

Closing entry

==> Go to the 'Change parameters' screen for the closing entry.
==>Enter "MUST_CLOSE" in the OK code (Transaction code field).
==> A closing entry is carried out for the run afterwards.

Option 2: Close all the previous periods at once (if you missed many periods)

**This solution may cause data inconsistencies, in this case the solution I've is to restart cost component split at actual cost, this erases all the ML history and removes the inconsistencies**

TCODE:  ckmhelp

Choose HelpDesk for master data

Choose Change period status to 70

Enter Materials, plant and Period/Year and run the transaction.