Show TOC

  Run Schedule Header in Cost Object Controlling Locate this document in the navigation structure


Specification of the production version for a plant material and a validity period during which costs are collected.

Note Note

From Release 4.6A onwards, you no longer create run schedule headers in repetitive manufacturing. Instead, you manufacture on the basis of production versions. Run schedule headers are only used if they were created in releases before 4.6A and therefore still exist in the system.

End of the note.


Depending on how the costs are settled, run schedule headers can be subdivided into run schedule headers with run schedule quantities and run schedule headers with partial orders.

For a run schedule header with run schedule quantities, production is split into production quantities by specifying quantities and periods. The costs of the run schedule header are collected on a Controlling object (product cost collector).

In the case of a run schedule header with partial orders, the production process uses the planned orders and production orders or process orders. The costs incurred in production are settled to these orders.


Run Schedule Headers in Cost Object Controlling

You collect the costs for run schedule headers on product cost collectors. You create these product cost collector manually. When you create a run schedule header for a production version, the system establishes a direct link to the product cost collector with the same characteristic value (material / plant / production version). The number of the product cost collector is specified in the run schedule header.

You perform logistical functions such as confirmations and goods issues for the run schedule header. The costs are collected on the product cost collector.

Note Note

If you are manufacturing on the basis of sales orders and want to withdraw materials manufactured using run schedule headers as individual requirements materials, you do this by means of a planned order.

End of the note.
Reorganization of Run Schedule Headers

A run schedule header can only be reorganized if it is certain that no change in the work in process or scrap will occur on the basis of that run schedule header and that therefore no more work in process or scrap will need to be calculated for the run schedule header. Requirements:

  • The order must have the status delivered .

    It is pointless to calculate work in process after final delivery because the work in process is canceled upon final delivery.

  • The accounting period must be closed

    When the accounting period is closed, no further correction postings in Financial Accounting are possible.

General Information on Run Schedule Headers

The repetitive manufacturing process delivers the semifinished and finished products to the warehouse stock. In contrast to order-related production, the planned orders from requirements planning are not converted into orders using the original lot size. Instead, multiple planned requirements are grouped into run schedule headers.

Run schedule headers are therefore not based on the lot size but on a period of time defined by the user. In some circumstances this period of time can be the entire life of the product. Cost Object Controlling is period-based, and measures the target costs and actual costs for the period for each product cost collector.

The costs are updated on a product cost collector that you first create manually in the menu of Product Cost by Period .

The run schedule header determines the following:

  • Which material is manufactured in the specified time frame

  • Which alternative BOM is used as the basis for backflushing

  • Which alternative routing is used as the basis for the confirmation to reporting point quantities

  • The storage location to which the material is delivered

See also:

Recommendations for Repetitive Manufacturing

Cost Object Controlling: Sales-Order-Related Production

Selected Logistical Processes and Cost Objects