How to Create a Control Key in SAP PP (OPJ8)
how to create control key in sap pp
Also searched as
- sap pp control key configuration
- OPJ8 control key sap
- sap control key indicators
Short answer
A control key tells SAP what an operation is allowed to do: be scheduled, costed, confirmed, printed, sent for external processing. Create one with transaction OPJ8 (or SPRO > Production > Basic Data > Routing > Operation Data > Define Control Key), copy a standard key such as PP01, change the indicators, and assign it in the routing or work center.
Applies to: SAP ECC 6.0 and SAP S/4HANA on-premise
Create a control key
- 1Run OPJ8 (Maintain Control Keys for task lists and orders). Do not edit the standard keys, copy one instead.
- 2Select the nearest standard key (PP01 for an in-house operation) and choose Copy As, then enter a new key in your customer namespace (for example Z001 or ZP01).
- 3Give it a description that explains the use, such as 'In-house with confirmation'.
- 4Set the indicators: scheduling, capacity planning, automatic goods receipt, cost, confirmation, print time tickets, external processing, and so on.
- 5Save to a customizing request.
- 6Assign the key at the work center (Default values tab) so new operations pick it up, and in the routing operation (CA01 or CA02).
- 7Test by creating a production order (CO01) and confirming the operation with CO11N.
What the main indicators do
Scheduling decides whether the operation takes part in lead-time scheduling. Without it the operation gets no dates. Capacity planning decides whether capacity requirements are generated for the work center. Costing decides whether the operation is costed in the standard cost estimate and the production order.
Confirmation is a three-state choice: confirmation required, optional or not possible. If an operation will not confirm, this is the first thing to check. Automatic goods receipt posts the receipt of the finished material at confirmation of the final operation, and is useful for backflush environments.
External processing indicator sets the operation for subcontracting. It makes the system generate a purchase requisition and expects a different data entry in the routing (purchasing info record, plant, material group). Do not set it on an in-house operation.
Printing and milestone indicators
Print time tickets and print confirmation controls whether the production order print includes these documents. Printing is in practice an order-level setting, but the control key decides whether each operation is eligible.
Milestone indicator is used for milestone confirmation and milestone-based costing, such as the progress of a long order. If you rely on milestone confirmation in the order, an operation without this flag will not trigger it.
Rework and inspection characteristics indicators exist so that operations related to quality are handled consistently. Copy these settings from the standard QM-related keys rather than guessing.
Where the key is used and how to test
The key is on the operation in the routing, and it defaults from the work center when the work center is chosen. The production order copies the operation from the routing, so changing the key later does not update existing orders. You must update or re-explode them.
To verify, create a production order with a material that uses the new key, display the operation and look at the Control key field, then confirm it in CO11N. Check that costs appear on the order, capacity requirements in CM01, and that the confirmation behaves as designed.
Always transport the key in the same request as the work center or routing changes that reference it, otherwise the target system rejects the assignment.
OPJ8 Maintain control keys
SPRO > Production > Basic Data > Routing > Operation Data > Define Control Key
CR02 Work center > Default values > Control key
CA02 Routing > Operation overview > Control key
Try it here, free
SAP PP Database Tables Reference
A lookup of the main SAP PP database tables, what each holds and the key fields to join on.
Common pitfalls
- !Editing the delivered keys directly, which is overwritten by upgrades and support packs.
- !Setting confirmation to 'not possible' on an operation shop floor staff need to confirm.
- !Using external processing on a normal operation, creating unwanted purchase requisitions.
- !Changing a key and expecting open production orders to change automatically.
- !Forgetting the cost indicator, leaving the operation with no planned cost.
How an ERP-grounded AI assistant handles this
Control key issues often show up as a symptom in production: an operation that will not confirm, has no cost, or creates a purchase requisition. A grounded assistant can read the operation, its control key and the key's indicators and tell the planner which flag explains it. Netray's read-only layer can be hosted on the customer's own servers so shop floor and routing data never leaves the building.
Frequently asked questions
What is the tcode for control key in SAP PP?
OPJ8 is the commonly used transaction for maintaining control keys. The same node is available through SPRO under Production > Basic Data > Routing > Operation Data > Define Control Key.
Which standard control key is used for in-house operations?
PP01 is the standard in-house key for production operations. For external processing, PP02 is the usual standard key. Copy the one closest to your need into the customer namespace.
Why can I not confirm an operation?
Check the control key first. If confirmation is set to not possible on the key, the operation will refuse confirmation. After that, check the order or operation status for a technical completion or delivery block.
Do control key changes affect existing orders?
No. Orders copy the operation data from the routing at creation. Existing orders keep their old control key until the operation is changed or the order is re-exploded.
Related
SAP PP End to End Configuration: Steps, IMG Paths and Process Flow
SAP PP configuration runs in a fixed order: enterprise structure (plant, storage location, planning plant), master data (material, BOM, work center, routing, production version), MRP and planning, production order types and scheduling, confirmation, then costing and settlement. Get the order right because each layer depends on the one before it. The IMG node is Production in SPRO, plus Materials Management for plant and MRP basics.
Error fixSAP CO11N Confirmation Errors and How to Fix Them
CO11N (time ticket confirmation for production/process orders) throws several distinct errors: deviation from the standard value is too large, goods movement not possible for a component, or the order/operation status does not allow confirmation. Each has a specific cause in order status, routing tolerance settings, or component availability, not a single generic fix.
Error fixSAP CO01 Error: No Production Version Found for Material
SAP cannot pick a production version for the order quantity and date, so it cannot determine the BOM and routing. Fix it in C223 or on the MRP 4 view of the material: create a version for the plant, make its validity dates and lot size range cover the order, link a valid BOM alternative and routing, and remove the lock indicator.
Error fixSAP M7 021: Deficit of SL Stock Quantity
M7 021 fires during a goods issue, delivery, or confirmation when SAP checks the unrestricted-use (SL) stock for the exact plant, storage location and batch combination and finds less than what you are trying to post out. Fix the entry (batch, storage location, quantity) first; only enable negative stock or downgrade the message to a warning if the business genuinely needs to post ahead of a receipt.
Error fixSAP IDoc Status 51: Application Document Not Posted
Status 51 tells you the IDoc reached the application layer and failed to post, but the status text itself is not the error - the real cause sits in the status record's long text or the linked application log. Fix the underlying data or configuration, then reprocess the IDoc through BD87 rather than editing the status.
Error fixSAP Short Dump TIME_OUT: Maximum Runtime Exceeded
A TIME_OUT runtime error means a dialog (or RFC) work process ran longer than the maximum allowed runtime, controlled by profile parameter rdisp/max_wprun_time (600 seconds by default). The fix is almost always to move the long-running work to background processing or tune the underlying program, not to raise the timeout.
AI for ERPAI Agents for SAP Production Planning, MRP, and Exception Triage
AI agents that triage SAP MD04 exceptions, explain predictive MRP shortages, and draft planned-order actions, grounded on your own SAP data, deployed on-prem.
Stuck on SAP S/4HANA and ECC?
Talk to engineers who work inside SAP S/4HANA and ECC every week, and who build private AI that answers these questions from your own ERP data.
Keep exploring
Free tools
- SAP PP Database Tables ReferenceA lookup of the main SAP PP database tables, what each holds and the key fields to join on.
- SAP PP Tables Map: Orders, Routings, Resources and PIRA table list for SAP PP grouped by production order, routing, work center, PIR and BOM, with the key fields to join on.
- SAP PP Production Order Variance CalculatorBreak the difference between target and actual production order cost into price, usage, rate and efficiency variances.
ERP fixes and how-tos
- How to create a routing, work center and production supervisor in SAP PPSet up SAP PP master data: create a work center with CR01, a routing with CA01, and a production supervisor with OPJ2, plus the production version link.
- SAP PP End to End Configuration: Steps, IMG Paths and Process FlowSAP PP end to end configuration in order: organizational structure, master data, MRP, order types, confirmation, costing and settlement, with IMG paths and tcodes.
- SAP PP Tolerance Keys: Overdelivery, Underdelivery and OMR6Where tolerances are set in SAP PP: over- and underdelivery on the material master, confirmation tolerances in the IMG, and tolerance keys in OMR6 for invoices.
Runs with your ERP
- Beas Manufacturing with SAP Business OneHow Boyum's Beas Manufacturing adds planning, capacity scheduling, quality control and shop floor control to SAP Business One, plus setup and pitfalls.
- delaware FAST MES and SAP ECC: Connecting the Shop FloorHow delaware FAST MES connects SAP ECC or S/4HANA to the shop floor with local buffering during outages: data flows, setup, pitfalls and a private AI layer.
AI on your ERP
- AI Agents for SAP Production Planning, MRP, and Exception TriageAI agents that triage SAP MD04 exceptions, explain predictive MRP shortages, and draft planned-order actions, grounded on your own SAP data, deployed on-prem.
- AI Production Scheduling on Top of Your ERP: Explain, Triage and Re-Plan Without Replacing the SchedulerHow AI helps planners and schedulers explain late jobs, fix bad routing data and draft reschedules on top of ERP work orders, without replacing the finite scheduler.
Integrations
- How to use ChatGPT with SAP ECC 6.0Using ChatGPT with SAP ECC 6.0: custom GPT actions, exports versus live access, an OData or MCP bridge, enterprise data controls, and when a private model is safer.
- How to build a mobile app for SAP ECC 6.0Build a mobile or barcode app for SAP ECC 6.0 on the shop floor: goods movements, production confirmations, approvals and offline handling over RFC or OData.