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.

Structures vs Tables and Using the SQL Trace ST05

I guess you have looked at a standard SAP transaction and fit F1 help, followed by F9 technical information on a field?

You were hoping to find where the data was stored for a given transaction?

SAP often selects data from the database (Tables) and then formats it before presenting it on the screen. Often it creates structures with specific fields (which may span many tables) to display on the screen.

To find where the data is actually stored you need to dig deeper than just the structure:

Using the SQL Trace 

Open a new session with transaction ST05, select SQL Trace, click on the Trace On button, and go back to your transaction (while leaving the session with ST05 open). Submit your transaction, and go back to the ST05 session. Click on the Trace Off button, then select the List Trace button. Continue with standard selections, and a BASIC TRACE LIST will appear. search through the tables displayed under ObjectName.

SAP Library Link: SQL Trace

Cash Management Report Reconciliation

Reconciling Cash Position And Liquidity Forecast Reports

> Cash Position:

Compare FF7A with the trial balance (FS10N or F.01), note that FF7A uses the exchange rate valid at the day you run the report while FS10n uses the exchange rate recorded when the GL entry was posted, so there will be some differences between FF7A and F.01

In case of unreasonable differences, run transaction FDFD and do a data correction for all GLs then check again

> Liquidity Forecast:

1. Compare FF7A with the customer/vendor aging report (FDI0/FKI0)

2. If there's a difference then compare FF7A with FBL1N/FBL5N (use the Due Date column not the Posting Date column)

3. If there's still unreasonable difference then run transaction FDFD and do a data correction for All Customers/Vendors


NOTES

1. TCODE TRTC includes all CM reports

2. CM tables start with FD*:

• FDFIEP (CM: FI Line Items (OP of Deb/Cred for Drilldown))
• FDSR2 (CMF Totals Records for customer/vendor Planning Groups)
• FDSB2 (CMF Totals Records for GL)
• and many others

Asset Reporting Customization

The sort versions can do any report, and it's configurable on PRD too !

Go to tcode OAVI and customize your own sorting variant.

Managing COPA Reports

Solution to short lead column (characteristic) description:

        Right click on the lead column header >> Characteristic display >> in the available fields         select the long text

Manually modifying layout:

       You can change the report layout after running it, then save the report definition.

Deleting frozen "Saved" report data:

       Go to transaction KE39 "Reorganize Reports"

Creating New Tcode for a report with SAP Area Menu

Go to tcode SE21
 > Create your Z Package

Go to Tcode SE43
> Choose a suitable area menu (such as COPA)
> Change the menu, add your report(s), they will be assigned a Y tcode by SAP
>Copy this menu to a new menu (menu name is its tcode)
>Delete inquired nodes
>Save, insert your package upon request