Material Ledger Actual Costing has been activated already in the system before the system conversion to SAP S/4HANA.
You can verify if Material Ledger Actual Costing is active for one or more plants via SAP Reference IMG / SAP Customizing Implementation Guide (transaction SPRO)
-> Controlling-> Product Cost Controlling-> Actual Costing/Material Ledger
-> Actual Costing-> Activate Actual Costing-- Activate Actual Costing
=> Checkbox 'Act.Costing' (Updating Is Active in Actual Costing)
When this checkbox is marked, this means that Material Ledger Actual Costing is active in this plant.
Technically this can be verified via database table T001W, field MGVUPD. 'X' means that Material Ledger Actual Costing is active in this plant.
In addition, the table T001W shows the link between the plant and the valuation area.
With S/4HANA the data model for material ledger data has been changed significantly, especially when actual costing is active.
The main purpose for the changed data model is:
Business Process related information
Required and Recommended Action(s)
There is no default Material Ledger Type 0000 anymore.
Simplified Data Model
o The new Material Ledger Document tables MLDOC and MLDOCCCS replace most former periodic tables (MLHD, MLIT, MLPP, MLPPF, MLCR, MLCRF, MLKEPH, CKMLPP, CKMLCR, MLCD, CKMLMV003, CKMLMV004, CKMLPPWIP, CKMLKEPH). For more information refer to note 2352383.
o Some of the former periodic tables are still required for the following purposes:
o The design of tables MLDOC/ MLDOCCCS allows storing both line item and aggregated data.
o Periodic transactions (goods movements, activity confirmation, etc.) update tables MLDOC/ MLDOCCCS with line item data using the INSERT ONLY principle.
o Material Ledger Period Close creates (run-dependent) settlement records in tables MLDOC/ MLDOCCCS to store the results from Actual Costing. These records are stored under the costing run key (field Run Reference) so that they are visible only by the corresponding costing run. In this way different runs (e.g. a periodic run and an AVR) can store their results independently from each other.
o Important design changes
Single- and multilevel differences are no longer distinguished. In table
MLDOC all price/exchange rate differences are stored in fields PRD/KDM. In
table MLDOCCCS the CCS for price/exchange rate differences are stored
under the CCS types E/F (field MLCCT).
The CCS is stored in a table format using the cost component (field
ELEMENT) as additional key. This allows increasing the number of cost
components without modification.
The CCS for preliminary valuation is always stored
Tables MLDOC_EXTRACT and MLDOCCCS_EXTRACT
The table MLDOC_EXTRACT holds information about quantity and valuation changes.
Transaction based updates, like goods movements or invoice receipts, usually update tables MLDOC and MLDOC_EXTRACT in parallel. But table MLDOC_EXTRACT can be compressed. After compression, the table will contain only one entry per cost estimate number, period and currency type valuation view. Table MLDOC_EXTRACT allows fast and efficient calculation of total quantity and total value, by cumulating all records for specific cost estimate number(s). The same is true for table MLDOCCCS_EXTRACT which has been designed for holding cost component information. During period shift (transaction MMPV) the tables MLDOC_EXTRACT and MLDOCCCS_EXTRACT will be compressed automatically for periods older than previous period.
Manual compression via program FCML4H_RMLDOC_EXTRACT_COMPRESS or via function module
FCML4H_MLDOC_EXTRACT_COMPRESS is possible and recommended in case of very high number of material movements.
o Table MLRUNLIST replaces the former table CKMLMV011 (Object List for Costing Run), but has some additional functions:
Materials and activities selected for a costing run are stored under the
corresponding run id.
It manages the period status of materials and activities
In case Material Ledger Actual Costing has been activated already in the system, in one or more valuation areas, before the system conversion to SAP S/4HANA (when the system is e.g. on release SAP ERP 6.0 or on SAP Simple Finance), the tables MLDOC, MLDOCCCS, MLDOC_EXTRACT and
MLDOCCCS_EXTRACT are filled automatically with data, during Migration Step M10: Migrate Material Ledger Master Data for the valuation areas, where Material Ledger Actual Costing has been activated. The data will be created starting from last period of previous year until the current period in the system. All material related goods movements or price changes from previous years will be converted to the MLDOC tables as if the goods movement or the price change has taken place in the last period of previos year. The data of the current year will be converted not based on single material documents or price change documents, but there will be one entry per period, per currency
type and valuation view, per category (e.g. "Receipts"), per process catregory (e.g. "Production") and per production process. Data related to ML Alternative Valuation Runs are not converted automatically during Migration Step M10.
Material Price Analysis (Transaction CKM3):
Remark: Data older than last period of previous year (related to the time of system conversion) cannot be displayed via transaction CKM3 because the 'old' data has not been converted to the MLDOC-tables. To show data older than last period of previous year you can use transaction CKM3OLD('Material Price Analysis') or CKM3PHOLD ('Material Price History')
ML Actual Costing Cockpit (Transaction CKMLCPAVR):
o Create a Classic AVR which is the same like before.
o Create an AVR with run reference which means the settings are taken from the run reference and cant be changed. Only the plants must be chosen.
The new steps of an ML costing run are:
o Selection (program FCML4H_SELECTION)
o Preparation (program FCML4H_PREPROCESSOR)
o Settlement (program FCML4H_SETTLEMENT)
o Post Closing (program FCML4H_POST_CLOSING)
the button Results in the section Processing.
o The new AVR do no longer copy the data into a separate key area. (Only the
settlement records are stored under the AVR Run Reference, see above). In
particular, the cumulation of several period is done On-the-fly.
o The former step Cumulate Data is no longer needed
o The complex rescale logic, which adjusts all materials data to a common preliminary AVR price, is no longer needed.
o All AVR can now handle WIP
o Post Closing:
introduced. See the documentation in transaction OBYC for the new
transaction key PRL:
Price differences for activity types or business processes. During settlement in
the material ledger, these price differences are posted from cost centers
(Transaction/Account Modification GBB/AUI) to the material ledger
(transaction PRL) and then further allocated to the receivers (finished
原文发布于微信公众号 - SAP最佳业务实践（sztunxi）