JinJin48
JinJin48
SAP Consultant | BTP · S/4HANA · US Global Rollout
· 8 min read

Cover: SAP CO Costing Variant — the configuration object that defines all rules for calculating standard cost estimates

SAP CO Costing Variant

The Costing Variant is the central configuration object that defines all rules for how a standard cost estimate is calculated in SAP Controlling Product Costing. It bundles together the Costing Type (what kind of cost to calculate), the Valuation Variant (where to get material prices and activity rates), the Date Control (which dates to use for BOM and routing selection), and the Quantity Structure Control (which BOM and routing alternatives to use). Every time a user runs a standard cost estimate (CK11N) or a costing run (CK40N), they select a Costing Variant — and that variant’s configuration determines every aspect of how the cost is computed.


Part 1: Costing Variant — Core Concepts (All Modules)

1.1 What Is the Costing Variant?

Hub-and-spoke diagram showing Costing Variant at center, connected to Costing Type, Valuation Variant, Date Control, Quantity Structure Control, Cost Component Structure, Standard Cost Estimate (CK11N), and Costing Run (CK40N)

The Costing Variant is a Customizing configuration object identified by a 4-character key (e.g., “PPC1”). It acts as a control document for the cost estimate engine — every parameter needed to compute the cost of a material is either defined directly on the Costing Variant or referenced from a subordinate configuration object (Valuation Variant, Costing Type). For most implementations, 2–4 Costing Variants are sufficient: one for standard cost (plan), one for modified standard cost, and optionally one for actual cost or transfer pricing.

AspectDetails
RoleControls all parameters of standard cost estimate calculation: what type, what prices, what dates, what BOM/routing alternatives
Modules using itCO-PC (Product Costing — primary; all standard cost estimates reference a Costing Variant), PP (BOM and Routing selection controlled via Quantity Structure Control on the variant), MM (material price update controlled via Costing Type), CO-PA (standard cost settlements use the Costing Variant to classify costs)
TransactionsOKKN (Maintain Costing Variants), CK11N (Standard Cost Estimate — selects Costing Variant), CK40N (Costing Run — selects Costing Variant)
Key TablesT499S (not primary), T001W (plant to comp code), TCKH (Costing Variant header), TCKH1 (Costing Variant detail — Costing Type, Valuation Variant, etc.)
S/4HANA noteCosting Variants work identically in S/4HANA and ECC at the configuration level. In S/4HANA, the Material Ledger is mandatory and actual cost calculation (Material Ledger actual costing) runs in parallel using the same material prices and activity rates defined by the Costing Variant’s Valuation Variant. The Costing Variant for standard cost estimates is typically “PPC1” (SAP standard); for actual costing via Material Ledger, a separate variant is used.

1.2 Costing Variant Types

Comparison grid showing Standard Cost (PPC1), Modified Standard Cost (ZPC1), Transfer Pricing variant, and Actual Cost variant, with use cases

Variant TypeTypical KeyCosting TypeUse CaseKey Behavior
Standard CostPPC101 (Standard Cost)Annual standard cost estimate — marks and releases the new standard price for the materialUpdates the standard price (Material Ledger moving average in ECC; ML standard in S/4HANA) when released via CK24
Modified Standard CostZPC1 (custom)06 (Modified Standard)“What if” cost simulations — what would the cost be if material prices changed?Does not update the material price — for simulation and planning analysis only
Transfer Pricing VariantZTP1 (custom)03 (Transfer Price)Intercompany cost calculation for group pricingUses group valuation instead of legal valuation for cross-company postings
Actual Cost VariantZPCA (custom)19 (Actual Price)Post-period actual cost calculation using ML pricesUsed in Material Ledger actual costing run to recalculate costs at actual prices

Design principle: Configure the minimum set of Costing Variants needed. PPC1 for standard cost is always required. A simulation variant (ZPC1 or similar) is strongly recommended for annual budget planning and price change analysis. Transfer pricing variants are required only when intercompany pricing is in scope. Actual cost variants (ML) are required in S/4HANA for Material Ledger reconciliation.


1.3 Organizational Levels and Data Hierarchy

Costing Variant is scoped at the Controlling Area level — a Customizing object available to every plant in the CO Area (it has no plant restriction of its own).

Hierarchy diagram showing CO-Area-scope Costing Variant referencing a Cost Component Structure

Every Costing Variant references a Cost Component Structure, which controls how the resulting cost estimate is split (material, labor, overhead, etc.).

Data hierarchy with a concrete example

Controlling Area 1000
   │
   └── Costing Variant "PPC1"      Std cost estimate
          └── uses ── Cost Component Structure "Z1"   Std cost split

Design principle: The Valuation Variant inside the Costing Variant determines where each cost estimate’s prices come from (Material Master standard price, Purchase Info Record, or planned activity rate). For the annual standard cost run, Purchase Info Record prices for raw materials plus planned activity rates for manufacturing is the most common configuration.


1.4 Integration with Other Master Data Objects

Hub-and-spoke diagram showing Costing Variant at center, connected to Costing Type, Valuation Variant, Cost Component Structure, Material Master (Standard Price), Activity Type (KP26 rates), and Costing Run (CK40N)

ObjectRelationshipPractical Notes
Cost Component StructureReferenced directly on the Costing VariantThe Cost Component Structure determines how cost elements are classified into cost components in the estimate output. Must be fully configured before the first cost estimate run with this variant.
Valuation VariantSub-configuration object referenced by the Costing VariantDefines where to get prices for materials (PIR, standard price, planned price), for activities (plan rate from KP26, actual rate from KSII), and for external operations. Must align with the current state of price maintenance in the system — if KP26 activity prices are not yet planned, activity costs will be zero in the estimate.
Material Master (Standard Price)Costing Variant can source material prices from the Material MasterFor manufactured materials at higher BOM levels, the standard price from the lower-level material’s Material Master (already released from a previous cost estimate run) is used. This creates a dependency: lower-level standard costs must be released before upper-level cost estimates are run.
Activity Type (KP26)Costing Variant’s Valuation Variant sources activity rates from KP26 planningIf the Valuation Variant is configured to use planned activity prices (most common), KP26 prices must be maintained for all Activity Types used in routing operations before the cost estimate run.
Costing Run (CK40N)The Costing Run uses the Costing Variant to process all materials in scopeCK40N selects the Costing Variant once for the entire run. Ensure the variant is consistent and fully configured before initiating a mass costing run — errors in the variant affect all materials in the run scope.

Part 2: CO-Specific Field Details

2.0 Scope of CO Ownership

Checklist showing CO ownership across Costing Variant configuration: Variant header, Costing Type, Valuation Variant, Date Control, Quantity Structure Control

Data SectionCO InvolvementNotes
Costing Variant Header (TCKH)◎ OwnerCO administrator creates and maintains in Customizing (OKKN)
Costing Type◎ OwnerCO Customizing — determines standard price update behavior
Valuation Variant◎ OwnerCO Customizing — most critical sub-object; defines price sources
Date Control◎ OwnerCO Customizing — controls BOM and routing selection dates
Quantity Structure Control○ Shared with PPPP consultant defines BOM and Routing selection criteria; CO integrates with the costing variant

Legend: ◎ = Owner / Critical, ○ = Direct involvement


2.1 Costing Variant Key Parameters (TCKH)

Checklist of key Costing Variant configuration parameters: Costing Type, Valuation Variant, Date Control, Quantity Structure, Cost Component Structure, Transfer Control

ParameterDescriptionPractical Usage
Costing Variant Key4-character identifier (e.g., PPC1, ZPC1)Use the SAP standard PPC1 for standard cost estimation whenever possible — it is pre-configured and well-documented. Create custom variants only when specific control parameters are needed that differ from PPC1. Name custom variants with a “Z” prefix per SAP naming convention.
Costing TypeDetermines the purpose and price update behavior of the estimateCosting Type 01 (Standard Cost) is the most common — allows the estimate to be marked and released to update the standard price. Costing Type 06 (Modified Standard) is used for simulations. Costing Type 19 (Actual Cost) is for Material Ledger actual costing. The Costing Type is a separate Customizing object (transaction OKKI) — create the type before configuring the variant.
Valuation VariantReferences the sub-configuration that defines price sourcesThe Valuation Variant is the most technically complex sub-object. It defines: (1) Material price source — which field in the Material Master or which external price record to use for material costs; (2) Activity price source — planned rate (KP26), actual rate (KSII), or manual price; (3) External processing — price source for subcontracted operations. Maintain the Valuation Variant in OKKN → Valuation Variant.
Date ControlControls which dates are used for BOM and routing validity during the cost estimateDate Control determines: Costing Date From (start of validity for the estimate), BOM validity date (which BOM to select), Routing validity date (which routing to select). For annual standard cost estimates, typically set BOM and Routing validity dates to the first day of the new fiscal year, ensuring that engineering changes effective from that date are reflected in the new standard cost.
Quantity Structure ControlControls BOM type, routing type, and selection priorityReferences the PP BOM application (e.g., “PP01”) and routing type to use during the cost estimate BOM explosion. For standard manufacturing cost estimates, this typically references the Production BOM and Standard Routing. For process industries, this may reference the Master Recipe instead of the routing.
Transfer ControlControls whether multi-level BOM explosion uses existing cost estimates for sub-materialsIf Transfer Control is active, the cost estimate for a sub-material already marked/released is used as the cost for that sub-material in the upper-level estimate, rather than re-exploding the sub-material’s BOM. This speeds up cost estimate runs significantly for large BOMs. Standard practice for annual costing runs where all sub-material standard costs are released in a specific sequence (lower levels first).

L1) Big Picture

IDCategoryTitle
co-001OverviewWhat is SAP CO?

L2-A) Master Data

IDCategoryTitle
co-a01OverviewSAP CO Master Data: Overview, Hierarchy & Relationships
co-a02-01Master DataSAP CO Material Master
co-a03-01Master DataSAP CO Cost Element
co-a03-02Master DataSAP CO Cost Element Group
co-a04-01Master DataSAP CO Profit Center Group
co-a04-02Master DataSAP CO Profit Center
co-a05-01Master DataSAP CO Cost Center Group
co-a05-02Master DataSAP CO Cost Center
co-a05-03Master DataSAP CO Activity Type Group
co-a05-04Master DataSAP CO Activity Type
co-a05-05Master DataSAP CO Statistical Key Figure
co-a06-01Master DataSAP CO Internal Order Group
co-a06-02Master DataSAP CO Internal Order
co-a07-01Master DataSAP CO Cost Component Structure
co-a07-02Master DataSAP CO Costing Variant 📍
co-a08-01Master DataSAP CO Operating Concern

L2-B) Transaction

IDCategoryTitle
co-b01OverviewSAP CO Transactions: Process Flow, Hierarchy & Relationships