Change SAP Cost Component Structure with Material Ledger

By Constantino Solis Prego

Changing an SAP cost component structure with Material Ledger active requires careful cost mapping, cutover timing, and historical reporting. This six-step case study shows how a food and beverage plant added more detail to its existing structure while retaining historical cost information.

The plant had two main production areas: food and liquid processing, and packaging. Its original structure grouped all ingredients into one cost component, packaging into another, and labor, depreciation, and other production activities into three further components. The objective was to make these costs easier to analyze without confusing comparisons with earlier periods.

Table of Contents

1. Before You Change an Active Structure
2. Step 1: Map Origin Groups
3. Step 2: Map Cost Component Groups
4. Step 3: Define a Reporting Sort Strategy
5. Step 4: Plan the Cost Component Split
6. Step 5: Coordinate Cutover Timing
7. Step 6: Preserve Historical Reporting
8. Validation Checklist
9. Conclusion
10. Related Reading
11. Glossary

Before You Change an Active Structure

This example extends the existing structure; it is not a universal procedure for replacing a productive cost component structure or converting historical splits. Check the applicable SAP guidance for your release and deployment before deciding whether the proposed change is compatible with the active actual cost component split. SAP KBA 2230091 covers activation and structure-change scenarios.

Historical postings do not automatically gain the detail introduced by a new mapping. Agree on how reports will interpret old and new components, test the change in a representative system, and coordinate configuration, master data, costing, Material Ledger closing, and reporting.

Step 1: Map Origin Groups

Table 1 shows the initial cost structure before origin groups were used to provide more detail.

Table 1: Initial Cost Component Structure

Create origin groups with transaction OKZ1 and maintain them in the Costing 1 view of purchased materials, including ingredients and packaging. Transaction MM17 can support collective maintenance.

Origin groups allow purchased materials to be mapped to different cost components even when they use the same cost element. In transaction OKTZ, assign cost elements together with origin groups to the required cost components, as shown in Figure 1.

Figure 1: Origin Group Assignment in OKTZ

Check the component capacity supported by your system. Classic structures provide 40 cost fields, allowing up to 20 components when both total and fixed amounts are stored. Extended SAP S/4HANA structures can provide 120 fields, allowing up to 60 such components. The number available depends on the fields consumed by each component and the system capabilities; confirm the applicable limit before expanding the design.

In this project, we also split labor cost between the two main factory sections. This required a new activity type assigned to a separate secondary cost element, A000000004, appropriate routing activities, and changes to assessment cycles. We maintained the splitting structure using transaction OKES to distinguish labor costs for sections 1 and 2.

Before configuring OKTZ, we designed the cost component, cost element, and origin group mapping in a spreadsheet, as shown in Figure 2.

Figure 2: Cost Component Mapping After Origin Group Assignment

Step 2: Map Cost Component Groups

For each cost component, we maintained cost component groups 1 and 2 in OKTZ, as shown in Figure 3.

Figure 3: Cost Component Groups Assigned to a Cost Component

These groups provide alternative aggregations in cost reports. Figures 4 and 5 illustrate selecting cost component group 2 in the costing run analysis and the cost estimate comparison report.

Figure 4: Costing Run Analysis Step

Figure 5: Analyze/Compare Cost Estimates — S_P99_41000111

Step 3: Define a Reporting Sort Strategy

Adding components changed the sequence needed in our reports. We added an alphanumeric prefix to each cost component description, as shown in Figure 6. Reports that sort by description could then display the components in the intended business order. This reporting convention does not remap stored cost values.

Figure 6: Cost Component Descriptions With Sort Prefixes

Step 4: Plan the Cost Component Split

We added new cost components to the active structure and used origin groups to separate costs previously grouped together. For example, all ingredients had been mapped to component 1. The revised mapping assigned some ingredients to the new component 6.

Earlier periods still show all ingredient costs in component 1. From the cutover period onward, costs follow the revised mapping between components 1 and 6. A configuration change does not reconstruct a detailed historical split that was never recorded.

Figure 7: New Cost Component Mapping

Avoid the approach highlighted in red in Figure 7: reusing an existing component for an unrelated cost category can make historical comparisons misleading. In that example, component 2 would combine its remaining packaging role with ingredient B. Document the meaning and validity of each component before implementing the mapping.

Step 5: Coordinate Cutover Timing

Plan a controlled period-boundary cutover. In this case study, the configuration change was scheduled at the end of month M-1, with new standard cost estimates released at the start of month M before material movements began.

Treat that timing as a project example. The correct sequence depends on the release, the type of structure change, period opening, prior-period closing, and any required startup or conversion activities. Confirm the sequence against the applicable SAP Notes and test it before production.

• Coordinate configuration transports and origin group master data updates.
• Calculate, review, mark, and release affected cost estimates in the approved window.
• Control posting access during cutover so transactions do not use an unintended combination of old and new mappings.
• Reconcile standard and actual cost component reporting after the change.

Step 6: Preserve Historical Reporting

Work with the Business Intelligence team to define how reports compare periods before and after cutover. Newly added components may have no values in earlier periods, while an existing component may contain a broader category of historical costs.

For example, renaming component 1 to Ingredients A does not mean its earlier values excluded other ingredients. Keep a dated mapping of component definitions and use reporting groups or documented comparison rules to avoid presenting an apparent cost change that is only a classification change.

Validation Checklist

Validate representative purchased materials, semifinished products, and finished goods before approving the change:

• Check cost element and origin group assignments for completeness.
• Compare cost estimate totals and component splits before and after the change.
• Verify labor allocations, routing activities, and splitting results.
• Test material movements and a complete Material Ledger closing cycle where Actual Costing is active.
• Reconcile total values and confirm that historical reports retain their intended interpretation.

Conclusion

The project achieved more detailed Material Ledger cost reporting by extending the existing mapping and coordinating master data, costing, cutover, and analytics. Preserving the meaning of historical values is as important as adding new components.

About the Author

Constantino Solis Prego is a senior SAP FICO end-user with implementation and training experience, including transformation projects for Central Finance, Profitability Analysis, Project System, and Product Costing. His experience spans management consulting, heavy equipment, FMCG, textiles, and apparel, including global rollout and localization projects.

Related Reading

• SAP Material Ledger: Overview and Actual Costing
• SAP Product Cost Controlling: Book Guide and Key Concepts
• SAP Standard Price vs. Moving Average Price

SAP References

• SAP KBA 2230091: Actual Cost Component Split Activation — Recommendations and Sequence of Steps (full content may require SAP sign-in).
• SAP Learning: Explaining the Cost Component Split.
• SAP Help: General Data in the Material Costing View.

Glossary

Activity Type

A service or activity supplied by a cost center, such as labor or machine hours. Activity quantities and rates determine the costs allocated to receiving objects.

Actual Cost Component Split

A breakdown of actual material costs into cost components in Material Ledger. It supports analysis of the composition of actual costs when the relevant functionality is active.

Central Finance

An SAP S/4HANA deployment scenario that replicates financial and management accounting postings from connected source systems into a central system. Mapping harmonizes accounting data to support central reporting and selected finance processes while source systems continue operating.

Cost Component

A grouping of cost elements, optionally differentiated by origin group, used to show costs such as ingredients, packaging, labor, and overhead.

Cost Component Group

A grouping assigned to cost components to support alternative aggregations and layouts in cost reporting.

Cost Component Structure

The configuration that defines cost components and assigns cost elements and origin groups to them. It determines how a cost estimate is broken down.

Cost Element

A classification of costs in Controlling. In SAP S/4HANA, primary and secondary cost elements are represented by G/L accounts with the relevant cost element categories.

Costing Run

Collective processing of material cost estimates, commonly performed with transaction CK40N.

Material Ledger

SAP functionality supporting material valuation in multiple currencies and the collection of material valuation data. Actual Costing is a separate, optional process in SAP S/4HANA.

Origin Group

A material master attribute that differentiates materials assigned to the same cost element, allowing their costs to be assigned to different cost components.

Profitability Analysis (CO-PA)

SAP functionality for analyzing revenue, costs, and contribution margins by market segments such as products, customers, and sales organizations. Costing-based CO-PA uses value fields; Margin Analysis in SAP S/4HANA uses accounts in the Universal Journal.

Standard Cost Estimate

A material cost estimate used to calculate a standard price. A suitable costing variant and the required marking and release steps are needed to update the material master.

Standard Price

The price used to value a material when price control is S. Releasing a standard cost estimate can update this price.