Production costs¶

Production costs assign economic consequences to manufacturing capacity and output. The three records on this page are complementary:

resource cost represents fixed capacity cost and time-based run cost;
routing cost represents a unit cost attached to a production routing;
shift cost represents the cost of making a shift available on a resource.

They do not replace COGS. COGS values the material sold or served; production costs explain the manufacturing choices used to create supply.

Production resource costs¶

Path in the platform¶

Data > Data Operations > Master Data > Production > Production Assets > Production Resource Costs

Granularity and key¶

Granularity: one effective-dated cost record per production resource.
Key: productionResourceId + effectiveStartDate + effectiveEndDate.

Required fields¶

Field	Meaning
`productionResourceId`	Production resource being valued
`effectiveStartDate`	Beginning of the validity interval
`effectiveEndDate`	End of the validity interval

Optional fields¶

Field	Meaning	Default Value When Not Provided
`fixedCostIncidencePeriod`	Time frequency of the fixed cost	`Monthly`
`fixedCost`	Cost incurred for the resource even when it does not produce	`0`
`runCostIncidencePeriod`	Time frequency of the run cost	`Hourly`
`runCost`	Cost incurred according to productive-resource usage	`0`

The fixed cost is converted to the analysis period. The run cost is converted to an hourly reference and combined with the capacity consumption of the selected resource and routing.

Production routing costs¶

Path in the platform¶

Data > Data Operations > Master Data > Production > Production Assets > Production Routing Costs

Granularity and key¶

Granularity: one effective-dated unit cost per production routing.
Key: routingId + effectiveStartDate + effectiveEndDate.

Required fields¶

Field	Meaning
`routingId`	Production routing being valued
`effectiveStartDate`	Beginning of the validity interval
`effectiveEndDate`	End of the validity interval

Optional fields¶

Field	Meaning	Default Value When Not Provided
`unitCostUom`	Unit in which routing cost is stated	Default Supply Planning unit from Global Planning Parameters
`unitCostValue`	Production cost per unit made through the routing	`0`

The platform converts the routing cost to the output material's planning unit before it is accumulated in the economic result.

Shift cost by production resource¶

Path in the platform¶

Data > Data Operations > Master Data > Production > Production Assets > Shift Cost by Production Resource

Granularity and key¶

Granularity: one effective-dated cost per shift definition and production resource.
Key: shiftDefinitionId + productionResourceId + effectiveStartDate + effectiveEndDate.

Required fields¶

Field	Meaning
`shiftDefinitionId`	Shift definition being valued
`productionResourceId`	Resource on which the shift may be used
`effectiveStartDate`	Beginning of the validity interval
`effectiveEndDate`	End of the validity interval

Optional fields¶

Field	Meaning	Default Value When Not Provided
`costOfShift`	Cost of using the shift on the resource	`0`

Shift cost is accumulated according to the part of the shift-validity interval covered by the planning period.

Dependencies¶

productionResourceId references the production resource in Production resources and routings.
routingId references the routing in Production resources and routings.
shiftDefinitionId references a shift definition associated with the production setup.
unitCostUom references Units of Measure or follows Global Planning Parameters.
Incidence periods use Planning Bucket Size.

Used by¶

Supply Planning and constrained-plan scenario valuation;
capacity, routing, and shift choices in S&OE and Line Sequencing;
the Supply Planning optimizer objective;
Cost-to-Serve and P&L;
the economic decision data model.

Checks¶

provide all dimensions and both validity dates;
do not place the end of validity before the start;
do not repeat the same composite key;
register resources, routings, shift definitions, and units before loading their cost records;
use only accepted time-frequency values;
provide finite numeric values;
keep costOfShift non-negative;
verify that cost validity intersects the scenario period;
avoid counting the same economic component in resource, routing, and shift cost unless the accumulation is intentional.