Ansicht
Dokumentation
DOCU_MIG_ML - Material Ledger Migration
RFUMSV00 - Advance Return for Tax on Sales/Purchases BAL Application Log DocumentationThis documentation is copyright by SAP AG.
The material ledger needs to be migrated in the following scenarios:
- Migration from SAP ERP to SAP S/4HANA
- Migration from SAP Simple Finance to SAP S/4HANA
You always need to migrate the material ledger, even if you were not using the material ledger in the source system.
The process of migrating the material ledger consists of the following activities in the Start and Monitor Migration activity:
- M10: Migrate Material Ledger Master Data
- This activity ensures that the material ledger is activated for all valuation areas, since it is mandatory in SAP S/4HANA. The activity creates material ledger master data (tables: CKMLHD, CKMLPR, CKMLPP and CKMLCR) in all material ledger currencies for periods more recent than the last period of the previous year.
- In addition, all existing inventory aggregate values (tables MBEW, EBEW, QBEW, OBEW) and their complete historic data (tables MBEWH EBEWH, QBEWH, OBEWH) are migrated into the new universal journal entry table ACDOCA. Period records newer than the last period of the previous year are converted into material ledger currencies using the standard exchange rate type. Periods older than the last period of the previous year are only migrated in home currency. During migration, balance carryforward records (fields: BSTAT = ‘C’ and MIG_SOURCE = ‘N’) are created in ACDOCA. If you are already using the material ledger, existing material ledger records (tables CKMLPP and CKMLCR) are transferred into ACDOCA with all existing currency information.
- This migration activity does not activate actual costing, since actual costing is still optional in SAP S/4HANA. However, if you are already using actual costing in the migration source system, ML data for actual costing will be transferred to new data structures to enable fast and efficient cost calculation. In particular, the following database tables will be filled:
| Table Name | Description | Replacement for | Purpose | Remark for Migration |
|---|---|---|---|---|
| MLDOC | Material Ledger Document | MLHD, MLIT, MLPP, MLPPF, MLCR, MLCRF, CKMLPP, CKMLCR, MLCD, CKMLMV003, CKMLMV004, CKMLPPWIP etc. | Optimized data structure for ML actual costing. Will be filled during transactional update of ML data and during ML settlement. | During step M10, data in MLDOC is created from the last period of the previous year to the current period for all valuation areas where actual costing is activated. |
| MLDOCCCS | Material Ledger Document Cost Component Split | MLKEPH, CKMLKEPH, (CKMLPRKEKO) | Optimized data structure for cost component split in ML actual costing | During step M10, cost component split data are created based on MLDOC entries. |
| MLDOC_EXTRACT | Extract of Material Ledger Document | Similar to MLDOC, but contains only information about quantity and value. It is possible to compress this table to one entry per period and cost estimate number via report FCML4H_MLDOC_EXTRACT_COMPRESS. | During migration, one entry is created for each combination of cost estimate number, currency type, period, category, and process category. | |
| MLDOCCCS_EXTRACT | Extract of Material Ledger Document Cost Component Split | - | Similar to MLDOC_EXTRACT but with information per cost component. Tables MLDOC_EXTRACT and MLDOCCCS_EXTRACT will be used especially to calculate information about beginning inventory in specific period, by cumulating quantities and values from all previous periods. | |
| MLRUNLIST | Object List for Costing Run | CKMLMV011, status in CKMLPP | Information about status of materials and activity types in ML costing runs | During migration, table MLRUNLIST is filled based on costing runs created in the start release. |
- Note
- For all ML costing runs created in the start release, the Post Closing step needs to be finished. It will not be possible to process costing runs created earlier in the new release.
- The Posting Logic of the new Actual Costing has been changed in some details. These changes require the following adjustments in the Account Determination (Transaction OBYC or IMG -> Materials Management -> Valuation and Account Assignment -> Account Determination -> Account Determination Without Wizard -> Configure Automatic Postings).
- Transaction PRL (Activity Price Differences):
-
This transaction was introduced with SAP S/4HANA 1610. It is used for the offsetting posting of the
cost center credit posting (Transaction/Account Modification GBB/AUI). Maintain the rules and posting
key for transaction PRL. Then assign the accounts that will receive the activity price differences credited
to the cost centers. From SAP S/4HANA 1610 all activity related postings are performed with valuation class
. It is therefore not necessary to activate the Valuation Modification in the rules of transaction PRL.
- Transaction GBB/Account Modification AUI:
-
From SAP S/4HANA 1610 all activity related postings are performed with valuation class
. If you have activated the Valuation Modification in the rules of transaction GBB, make sure to create an account assignment entry for General Modification AUI and Valuation Class also.
- Transactions PRV and KDV:
-
These transactions are obsolete with SAP S/4HANA 1610 (since the new Actual Costing no longer distinguishes between single-level and multilevel variances).
Their account assignment entries may be removed.
- M20: Check Material Ledger Master Data
- After performing the material ledger master data migration activity, this activity checks and verifies the migrated data. For instance, existing values from the inventory and material ledger tables are compared with aggregation via table ACDOCA.
- Check the error messages. Usually no adjustment is necessary for insignificant errors, such as those from time periods long in the past or from company codes that are not productive. If you have any doubts, discuss them with your auditor. You have the option to accept errors that are not to be corrected After you have accepted all errors, you can continue with the next migration step. If anything was adjusted, you can reset the run and repeat it.
- M11: Migrate Material Ledger Order History
- If the material ledger was not active in any valuation area before SAP S/4HANA conversion, this actvity ensures that all existing purchase order history table records (tables EKBE, EKBEH, EKBZ, EKBZH) and production order history table records (tables MLAUFCR and MLAUFCRH) are converted into the material ledger currencies.
- M21: Check ML Production Order and Purchase Order History
- This activity verifies whether all production and purchase order history records have been converted into the material ledger currencies.
- Note
- If you want to minimize the amount of data to be migrated, archive or delete any data that is no longer needed. This will decrease the migration downtime. The relevant tables are the following:
- Inventory valuation tables: MBEWH, EBEWH, QBEWH, OBEWH
- Material ledger inventory tables (only relevant if material ledger was active before SAP S/4HANA migration): CKMLPP, CKMLCR
- Purchase order history tables: EKBE, EKBEH, EKBZ, EKBZH
- Production order history tables: MLAUFCR, MLAUFCRH
Before migrating the material ledger, you need to complete the following IMG activities under Migration to SAP S/4HANA Finance.
Under Preparations and Migration of Customizing:
- Preparations and Migration of Customizing for General Ledger
- These activities only need to be executed if you are migrating from SAP ERP Business Suite to SAP S/4HANA. If you are already using SAP Simple Finance 2.0 or higher, they are not relevant.
- Preparations and Migration of Customizing for Material Ledger -> Migrate Material Ledger Customizing
- This activity always needs to be executed, even if you are migrating from SAP Simple Finance to SAP S/4HANA.
You also need to implement SAP Notes. For more information, see SAP Note 2345739.
To start the material ledger migration activities, go to Migration to SAP S/4HANA Finance -> Data Migration and start the activity Start and Monitor Data Migration.
For further information, see the documentation on the Start and Monitor Data Migration activity.
Note
The migration activities are parallelized using background jobs. Make sure that enough background jobs are available.
During parallelization, a standard package size of 20,000 is used in all material ledger migration activities. You may adapt this size by setting user parameter FML_MIG_PKG_SIZE.
ABAP Short Reference General Data in Customer Master
This documentation is copyright by SAP AG.
Length: 11632 Date: 20240523 Time: 154322 sap01-206 ( 183 ms )
