SAP Cost Objects in Controlling: Types, Uses, and Transactions

By Ashish Sampat

Table of Contents

• Production Orders and Process Orders
• Cost Objects Compared
• Product Cost Collectors and CO Production Orders
• Internal Orders, Maintenance Orders, and Cost Centers
• Selected SAP Transactions
• Case Study of an Acquired Business Unit
• Conclusion

Production Orders and Process Orders

A production order supports discrete manufacturing, such as assembling machine parts. Its quantity structure typically comes from a bill of materials (BOM) and routing, with operations performed at work centers.

A process order supports process manufacturing, such as chemicals or food processing. It typically uses a material list and master recipe with resources, operations, and phases. Process instructions can support shop-floor execution through control recipes and PI sheets.

Both order types support production cost planning and actual cost collection. The manufacturing process, execution requirements, and reporting design should guide the choice. Read our detailed comparison of SAP Process Orders and Production Orders.

Cost Objects Compared

Table 1 summarizes common objects used to collect and analyze costs. The master data column describes a typical setup. Required fields and available functions depend on your configuration and SAP edition.

Product Cost Collectors and CO Production Orders

A product cost collector collects actual production costs by period. It is used in repetitive manufacturing and can also collect costs from production orders or process orders when Product Cost by Period is configured for a supported scenario. In that setup, the collector receives the costs associated with the linked manufacturing orders. See SAP’s product cost collector documentation.

A CO production order supports cost collection without the usual BOM and routing quantity structure of a logistics production order. Preliminary costs can be planned using unit costing. SAP describes this in preliminary costing for CO production orders.

Order types such as PP01, PI01, CP01, and RM01 are familiar examples for production orders, process orders, CO production orders, and product cost collectors. Use the order types configured for your system and check their costing and settlement parameters.

Internal Orders, Maintenance Orders, and Cost Centers

An internal order provides focused cost tracking for a job or activity, such as a marketing event or investment. A real order receives actual costs and can settle them to permitted receivers under its settlement rule. A statistical order provides an additional reporting view while the real posting goes to another object, such as a cost center. Statistical orders cannot be settled.

A maintenance order collects maintenance costs, including labor, materials, and external services. Equipment and functional locations provide the technical context where used.

A sales order item can carry costs and revenues when the sales-order costing scenario is configured accordingly. This is relevant for customer-specific production and services. Collecting costs at sales order item level requires the relevant account assignment and costing settings.

A cost center represents an area of responsibility for ongoing costs. It supports departmental planning, actual cost analysis, and allocation of services to other objects.

Selected SAP Transactions

Table 2 lists selected SAP GUI transactions. In S/4HANA, check the apps and authorizations available for your edition and release.

Plan closing activities around the object and accounting scenario. Manufacturing orders and product cost collectors can require different work-in-process, variance, and settlement procedures. SAP’s settlement guidance for Product Cost by Order and Period explains the configuration dependencies.

Case Study of an Acquired Business Unit

Consider a company using process orders that acquires a business unit running production orders in another SAP system. As the acquired unit moves onto the company’s platform, should it switch to process orders?

Using a common approach can simplify training, support, and master data maintenance when both units have similar manufacturing processes. The evaluation should include recipes or routings, shop-floor instructions, confirmations, reporting, and the effort required to change.

If one unit makes discrete machine parts while the other manufactures chemicals, each may need its existing production model. The Production Planning and shop-floor teams should assess the operational fit together with Controlling, then test the cost flow and closing process.

Conclusion

Choose the object around the activity being controlled and the level at which costs must be analyzed. For manufacturing, decide whether costs should be analyzed by individual order or by period, then align the logistics master data, posting rules, and closing procedures.