Monday, 15 July 2019 03:01

Performance Improvement in Material Ledger Closing Cockpit of SAP

Written by
Rate this item
(0 votes)

Ashish Sampat 2018 12 1Many SAP installations experience large run-times during material ledger close. This blog will explain a function that can help expedite Material Ledger close.

Knowing

how much a product costs is essential to determining the actual profitability of a product. Yet most decisions are based on the standard cost of the product, given that it is not always easy to get an accurate picture of the actual cost. Actual costing functionality provided by the material ledger component of SAP Controlling bridges this gap. It provides the ability to capture actual costs by tracking variances at the material (product) level. This section provides an overview of actual costing in SAP Material Ledger.


1.1.1 Actual Costing with Material Ledger

SAP Material Ledger inventory valuation includes the following:

  • Collecting actual data during the month.
  • Determining price: single-level and multi-level prices are determined based on the type of transactions performed.
  • Calculating periodic unit prices at the end of the month.

SAP Material Ledger collects material movement data throughout the month and keeps track of which materials were used for the production of specific goods in production/process orders.

The SAP Materials Management module (in combination with the FI module) tracks goods movements and their values at standard cost, while the SAP Material Ledger tracks goods movement values at standard and actual costs. In other words, SAP Material Ledger can be considered a second set of books where each material has a record of all goods movements for actual valuation.

save 400 head banner

1.1.2 Material Ledger closing cockpit

The SAP Material Ledger closing cockpit is run every month to perform actual costing using transaction code CKMLCP. The menu path is as follows: AccountingControllingProduct Cost ControllingActual Costing/Material LedgerActual CostingCKMLCP—Edit Costing Run.

The first step is to create a costing run and assign relevant plants. After selecting plant(s), the Material Ledger closing cockpit requires several steps as shown in Figure 1.1

Webp.net resizeimage 8

Figure 1.1: CKMLCP — SAP Material Ledger closing cockpit process steps

  1. Selection: all materials for the given plants are selected.
  2. Sequence Determination: the sequence of costing is established, starting with the lowest level material and going all the way up to the highest-level material and goods movements.
  3. Single-Level Price Determination: prices are calculated for each material.
  4. Multi-Level Price Determination: prices are calculated for the entire production stream.
  5. Revaluation of Consumption: adjustment posting of actual costs at month end, where all variances are transferred to the receiving object (which can be a material, cost center, internal order, GL Account, etc., depending on where the original consumption occurred).
  6. Post-Closing: all calculations performed in prior steps are posted during this step.
  • Multi-level price differences are transferred to the next level.
  • Revaluation of consumption is posted to cost objects.
  • Inventory is revalued in FI for the period being closed.
  1. Mark Material Prices: this step is optional. An organization may decide not to use the periodic unit price as a standard for the upcoming month. If so, this step is skipped, and the system uses the standard price for goods movements and revalues at the periodic unit price only at month-end.

1.1.1 Performance improvement with parallel processing

Large run times and low system performance may become the norm, given that Material Ledger processes large amounts of data in the closing cockpit. Parallel processing can be used to address this performance concern.

As shown in Figure 1.2, there is an option to run Material Ledger close steps on multiple servers at the same time.

Webp.net resizeimage 7

Figure 1.2: CKMLCP – ML Close: Parallel processing on multiple servers

This feature is often referred to as parallel processing. As seen at the bottom of the screen, server group “parallel_generators” has been selected, with the additional selection of maximum number of parallel processes as 10. This would mean that, instead of the usual single server, this job would be executed in parallel on 10 servers. This would imply that there could be a significant (at times, 85-90 percent) performance improvement for this job.

Parallel processing setup requires collaboration with the BASIS team in your organization.

Copyright acknowledgement: This blog was created based on information that was originally published by Espresso Tutorials GmbH as one of many tips in Expert tips to Unleash the Full Potential of SAP Controlling, authored by Ashish Sampat

About the author: Ashish Sampat is an SAP FI/CO Consultant who has provided solutions in SAP Controlling including product costing, material ledger, and cost center accounting to global clients in consumer packed goods, life sciences, and industrial sectors. Ashish is based in Chicago region, where he works as an independent SAP FI/CO consultant. A recipient of Controlling Community Award for 2017, Ashish is the author of First Steps in SAP Controlling (CO) and Expert tips to Unleash the Full Potential of SAP Controlling.

Read 191 times

Leave a comment

Make sure you enter all the required information, indicated by an asterisk (*). HTML code is not allowed.