Written by Takanashi — Paddy & Water Inc. / Finance & Controlling

Part One: Cost Management

Design and Practice of Product Cost Planning, Production Order Cost Management, and Actual Costing

June 2026

Introduction: The Blind Spot of Companies Where Cost Is “Invisible”

In manufacturing, cost information — “how much does it cost to make which product” — is fundamental management information underlying pricing strategy, product portfolio decisions, capital investment evaluation, and cost reduction activities. However, at many companies there is a large gap between the cost recorded in the accounting system and the sense of cost on the shop floor, leading to problems such as “the system shows a profit, but no cash remains” or “we know a particular product’s profitability is poor, but we cannot prove it with numbers.”

The root cause of this problem lies in the “structural looseness of cost accounting.” Overhead allocation relies on simple, fixed annual ratios, so it fails to properly reflect changes in the product mix. Actual costs of production orders are not compared against standard costs, and the causes of variances are absorbed into profit and loss without being identified. Under such conditions, it is difficult to pinpoint targets for cost reduction activities or to build a solid basis for price revisions.

SAP S/4HANA’s Controlling (CO) module — and in particular Product Cost Controlling (CO-PC) — provides an integrated framework for precisely managing product cost through a “plan → actual → variance analysis” cycle. Under the integrated financial and management accounting architecture of the Universal Journal (ACDOCA), it achieves unified management of cost information, from the accumulation of cost center expenses, through the collection of actual costs on production orders, to actual costing by product (Actual Costing). This article systematically explains the overall picture of cost management as well as the technical configuration and operations involved.

1. The Overall Picture of SAP Controlling (CO) and the Universal Journal

The Structure of the Controlling (CO) Module

SAP S/4HANA Controlling (CO) is a group of modules that provides internal management information for a company, integrated with Financial Accounting (FI). The main components of CO are as follows.

• Cost Center Accounting (CCA): the function that collects and allocates overhead costs to organizational units (cost centers).

• Product Cost Controlling (CO-PC): the function that manages product cost planning (standard cost roll-up), the collection of actuals by production order, and actual costing. This is the subject of this article.

• Internal Order: an internal management account used as the object for collecting individual costs for projects, campaigns, capital investments, and the like.

• Profitability Analysis (CO-PA): the function that manages profit and loss by segment, such as product, customer, and region.

• Profit Center Accounting (PCA): the function that manages profit and loss and the balance sheet by business unit or business segment.

Universal Journal (ACDOCA): The Integration of Financial and Management Accounting

The greatest architectural innovation of SAP S/4HANA is the introduction of the “Universal Journal.” The Universal Journal is implemented in the ACDOCA (Accounting Document Items Universal Journal Entry Line Items) table, which integrates into a single table the journal entries and line items of Financial Accounting (FI) and Controlling (CO) that previously existed separately.

In legacy SAP (ECC), postings for Financial Accounting (FI) and postings for Controlling (CO) were dually managed in separate tables, requiring periodic reconciliation work to confirm consistency. With the Universal Journal in S/4HANA, a single posting is recorded only once in ACDOCA, and from there views are generated for each purpose — financial, managerial, and analytical. This structurally eliminates the classic problem of “discrepancies between FI and CO.”

Each line item in ACDOCA carries, in addition to the “G/L account (the financial accounting key),” management accounting dimensions such as “cost center, profit center, cost object, profitability segment, and project,” and all costs and revenues are posted in real time to these management accounting dimensions as well.

2. What CO-PC Can and Cannot Do

What It Can Do: The Strengths of SAP CO-PC

SAP CO-PC’s greatest strength lies in its ability to automatically execute cost roll-ups for complex products with multi-level BOMs. Here we organize the main capabilities that have been confirmed in practice, from standard costing through to actual costing.

Multi-Level BOM Explosion and Roll-Up of Standard Cost (CK11N / CK40N)

For a multi-level BOM structure of purchased parts → semi-finished goods → finished goods, SAP fully and automatically explodes down to the lowest-level purchased parts and rolls up cost elements (material cost, conversion cost, overhead) hierarchically. Even for precision machinery or automotive parts with BOM hierarchies hundreds of levels deep, automatic roll-up is possible, and standard costs for all items can be calculated in a single mass run (CK40N: mass processing of cost estimates) without manual intervention by staff.

Breakdown Management Through the Cost Component Structure

The ability to hold and analyze roll-up amounts by Cost Component — such as “material cost, machining cost, labor cost, subcontracting cost, manufacturing overhead, and design cost” — is extremely effective in clarifying which area (materials, processes, or overhead) should be targeted for cost reduction. This breakdown can be referenced consistently across standard cost reports, variance analysis, and actual costing alike.

Breakdown of Variance Categories at the Production Order Level

Automatic decomposition into six categories — “quantity variance (excess or shortfall in usage), price variance (fluctuation in procurement price), activity variance (excess or shortfall in processing time), resource-usage variance (use of substitute parts), mix variance, and remaining variance” — generates information that directly answers the management question of “what caused the cost overrun.” In ECC there were cases where equivalent variance decomposition required additional customization, but in S/4HANA it is provided as standard functionality.

Multi-Level Roll-Up of Actual Cost Using the Material Ledger (ML)

In monthly actual costing (CKMLCP), the ability to roll up the price variance of purchased materials, multi-level, to higher-level products and calculate “actual cost by product” is especially effective for materials-intensive manufacturers, chemical companies, and food companies where material price fluctuations are large. It tracks the gap between standard and actual price broken down into “Material Price Variance, Exchange Rate Variance, and Other Variances,” greatly improving the accuracy of inventory valuation in financial reporting.

An Approximation of Activity-Based Costing

By precisely defining cost centers and setting up multiple activity types (machine hours, labor hours, setup hours, quality inspection hours, etc.), it is possible to achieve an allocation of costs that approximates ABC. Using the combination of cost center × activity type, it is possible to track, on an activity basis, which products consume which resources and by how much. However, there are also the constraints described below.

What It Cannot Do: Constraints

CO-PC is powerful, but there are constraints and things it “cannot do” that should be understood before implementation. Implementing without recognizing these will create a gap between expectations and reality.

True Activity-Based Costing (ABC) Is Not Possible

SAP’s CO-PC allocates costs in the flow “cost center → production order → product,” but it is not possible to fully achieve true, end-to-end ABC — defining business activities such as “order processing,” “quality inspection,” and “design change,” and allocating them to products using consumption-based drivers — using SAP standard functionality alone. True ABC requires additional design work (defining custom activity drivers, complex CO-PA allocations, etc.), which entails significant consulting effort.

Automatic Allocation of Shared Resource Costs Across Multiple Make-to-Order (MTO) Projects

When multiple sales orders share the same production equipment or personnel, it is difficult, using SAP standard functionality, to accurately attribute “how much equipment a given order consumed” to that individual order. Because this relies on the practice of entering actual hours by order through Confirmation, if shop-floor workers do not have a culture and operational discipline of accurately recording work hours by order, the accuracy of cost attribution by order will decline.

Constraints of Material Ledger Actual Costing and Parallel Valuation

Activating the Material Ledger enables Parallel Valuation of standard cost and actual cost, but when different valuation approaches must be maintained simultaneously for different accounting standards (IFRS, Japanese GAAP, US GAAP), the configuration of Ledger Groups becomes complex. In particular, for companies that operate multiple ledgers — such as an “IFRS ledger (supporting lease standards ASC 842 / IFRS 16)” and a “ledger for corporate tax purposes” — the design effort for ML configuration increases substantially.

Limits to the Flexibility of the Costing Sheet

A costing sheet that allocates overhead using an overhead rate (a percentage rate or a fixed amount) is simple to configure, but has limited flexibility for the purpose of “precisely allocating actual factory overhead to products.” In particular, the constraint that “the allocation basis must be designed on a cost-amount basis rather than an activity-quantity basis” can cause overhead cost distortion at companies with a complex product mix. In such cases, consider refining the activity-type settings of the cost center, or reconsider allocation via reclassification at the CO-PA level.

The Scope of Impact of Mid-Year Changes to Standard Cost

If the standard cost is changed partway through the fiscal year (CK11N → re-release via CK24), the new standard cost applies to production orders created after the change, but production orders that were already started before the change remain at the old standard cost. In situations where mid-year changes occur multiple times, managing “which order is costed under which version of the standard cost” becomes complex. It is important, in principle, to limit standard cost changes to once at the beginning of the fiscal year, or to design a change-freeze period in advance.

Constraints Specific to Process Orders

When using Process Orders (PI: process orders) for batch manufacturing in chemicals, pharmaceuticals, or food, integration settings with PP-PI (Process Industries) are required. The cost roll-up of the “Master Recipe,” which corresponds to a routing, depends on PP-PI settings, and requires a Costing Variant and Quantity Structure different from those of standard PP. It is important to confirm PP-PI-specific cost settings before implementation.

Monthly Closing Processing for WBS Elements and Project Cost

When a WBS element in a PS project (PS: Project System) is used as the cost object, settlement and closing processing different from that of production orders are required. The handling of “Construction in Progress” for incomplete projects, capitalization after project completion, and management of “Unbilled Revenue” at period-end make PS-CO integration design complex. Companies that mix CO-PC and PS-CO designs require specialized consulting.

3. Product Cost Planning (CO-PC): Rolling Up Standard Cost

What Is Standard Cost

Standard Cost is “an estimate of the cost required to manufacture one unit of a product under ideal production conditions.” Standard cost is the starting point of product cost management, and functions as the basis for comparison with the actual cost of production orders (variance analysis), inventory valuation, and profit planning.

In SAP CO-PC, the standard cost of a product is calculated as a “Cost Estimate.” A cost estimate explodes the BOM and routing linked to the material (product) and rolls up “raw material cost (price × quantity of BOM components) + conversion cost (routing operation time × work center cost rate) + overhead (overhead rate)” to calculate the cost of one unit of the product.

The Calculation Structure of the Cost Estimate

The cost roll-up of a cost estimate is executed at the following levels.

• Raw material cost: for each component in the BOM item, this is calculated as “unit quantity × standard purchase price (managed via MR21, or the moving-average price at goods receipt).” For multi-level BOMs, the calculation explodes down to and rolls up from the lowest-level purchased components.

• Conversion cost: for each operation in the routing, this is calculated as “standard time (setup, execution, machine) × the work center’s cost rate (planned activity price: KP26).” The breakdown is held by the work center’s cost category (labor cost, machine cost, energy cost).

• Overhead: overhead is added by multiplying the total of the product’s material cost and conversion cost by the allocation rate defined in the Costing Sheet (Overhead Sheet). Example: it is set up in a form such as “manufacturing overhead = 15% of direct material cost.”

A View of the Operation: Creating a Cost Estimate in CK11N

• Launch CK11N (Create Material Cost Estimate). Enter the material number, plant, costing variant (a standard costing variant such as “PPC1”), the quantity structure date, and the costing date.

• When executed (F8), SAP automatically explodes the BOM and performs the cost roll-up. The results screen displays “raw material cost, conversion cost, overhead, and total cost” broken down by cost element.

• The “Cost Component View” tab displays the breakdown by cost component — “material cost, machining cost, labor cost, subcontracting cost, and manufacturing overhead” — allowing you to see which cost driver is the largest.

• Using CK24 (Release Cost Estimate), the cost estimate is marked and released as the material master’s “standard cost” (Moving Average Price or Standard Price). The released standard cost is then used for subsequent inventory valuation and as the planned cost for production orders.

4. Production Order Cost Management: Collecting Actuals and Variance Analysis

Production Orders and Cost Objects

A Production Order is both an instruction to manufacture a specific material in a specific quantity by a specific date, and at the same time a “Cost Object” that collects the costs incurred in that manufacturing. The “actual material cost input, actual equipment time consumed, and actual subcontracting cost incurred” for a production order are posted and collected as actual costs.

The Routes Through Which Actual Costs Are Collected

Actual costs are automatically posted to a production order through the following business events.

• Goods Issue (GI): through the picking of components on the shop floor (MB1A/MIGO), raw material inventory decreases and is posted to the production order as material cost. The posted amount is “issue quantity × moving average price (or standard cost).”

• Confirmation (CO15/CO11N): the actual working time for each operation (actual setup time, actual machine time, actual labor time) is entered via confirmation. The entered actual time is multiplied by the work center’s actual activity price and posted to the production order as conversion cost.

• Subcontracting: for operations sent out to subcontractors, when the invoice for the subcontract purchase order is recorded, the subcontracting cost is posted to the production order.

• Overhead Calculation (CO43 Actual Overhead Calculation): as a period-end process, overhead is allocated by multiplying the total of actual raw material cost and conversion cost by the actual rate in the costing sheet.

Variance Analysis: The Gap Between Planned Cost and Actual Cost

The difference between a production order’s “planned cost (standard cost × order quantity)” and its “actual cost (the costs actually collected)” is called a “Variance.” SAP CO-PC’s variance calculation (KKS1/KKAO) automatically decomposes the variance into the following categories.

• Quantity Variance: the variance arising because the actual input quantity differs from the planned quantity. Example: 100g of material was planned as the standard, but 110g was actually used.

• Price Variance: the difference between the actual purchase price and the standard cost. For material cost, this is captured here when moving-average inventory valuation is used.

• Resource-Usage Variance: the variance that arises when a component other than the one defined in the BOM is substituted.

• Activity Variance: the variance that arises because the actual working time differs from the standard time.

A View of the Operation: KKS1 Variance Calculation and Checking Results

• Launch KKS1 (Production Order Variance Calculation). When executed with the plant, period, and fiscal year specified, the variances for all production orders in the target period are calculated in a single run.

• Double-clicking an order in the results list displays the “Variance Categories” screen, where you can check a breakdown such as “quantity variance: -¥3,200, price variance: ¥1,800, activity variance: -¥1,500.”

• Variances are transferred to CO-PA or to the variance accounts in Financial Accounting through SETTLEMENT (order settlement) and are recorded in the monthly profit and loss.

5. Actual Costing (Actual Costing / Material Ledger)

The Limits of Standard Costing and the Need for Actual Costing

Standard costing is effective from the standpoint of managing variance against the plan, but it is insufficient for grasping the precise actual cost by product — that is, “how much it actually cost to make that product.” In industries where material prices fluctuate significantly (chemicals, energy, food, etc.), the gap versus standard cost widens, creating a large discrepancy between the standard-cost valuation of inventory and the actual procurement cost.

SAP S/4HANA’s “Material Ledger (ML)” is the foundation for actual costing. ML records all goods movement transactions for materials in detail, and by executing an “Actual Costing Run” at period-end, it precisely calculates the actual cost of a product, tracing back down to its lower-level components.

How the Material Ledger (ML) Works

ML accumulates the variance against standard cost (price variance, exchange rate variance, etc.) by material and plant. In the period-end Actual Costing Run (CKMLCP: Execute Actual Costing), this variance is allocated to products according to the following rules.

• Step 1 — Single-Level Price Determination: for each purchased material, the “actual average procurement price during the period” is calculated. Even if the purchase unit price fluctuated multiple times, a weighted average for the period is calculated.

• Step 2 — Multi-Level Roll-Up: the actual price variance of purchased materials is rolled up in stages to higher-level semi-finished and finished goods. A chain calculation is executed across the entire BOM hierarchy such that, “if the actual price of Component A was 3% higher than standard, that 3% is added to the actual cost of the finished good that uses Component A.”

• Step 3 — Valuation of Inventory at Actual Price: the period-end inventory balance is revalued at actual cost (actual price valuation of inventory). This brings the inventory valuation in the financial statements closer to a more accurate actual cost.

A View of the Operation: Executing Actual Costing in CKMLCP

• CKMLCP (Execute Actual Costing) is run at month-end. The company code, plant, period, and fiscal year are specified.

• Execution steps: run in the order “1. Close Periods for Inventory Costing” → “2. Single-Level Price Determination” → “3. Multi-Level Price Determination” → “4. Post Closing Entries.” Each step is checked beforehand in simulation mode before being run for production.

• After execution, check the actual cost by product and by cost element in CKMLDUMP (the actual costing results report). The variance from standard cost is displayed broken down by cost component (material cost, conversion cost, overhead).

6. Make-to-Order (MTO) Cost Management

The Special Nature of Cost Management in Make-to-Order

Under the Make-to-Order (MTO) approach, product specifications differ for each customer order, and setting a standard cost at the product level can be difficult or inappropriate. For make-to-order production of custom items, large-scale equipment, plants, and the like, managing profitability by individual order — “how much did this particular order actually cost” — is the most critical issue.

In SAP’s MTO cost management, a “Sales Order Line Item” or a “Project (PS)” is set as the cost object, and all costs linked to that order (manufacturing cost, procurement cost, subcontracting cost, design cost) are collected by order. Profitability by order is calculated with “Revenue and Cost” linked at the time revenue is recognized, making it possible to accurately grasp the profit margin for each order.

Configuration of Sales Order Costing

• Requirement Class (transaction OVZG): controls whether a sales order line item becomes a cost object, and the inventory valuation approach (order-specific stock vs. anonymous stock). MTO cost management uses a requirement class with Cost Collection enabled.

• Costing Variant: sets the standard costing variant used for the cost estimate of the sales order line item. By defining an MTO-specific variant (for example, SMTO), an individual cost estimate reflecting the order quantity and specification changes of the order line item is possible.

7. Collecting and Allocating Overhead to Cost Centers

Integration with Cost Center Accounting

Product Cost Controlling (CO-PC) is closely integrated with Cost Center Accounting (CCA). Manufacturing overhead (factory administration cost, equipment maintenance cost, quality control cost, etc.) is first collected in cost centers (for example, Manufacturing Department 1, Maintenance Department, Quality Control Department), and from there is incorporated into product cost through allocation to production orders and the setting of activity prices.

The transfer of cost from a cost center to a production order takes place through “Activity Allocation.” In a manufacturing department’s cost center, activity types such as “Machine Hours” and “Direct Labor Hours” are defined, and a “Planned Activity Price” is calculated from the planned activity quantity (set via KP26) and the planned cost center cost. This planned activity price is used as the “conversion cost unit rate” in the standard cost roll-up of the production order.

A View of the Operation: KSPI — Calculating the Actual Activity Price

• KSPI (Calculate Actual Activity Price): performed at period-end. It calculates the “actual activity price” by dividing the cost center’s actual cost by the actual activity quantity.

• The difference between the planned activity price (the value set in KP26) and the actual activity price is captured as an “activity price variance” and reflected in the variance analysis of the production order.

8. Cost Planning and Budget Management

Cost Center Planning (KP06): Expense Planning

In the annual planning process, cost planning for each cost center is entered in KP06 (Planning of Primary Cost Elements). Planned costs are entered by the combination of cost center × cost element (G/L account) × period, and the planned activity price is derived by combining this with the planned activity quantity (KP26).

Planned cost is entered broken down into “Fixed Cost” and “Variable Cost.” Variable cost varies in proportion to the activity quantity (production volume), while fixed cost remains constant regardless of activity quantity. This breakdown determines the accuracy of break-even analysis in Marginal Costing.

Budget Management and Commitment Management

SAP’s “Availability Control” is used for budget management of internal orders and projects. Once a budget amount is set on an order, when costs are incurred (recorded as a “Commitment” as soon as a purchase order is created), the budget used and the remaining budget are managed in real time. When the budget is exceeded, warnings or errors can be configured to block processing, automating governance of budget compliance.

9. Cost Analysis Reports: Providing Information to Management

The Main Reports for Product Cost Analysis

The cost information collected by CO-PC is referenced through the following analysis reports.

• KKBC_ORD (Production Order Cost Analysis): displays a specific production order’s planned cost, actual cost, and variance broken down by cost element. You can drill down to the details of the material input and working time that caused a variance.

• S_ALR_87013139 (Product Cost Analysis Report): displays a list of standard cost, actual cost, and variance by product, given a specified material, plant, and period. Used to identify high-variance products and select priority improvement targets.

• CKMLQS (Material Ledger Cost Element Details): checks, from ML’s actual costing data, the actual cost breakdown of a material (actual values of raw material cost, conversion cost, and overhead).

Fiori Analytics: Real-Time Cost Dashboards Through SAC Integration

CO-PC data in S/4HANA can be analyzed in real time via a Live Connection to SAP Analytics Cloud (SAC). By visualizing trend analysis of profit margin by product, factor analysis of cost drivers, and comparison of plan-versus-actual variance by region or product group in stories within SAC, cost information can be connected directly to management decision-making.

10. Case Studies from Other Companies

Case 1: Chemical Manufacturer Company A — Adoption of Material Ledger Actual Costing

Background and Challenges

Company A, a chemicals manufacturer, faced large price fluctuations in raw materials (petroleum-based feedstocks, solvents, etc.), such that the standard cost set at the beginning of the fiscal year would diverge greatly from reality within a few months. Under standard-cost inventory valuation, the impact of price fluctuations was reflected all at once in profit and loss at period-end, causing large swings in the monthly profit margin, which prevented timely management decisions.

Adoption of ML Actual Costing and Results

Company A introduced SAP S/4HANA’s Material Ledger (actual costing) and implemented a monthly actual cost roll-up. Through the monthly Actual Costing Run, the impact of raw material price fluctuations came to be reflected immediately in the monthly product cost. It is reported that the company became able to accurately grasp the actual profit margin by product on a monthly basis, and that the accuracy of judgments on the need for and timing of price revisions improved significantly.

Case 2: Precision Parts Manufacturer Company B — Refining Production Order Variance Analysis

Background and Challenges

At Company B, a mass producer of precision parts, the production department’s manufacturing efficiency was not being properly reflected in the accounting cost figures, and a contradiction persisted between the shop floor’s sense that “productivity is improving” and the accounting data showing that “cost has not improved.” Unable to identify the causes of the variance, the company could not prioritize improvement activities, nor verify the effectiveness of improvement investments.

Refining CO-PC Variance Analysis and Results

Company B revised its CO-PC variance category settings and established an operation to calculate “quantity variance, price variance, activity variance, and resource-usage variance” monthly at the production order level. By visualizing variance trends by work center and by material category in an SAC dashboard, the company identified the processes primarily responsible for the variance (processes with low equipment utilization, processes with high material loss). It is reported that, through pinpointed improvement activities, the company was able to improve the manufacturing cost of the target products.

11. Next-Generation Cost Management: AI and Predictive Costing

Extensions from S/4HANA 2023 Onward

Releases of SAP S/4HANA from 2023 onward have added the following extended functions in the area of cost management.

• Predictive Accounting: a function that calculates, in real time and before a production order is complete, an “Expected Actual Cost” — a projected final cost based on the actual pace to date. It allows you to grasp the projected final cost when an order is, for example, 50% complete, enabling early warning of cost overruns.

• AI-based Cost Estimate: using machine learning, this estimates an approximate cost from the cost patterns of similar materials even at a stage before the BOM is finalized (the early design stage). It supports design decisions that take profitability into account from the earliest stages of product development.

12. An End-to-End Transaction Operations Guide, From Setting Standard Cost to Variance Analysis

This chapter explains, as a flow of transaction operations, the full cycle of cost management: “setting the standard cost at the beginning of the fiscal year → collecting actuals on production orders → allocating overhead → calculating variances → settlement → Material Ledger actual costing.” It clarifies “what, when, and through which transaction” each person responsible performs within the monthly and annual cycle.

Step 1: Beginning of the Fiscal Year — Setting the Planned Activity Price (KP26)

The starting point of the cost management cycle is setting the “Planned Activity Rate.” The planned activity price is the “rate per machine hour and per labor hour” used in the conversion-cost roll-up of production orders.

A View of the Operation: Entering the Planned Activity Price in KP26

• Launch KP26 (Activity Planning). Enter the version (“0” is the standard plan), the period (01–12), the fiscal year, the cost center, and the activity type (for example, MAH01: machine hours, LAB01: labor hours).

• In the grid at the bottom of the screen, enter “Planned Fixed Cost,” “Planned Variable Cost,” and “Plan Activity Quantity.” Example: Manufacturing Department 1, machine hours, planned fixed cost = ¥12,000,000/year, planned variable cost = ¥0, planned activity quantity = 6,000 hours.

• Running KSPI (Calculate Planned Activity Price) automatically calculates “planned activity price = total planned cost ÷ planned activity quantity = ¥12,000,000 ÷ 6,000h = ¥2,000/h.” This ¥2,000/h is then used as the conversion-cost unit rate for the roll-up in CK11N.

• KPSI (Allocation of Auxiliary Cost Centers): performs the planned allocation from indirect departments (maintenance, quality, logistics, etc.) to the manufacturing department cost center. After the planned allocation, KSPI is re-run against the resulting total cost center cost to finalize the final planned activity price.

Step 2: Beginning of the Fiscal Year — Creating and Releasing Cost Estimates (CK11N / CK40N / CK24)

Once the planned activity price has been finalized, calculate and release the cost estimate for each product to set the standard cost in the material master.

A View of the Operation: Running a Mass Cost Estimate in CK40N

• Launch CK40N (Edit Costing Run). Specify the plant, costing variant (PPC1), material selection criteria (material group, planner group, etc.), and the costing date, and run “Create” for the cost estimate.

• SAP explodes the BOM for all target materials, serially or in parallel, and performs the cost roll-up. After completion, check the “error log” for errors such as “materials with no BOM registered, materials with no routing set up, and purchased materials with no price set.”

• Correct and recalculate the materials in error individually in CK11N. Most errors are caused by “the standard price of a purchased item not being set (MR21)” or “the activity type of a work center not being set.”

• The “Mark” step in CK40N: marks the cost estimate in the material master as the “Future Standard Cost.” At this point the current standard cost has not yet changed.

• The “Release” step in CK40N, or an individual CK24: releases the marked future standard cost as the “Current Standard Cost.” Simultaneously with release, an inventory revaluation journal entry (posting the difference from the standard cost change to a valuation-difference account) is automatically executed.

Step 3: During the Production Month — Collecting Actual Costs on Production Orders

During the production month, actual costs are automatically collected on production orders through business transactions. Here we show the main transactions that a cost management person in charge should check.

Goods Issue (MB1A / MIGO) — Collecting Material Cost

• Record the issue of components to a production order using MB1A (Goods Withdrawal from Stock) or MIGO (Goods Movement). Use movement type “261 (Goods issue to production order).”

• Simultaneously with posting, a journal entry of “Inventory account Cr / WIP (work in process) account Dr” is automatically generated, and the material cost is collected on the production order. The posted amount is “issue quantity × the material’s moving average price (or standard cost).”

Confirmation (CO11N / CO15) — Collecting Conversion Cost

• Enter the actual time for each operation of the production order in CO11N (Confirmation). Enter “actual setup time, actual machine time, and actual labor time.”

• Simultaneously with saving the confirmation, an amount equal to “actual time × planned activity price” is posted to the production order as conversion cost. At this point the planned activity price is used; the variance is corrected at period-end using the actual activity price (revaluation).

Overhead Calculation (CO43) — Collecting Overhead

• CO43 (Actual Overhead Calculation): run as a period-end process. When executed with the plant, period, and production order selection range specified, overhead is calculated and posted by multiplying the “total actual material cost and actual conversion cost” of the target production orders by the rate set in the costing sheet.

• Run CO43 first in simulation mode (Test Run) to check the overhead calculation results before executing it for production. If there are errors, check the costing sheet settings (KSH1/KZS2).

Step 4: Month-End — Allocating Cost Center Variances (KSU5 / KSV5)

At month-end, the actual costs collected in cost centers are allocated to receiving accounts such as production orders and CO-PA. Any cost remaining in a cost center becomes a variance against the activity allocation to production orders (actual time × planned activity price).

A View of the Operation: KSU5 — Actual Assessment

• KSU5 (Execute Actual Assessment Cycle): allocates the cost center costs of indirect departments (maintenance, quality, factory administration, etc.) via an allocation cycle to manufacturing department cost centers or to CO-PA segments.

• The allocation cycle is predefined in KSU1 (Define Assessment Cycle). Select an allocation basis (allocation key) such as “fixed percentage, planned activity quantity ratio, or production quantity ratio.”

• KSV5 (Actual Distribution): allocates cost center cost while retaining the original cost element (G/L account) (whereas Assessment consolidates the cost elements into a single “allocation cost” element, Distribution retains the breakdown by cost element). Which to choose depends on management accounting policy.

Step 5: Month-End — Variance Calculation (KKS1) and Settlement (CO88 / KO88)

A View of the Operation: Running Production Order Variance Calculation in KKS1

• KKS1 (Production Order Variance Calculation): calculates the variance for all production orders in a single run given the plant and period. Variance calculation is a prerequisite for CO88 (settlement), so KKS1 must always be run first.

• After running KKS1, check the variance breakdown by order in KKBC_ORD (Production Order Cost Analysis) or KKBC_PKO (Product Cost Details). For orders where the variance is unusually large, investigate the cause (excess material input, incorrect entry of working time, incorrect costing sheet configuration, etc.).

A View of the Operation: CO88 — Production Order Settlement

• CO88 (Collective Settlement of Production Orders): given the plant and period, executes settlement for all production orders in a single run. Settlement is a mandatory month-end process that transfers the costs (including variances) collected on a production order to its settlement receiver.

• Configuring the settlement receiver: the settlement rule of a production order (KO02 → the “Settlement” tab) defines the “settlement receiver category and settlement receiver (product stock, CO-PA segment, variance account).” A mass-production production order is typically settled to “product stock (Material: PRD),” with the variance settled to a CO-PA segment.

• Checking after running CO88: confirm in the CO88 execution log that all orders show status “Settled.” For unsettled orders (status “In Process” or “Released (incomplete)”), drill down to check the cause (for example, quantity confirmation not yet complete, or zero cost).

• KO88 (Internal Order Settlement): settlement of internal orders (R&D expense, capital investment expense, etc.) is executed via KO88. The operation is similar to CO88, but differs in that the settlement receiver is a “fixed asset, profitability segment, or cost center.”

Step 6: Month-End — Actual Activity Price Revaluation (KSII)

The conversion cost posted to a production order during the production month was calculated as “planned activity price × actual time,” but after the cost center’s actual cost is finalized at month-end, the “actual activity price” is calculated and the difference is additionally posted to the production order (revaluation: KSII).

A View of the Operation: Revaluation at Actual Activity Price in KSII

• KSII (Revaluation at Actual Activity Prices): at period-end, allocates the difference between the actual activity price calculated in KSPI and the planned activity price, in proportion to the actual activity quantity, and additionally posts it to each production order.

• Through this revaluation, “the conversion cost variance caused by the difference between the planned and actual activity price” is collected on the production order. This variance is classified as “Activity Price Variance” in the subsequent KKS1 variance calculation.

• KSII is run before CO88 settlement (so that the variance after revaluation can be settled by CO88).

Step 7: Month-End — Material Ledger Actual Costing (CKMLCP)

Companies that have implemented the Material Ledger (actual costing) run CKMLCP at month-end to finalize the actual product cost. CKMLCP is run after CO88 settlement (so that ML also incorporates the production order variances after settlement is complete).

A View of the Operation: Running the Actual Costing Run in CKMLCP

• CKMLCP (Execute Actual Costing): specify the company code, plant, period, and fiscal year. Before running, check the execution prerequisites (such as the resolution of all ML messages) in CKMLSTAT (Check ML Status).

• Step 1, “Close Periods for ML”: closes the current period’s ML records and prepares for carryforward to the next period.

• Step 2, “Single-Level Price Determination”: calculates the actual (weighted-average) procurement price during the period for each material. The price variance of purchased items is finalized here.

• Step 3, “Multi-Level Price Determination”: rolls up the price variance of purchased items to higher-level semi-finished and finished goods, calculating the actual cost of the finished goods. A chain calculation spanning the entire BOM hierarchy runs in the background.

• Step 4, “Post Closing Entries”: posts to Financial Accounting the revaluation difference from valuing inventory at actual cost. It is only once this step is executed that the impact on Financial Accounting is finalized. Always verify the amounts in simulation (Test Run) before executing for production.

• CKMLQS (Check ML Line Items): after CKMLCP completes, use CKMLQS to check the actual cost breakdown by material (a comparison of the actual and standard values of raw material cost, conversion cost, and overhead).

Summary of the Monthly Cost Management Cycle

Organizing the end-to-end flow above into a monthly calendar, the standard monthly closing sequence is: “During the month: goods issue (MB1A/MIGO), confirmation (CO11N) → Month-end (1): overhead calculation (CO43) → Month-end (2): cost center allocation (KSU5/KSV5) → Month-end (3): actual activity price revaluation (KSII) → Month-end (4): variance calculation (KKS1) → Month-end (5): production order settlement (CO88) → Month-end (6): ML actual costing (CKMLCP).” Because there are dependencies between each step, it is important to follow this order.

13. SPRO Configuration Guide

This chapter organizes the main SPRO configuration items for cost management (CO-PC). Each setting is explained from the perspective of “what you configure, and what becomes possible or what changes as a result.”

13-1. Controlling Area Configuration (OKKP)

The Controlling Area is the top-level organizational unit of SAP Controlling. In OKKP, you configure the basic settings of the controlling area (fiscal year variant, currency type, CO version management, etc.).

• OKKP “Maintain Controlling Area”: defines the “Chart of Accounts,” “fiscal year variant (for example, V3: 12 months starting in April),” and “controlling area currency (for example, JPY)” used in Controlling. A controlling area can encompass multiple company codes.

• OKKP “Activate Components”: activates each component — CCA (Cost Center Accounting), CO-PC, CO-PA, and PCA. Components that are not activated cannot be used. In particular, activation of ML (Material Ledger) is done not here but separately, via “MRN1: Activate Material Ledger.”

• OKKO “Maintain CO Versions”: defines the attributes of a planning version (with “0” being the base planning version) — the copy validity period, whether allocation planning is permitted, the variance version, and so on. If you manage multiple planning scenarios (optimistic, base, pessimistic) as separate versions, create the additional versions here.

13-2. Costing Variant (OKKN / OKKFx)

The Costing Variant is the “set of calculation parameter settings” used in the cost estimate calculations of CK11N and CK40N. It consists of three elements: the valuation variant (with what price the cost is calculated), the quantity structure variant (which BOM and routing are used), and transfer control (the rules for carrying forward cost estimates).

• OKKN or IMG “Define Costing Variant”: creates a new variant, or customizes a standard variant (PPC1: standard costing, PPP1: modified costing, PPE1: actual costing).

• Valuation Variant: defines “the price source for raw materials (standard price, moving average price, purchasing info record, planned price),” “the source for purchased-item subcontracting costs (purchase order, assigned cost),” and “the activity price (planned activity price or actual activity price).” Example: PPC1’s valuation variant might be set to “raw materials → standard price, purchased items → moving average price, activities → planned activity price.”

• Quantity Structure Variant: defines “the BOM usage to use (01: production, 10: costing),” “the BOM selection priority (priority order among alternative BOMs),” and “routing selection (validity period, group).”

• Transfer Control: controls “which variant’s calculation results for a higher-level material’s cost estimate are referenced.” This is an optimization setting for which variant’s calculation results are reused at which level of a multi-level BOM explosion.

13-3. Cost Component Structure (OKTZ)

The Cost Component Structure is a setting that defines “into which groups (components) the roll-up results of a cost estimate are classified for display.”

• OKTZ “Define Cost Component Structure”: defines components (for example, 01: Direct Material Cost, 02: Direct Conversion Cost, 03: Subcontracting Cost, 04: Manufacturing Overhead, 05: Administrative Overhead) and assigns to each component “which cost elements (G/L accounts) are included.”

• The component classification determines the granularity of management analysis. Too coarse, and you can distinguish only “material cost versus conversion cost”; too fine, and management complexity increases. In practice, design starts from “the cost classification you want to grasp for product-specific cost reduction activities.”

• ML Cost Component (CKMVFM): Material Ledger actual costing also references the same component structure. Since standard cost and actual cost are compared by component, component design is also an important consideration when implementing ML.

13-4. Costing Sheet (KZS2 / OKZ1)

The Costing Sheet defines the overhead surcharge calculation added to product cost.

• OKZ1 “Define Costing Sheet” or KZS2 (Maintain Costing Sheet): defines the structure of the costing sheet. A costing sheet is built by combining “rows” — a “Base Row,” an “Overhead Row,” and a “Total Row.”

• Configuring the Base: specifies the cost element group subject to overhead allocation (for example, the G/L account group for direct material cost). This references a “cost element group (defined in KA01).”

• Configuring the Rate: specifies “a percentage rate or a fixed unit amount.” Different rates can be set for different combinations of “controlling area × validity period × conditions (plant, cost center, profit center, etc.).” Example: differentiated rates by plant, such as “20% for Plant A, 15% for Plant B,” are possible.

• Credit: specifies the “cost center that is credited” for the overhead posted in the overhead calculation. This cost center becomes the “source” of the overhead, and the starting point for allocation to CO-PA and elsewhere.

13-5. Material Ledger / Actual Costing Configuration (OMX1 / CKMVFM)

Here we organize the main configuration for implementing the Material Ledger (ML).

• OMX1 “Configure ML/Actual Costing”: activates the plants that use ML. Because ML is activated at the plant level, it can be enabled or disabled on a plant-by-plant basis. However, since ML cannot be deactivated once activated (a technical constraint), thorough design review is required before implementation.

• CKMVFM “Actual Costing Component Structure”: assigns to ML the component structure used for the actual cost roll-up in CKMLCP. It is recommended to use the same structure configured for standard cost in OKTZ (so that standard and actual cost can be compared using the same component scheme).

• MRN1 (Activate ML for Plant): physically activates ML in the plant master. This is the final activation step, performed after the configuration in OKTZ.

• CKMVFM “Assignment of Valuation Class”: in ML actual costing, actual cost is tracked by inventory “Valuation Class.” The valuation class works in conjunction with MM60 (the valuation class in the material master).

13-6. Variance Variant (OKV1)

The Variance Variant controls the “definition of variance categories, the calculation sequence, and the display settings” in KKS1 variance calculation.

• OKV1 “Define Variance Variant”: sets the calculation order and whether each variance category (quantity variance, price variance, activity variance, resource-usage variance, mix variance, remaining variance) is active. In many cases the standard variant is used as-is, but it is customized according to company-specific variance analysis requirements.

• Assigning the Variance Variant to Production Orders: the variance variant is set in association with the order type (the order category used when creating a production order via CO01/CO11) (OPL8). This allows different variance categories to be applied per order type.

13-7. Settlement Profile (OKO7)

The Settlement Profile defines the rules for settling (CO88/KO88) production orders and internal orders.

• OKO7 “Maintain Settlement Profile”: configures “allowed settlement receivers (Material / CO-PA / Cost Center / Asset, etc.),” “handling of the remaining variance (transfer to the settlement receiver or posting to a variance account),” “enforcement of 100% settlement,” and so on.

• Configuring the settlement receiver: for standard mass-production production orders, settling to “PRD (product stock)” is common. For MTO order-specific production orders, settlement is to “SDP (sales order item) → CO-PA segment.”

• The settlement profile is assigned in association with the order type (OPL8). By setting a different settlement profile for each order type (mass production, prototype, MTO, engineer-to-order assembly, etc.), settlement rules can be managed flexibly.

13-8. Integration Settings with Profitability Analysis (CO-PA)

Variances from cost management are settled to CO-PA segments (product line, customer group, region, etc.), making them visible as part of profit and loss analysis by product and by customer. Below are the main integration configurations with CO-PA.

• KEPC “Assignment of Value Fields: Settlement Rule”: configures the rule by which, at the time a production order is settled, the “CO-PA characteristics linked to the production order (product code, product group, customer, sales organization, etc.)” are automatically posted to the CO-PA segment.

• KE4I “Assignment of Cost Elements to CO-PA Value Fields”: maps a production order’s variance accounts (cost elements) to CO-PA’s “value fields (for example: material variance, conversion variance, quantity variance).” This mapping enables the variance breakdown to be displayed in CO-PA.

• KE4U “Automatic Posting Rules for Actual Data (SD → CO-PA)”: configures the CO-PA posting rules for revenue, cost of goods sold, discounts, and the like, from SD (Sales and Distribution) billing line items at the time revenue is recognized (VF01 invoice). Combined with CO-PC cost management, this achieves a complete product-level profit and loss of “sales revenue − cost of goods sold (standard) − variance − allocated overhead.”

13-9. Overall Summary of the Configuration Settings

Summarizing the main settings above from the perspective of “configuration item, transaction, content, and scope of impact,” the practical recommended order for designing and configuring cost management SPRO settings is: “① Controlling Area (OKKP) → ② Costing Variant (OKKN) → ③ Cost Component Structure (OKTZ) → ④ Costing Sheet (KZS2) → ⑤ Variance Variant (OKV1) → ⑥ Settlement Profile (OKO7) → ⑦ ML Activation (OMX1/MRN1) → ⑧ CO-PA Integration (KEPC/KE4I).” Because these settings are mutually dependent, finalizing the upper-level settings (controlling area, costing variant) first contributes to a stable design.

14. The Transformation Cost Management Brings to the Business

Improved Accuracy of Pricing Strategy

Once you can grasp the accurate actual cost by product, the floor of your pricing strategy becomes clear: “we must sell at or above this price at a minimum, or we will be in the red.” Profitability management through standard cost and variance makes it possible to quantitatively identify “which products are driving profit and which are eroding it,” enabling optimization decisions for the product portfolio.

Making Cost Reduction Activities Scientific

Visualizing, through variance analysis, “where, why, and how much of a cost overrun is occurring” provides the foundation for scientifically prioritizing improvement activities and measuring their effectiveness. The shift from “improving by intuition” to “improving with data” underpins the continuous strengthening of manufacturing competitiveness.

CO-PC as the Management Accounting Foundation for Manufacturers

When SAP S/4HANA’s CO-PC, Material Ledger, and Universal Journal work together, a company can grasp, precisely and in real time, “how much it costs to make a product.” This is not merely a feature of an accounting system — it is competitive infrastructure that determines the very quality of a manufacturing company’s management.

End