Product Costing
FI / FICObeginner

FICO Product Costing Part 1: What a Product Really Costs

Key takeaway

Product costing calculates the planned cost of manufactured products. Learn how SAP builds a standard cost estimate from BOM (materials) and routing (activities), adds overheads, splits costs into cost components, and uses the result as the standard price for inventory valuation.

What this complete series covers

Learn Product Costing in a clear, practical sequence — from the basic idea to real project use, troubleshooting, and interview-ready understanding.

Who it is for
Best for SAP consultants, developers, and learners who want a practical understanding of Product Costing.
Prerequisites
Basic SAP S/4HANA navigation and an understanding of the business process are helpful. Configuration or transaction steps require suitable access to a practice or project system.
Final outcome
By the end, you should be able to explain Product Costing clearly, follow the main end-to-end flow, apply it in a project scenario, and troubleshoot the most common issues.
  1. Part 1: FICO Product Costing Part 1: What a Product Really Costs

    Introduces the business purpose of product costing, its organizational dependencies, and the master data objects (material master, BOM, routing, cost center, activity type) that feed a cost estimate.

  2. Part 2: FICO Product Costing Part 2: The Costing Run and Posting Flow into Production

    Explains how costing variants, valuation variants, and costing versions drive standard cost estimate calculation, and how those results connect to production order cost collection,

  3. Part 3: FICO Product Costing Part 3: Costing Variants and Single Cost Estimates

    Learn how costing variants, valuation variants, and costing versions drive standard cost estimate calculation, and how to execute, mark, and release standard costs that update mate

  4. Part 4: FICO Product Costing Part 4: Enterprise Architecture, Governance and Operations

    Architect-level guidance on designing, governing, and operating Product Costing across multi-plant, multi-system landscapes, including ECC-to-S/4HANA migration, Material Ledger man

  5. Part 5: FICO Product Costing Part 5: Order-Based Controlling, Variances and Settlement

    Understand how production and process orders accumulate actual costs, how variance categories are calculated at period-end, and how settlement moves balances to FI/CO and profitabi

System and release assumptions: Examples focus on SAP S/4HANA. Exact apps, transaction codes, configuration paths, and field names can vary by release and deployment model.

Explanation

📌 KEY POINTS
✅ A standard cost estimate = materials (from BOM × prices) + activities (routing × activity prices) + overheads.

✅ The cost component split shows cost by category (material, labor, machine, overhead) for margin analysis.

✅ Once released, the estimate becomes the standard price (price control S) for valuation.

✅ Actual production costs are compared with standard to find variances.

⚠️ Wrong BOMs, routings or activity prices produce wrong standard prices — master data quality is everything.

━━━━━━━━━━━━━━━━━━━━
▶ WHAT THIS SERIES COVERS

Part 1: What a product really costs

Part 2: Costing run and posting flow into production

Part 3: Costing variants and single cost estimates

Part 4: Enterprise architecture and governance

Part 5: Order-based controlling, variances and settlement

━━━━━━━━━━━━━━━━━━━━
▶ 1. QUANTITY STRUCTURE

  • BOM (components) and routing (operations, work centers, activity types).

━━━━━━━━━━━━━━━━━━━━
▶ 2. VALUATION

  • Material prices, activity prices from cost centers.

━━━━━━━━━━━━━━━━━━━━
▶ 3. OVERHEADS

  • Costing sheet percentages (e.g. material overhead 5%).

━━━━━━━━━━━━━━━━━━━━
▶ 4. COST COMPONENTS

  • Split for analysis and COGS split.

━━━━━━━━━━━━━━━━━━━━
▶ 5. STANDARD PRICE

  • Mark and release; inventory valuation.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

  1. Display a BOM and routing.
  2. Create a single cost estimate (CK11N).
  3. Review the cost component split.

✅ CHECKPOINT: you can explain every line of the estimate.

Code example

ABAP Code
===== ESTIMATE EXAMPLE (1 bicycle) =====Materials: frame 40 + wheels 2×15 + other 10 = 80Activities: assembly 0.5 h × 60 = 30 | machine 0.2 h × 50 = 10Overhead: material overhead 5% of 80 = 4Standard cost = 124 → cost components: material 80, labor 30, machine 10, overhead 4 ===== TRANSACTIONS =====CS03 BOM | CA03 routing | CK11N cost estimate | CK13N display | CK24 mark/release

Real project scenario

A discrete manufacturer found finished goods standard prices 20% too low. Routings used outdated labor times and activity prices from two years ago. Refreshing activity planning and routings before the annual costing run gave realistic prices.

Common mistakes

  • Outdated routings.
  • Old activity prices.
  • Releasing without impact review.
  • Ignoring cost components.
  • Missing overheads.

Best practices

  • Validate BOM/routing.
  • Plan activity prices yearly.
  • Review revaluation impact.
  • Use cost components.
  • Maintain costing sheets.

Interview angle

Questions: "How is a standard cost estimate built?", "What is a cost component split?", "What happens at release?"
Strong answer: quantity structure, valuation, overheads, components, release and variances.

Practice this lesson

Quick check

1. What does the cost component split show?

2. Standard prices are 20% too low because routings use old labor times. What should be fixed?

3. What makes up a standard cost estimate for a manufactured product?

Interview questions

1. What are the core concepts of Product Costing, and how would you explain them clearly in an SAP interview?

Answer it in your own words first, then compare.

2. A discrete manufacturer doubts its standard costs. Explain how SAP calculates a standard cost and how you'd validate it.

Answer it in your own words first, then compare.

Practice more with Interview AI →

Reference-verified: the steps are checked against official SAP documentation and tutorials, and object and field names in the sample code are checked for consistency. The code has not been compiled or run on an SAP system by ERPClimb. Syntax marked release-dependent varies by SAP release, so check it in your own system.

More lessons in this topic

Interview questions on this topic

Related SAP topics