SAP CO Product Costing

You are an SAP Controlling (CO) specialist configuring product cost planning. The user wants to set up product cost estimates with bill of materials (BOM) integration, material cost analysis, and overhead allocation.

What to check first

• Verify transaction SPRO → SAP Reference IMG → Controlling → Product Costing is accessible in your client
• Run SE16 to check table PLKO (costing lot size master) and CKML (material costing run data) for existing cost estimates
• Confirm BOM exists in CS01 or CS11 for your material before creating cost estimate

Steps

1. Navigate to transaction CK11N (Create Cost Estimate with Quantity Structure) and enter material number, plant, and costing variant (typically V000 or Z001)
2. In the Costing Type field, select appropriate cost estimate type: 01 (standard), 02 (current), or custom variant matching your company costing practice
3. Click Details tab and configure Valuation Date, Currency, and Lot Size (unit of measure for BOM explosion, usually 1 or production batch size)
4. Activate Material Cost Estimate by marking checkbox; system auto-fetches BOM from MAST table and material prices from MBEW (material valuation data)
5. In Origin Group field, specify material source cost origin codes (01 = purchase price, 02 = activity input, 03 = subcontracting) for multi-level BOM costing
6. Set Overhead Key (COKL) to apply cost center activity rates; navigate to CK13 to assign cost elements and allocation percentages (material, labor, machine overhead typically 10-25% each)
7. Click Calculate button; system explodes BOM recursively, applies standard costs from CKMLHDR cost run, and calculates cumulative product cost including overhead absorption
8. Review Cost Estimate Result sheet showing material cost (Tier 1 + sub-assemblies), activity input cost (labor/machine hours × rate), and overhead—verify total against target cost in CKMLCO cost ledger
9. Execute transaction CK24 (Mark Cost Estimate as Standard) to activate calculated cost estimate to material master, updating field STPRS (standard price) in MBEW

Code

*& Report: Product Costing Setup with BOM Integration
REPORT z_product_costing.

TABLES: mara,        "Material Master
        mast,        "BOM Header
        plko,        "Costing lot size
        ckml,        "Material costing run
        mbew,        "Material valuation
        cokl.        "Overhead key

DATA: lt_bom_components TYPE TABLE OF stpo,
      ls_cost_estimate  TYPE ckml,
      lv_material       TYPE matnr

Note: this example was truncated in the source. See the GitHub repo for the latest full version.

Common Pitfalls

• Treating this skill as a one-shot solution — most workflows need iteration and verification
• Skipping the verification steps — you don't know it worked until you measure
• Applying this skill without understanding the underlying problem — read the related docs first

When NOT to Use This Skill

• When a simpler manual approach would take less than 10 minutes
• On critical production systems without testing in staging first
• When you don't have permission or authorization to make these changes

How to Verify It Worked

• Run the verification steps documented above
• Compare the output against your expected baseline
• Check logs for any warnings or errors — silent failures are the worst kind

Production Considerations

• Test in staging before deploying to production
• Have a rollback plan — every change should be reversible
• Monitor the affected systems for at least 24 hours after the change