SAP PP End to End Configuration: Steps, IMG Paths and Process Flow
sap pp end to end configuration
Also searched as
- sap pp configuration steps
- sap pp end to end implementation process
- sap pp organizational structure
- sap pp end to end process flow
Short answer
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.
Applies to: SAP ECC 6.0 and SAP S/4HANA on-premise (discrete manufacturing, PP-MRP, PP-SFC)
End to end PP configuration sequence
- 1Enterprise structure: define company code, plant (OX10), storage locations (OX09) and assign the plant to the company code (OX18). Assign the plant to a purchasing organization if you also buy components.
- 2Material master basics: define material types and number ranges, and activate the MRP, Work Scheduling and Plant Data/Storage views for the plant. Define MRP controllers per plant.
- 3Master data: create the BOM (CS01), work centers (CR01), routing (CA01) and, where used, the production version (C223) that ties BOM and routing together.
- 4Planning: maintain MRP plant parameters, MRP types, lot-sizing procedures and planning strategies, then test with MD01N and review the result in MD04.
- 5Shop floor: define production order types, order-type-dependent parameters, scheduling parameters, control keys (OPJ8) and the confirmation parameters. Number ranges and status profiles belong here too.
- 6Execution: release the order (CO02), issue components (MIGO 261), confirm (CO11N) and receive finished goods (MIGO 101).
- 7Costing and close: set up cost centers and activity types, standard costing (CK11N), the order settlement rule and the costing variants, then run variance calculation and settlement (KKS1 or CO88).
- 8Test the whole chain with a pilot material before loading the real master data.
Organizational structure for PP
PP does not have its own org unit. It sits on the plant, which is the central object. Planning in MRP happens at plant level (or at MRP area level if you activate MRP areas for storage locations or subcontractors). One plant can be the planning plant for others, and the work center, routing and production orders are plant-specific.
Decide early how many plants you need. A common mistake is creating one plant per physical building when the real need is a storage location or a work center group. Plants carry their own valuation, MRP, costing and number ranges, so every extra plant multiplies the configuration and master data load.
Also define the controlling area and cost centers now. Work centers refer to cost centers, and without them you cannot cost a routing operation.
SPRO > Enterprise Structure > Definition > Logistics - General > Define, copy, delete, check plant (OX10)
SPRO > Enterprise Structure > Definition > Materials Management > Maintain Storage Location (OX09)
SPRO > Enterprise Structure > Assignment > Logistics - General > Assign plant to company code (OX18)
Master data and the production version
The BOM defines what goes into the product, the routing defines the sequence of operations and the work centers they run on, and the work center holds the capacity, scheduling formulas and costing link. In the material master, the MRP 1 to 4 views, Work Scheduling view and the Plant Data / Storage 1 view must be created for the producing plant.
The production version links one BOM alternative to one routing alternative and is what the production order reads. If it is missing or invalid for the order quantity or date, order creation fails. See the related page on the missing production version error.
Procurement type must be set to E (in-house production) for manufactured items and F for externally procured. Special procurement type, planning strategy group and the MRP type then decide how demand is covered.
CS01 Create BOM
CR01 Create work center
CA01 Create routing
C223 Maintain production version
MRP, order types and scheduling
MRP configuration sits under Materials Management > Consumption-Based Planning and Forecasting. Define the plant parameters, MRP groups, MRP types, lot-sizing procedures and the planning horizon. Production planning strategies (make-to-stock, make-to-order) are in Production > Production Planning > Demand Management > Planning Strategy.
Production orders use order types defined under Production > Shop Floor Control > Master Data > Order. Each order type has a number range, a status profile, a settlement profile and a costing link. Order-type-dependent parameters per plant control the default scheduling, availability checks, goods movements and printing.
Scheduling parameters decide how lead time is calculated from operation durations and reduction levels. If dates come out wrong, check the scheduling type (forward, backward, today), the work center formulas and the factory calendar before blaming MRP.
Confirmation, costing and settlement
Confirmation parameters control whether CO11N posts activity, backflush, automatic goods receipt and which fields are visible. The control key (OPJ8) on each operation decides whether it is confirmable, costed, scheduled and printed. A wrong control key is the usual cause of an operation that will not confirm.
Costing needs a costing sheet or valuation variant, a costing variant for planned and actual costs, and a settlement profile with the target receiver (material account, usually). Standard price comes from CK11N and CK24, and variances are calculated at period end then settled to the variance accounts.
Run one test order through every step and check the financial documents at each point. That is the real end to end test of configuration, not the individual IMG nodes.
Try it here, free
SAP SD Configuration Transactions and IMG Reference
Find the SAP SD customizing transaction for a setting, with the table it maintains and the question it answers.
Common pitfalls
- !Configuring order types before the plant, number ranges and status profiles exist, which forces rework.
- !Creating a BOM or routing before the material master has the right views in the plant.
- !Skipping the production version, then finding the order cannot be created or the BOM explosion picks the wrong alternative.
- !Leaving the work center without a cost center or activity type assignment, so the operation has no cost.
- !Transporting configuration without master data dependencies (number ranges, status profiles), which makes the quality system test pass and production fail.
How an ERP-grounded AI assistant handles this
Configuration questions are usually 'why does this plant behave differently from that one'. An AI assistant grounded in the customizing tables can compare order types, control keys and MRP parameters across plants and show where they differ, so the consultant spends time deciding rather than navigating. Netray builds this as a read-only layer that can run on the customer's own servers with a private model. It explains and compares; configuration changes still go through your normal transport process.
Frequently asked questions
What is the order of SAP PP configuration?
Enterprise structure first, then material master settings, then BOM, work center, routing and production version, then MRP, order types and scheduling, then confirmation and costing. Each step depends on the previous one, so changing the order creates rework.
Which SAP modules does PP need to be configured with?
PP depends on MM for material master and procurement, CO for cost centers and order costing, QM if inspection is part of production, and FI for valuation and account determination. Configure at least the basics in MM and CO before PP order types.
Is the configuration different in S/4HANA?
Largely the same IMG nodes apply, but MRP runs through MD01N with MRP Live, the material master is simplified, and some tools such as Production Planning with PP/DS are separate options. Check the simplification list for your release.
How long does an SAP PP implementation take?
It depends on scope. A single plant with standard discrete manufacturing can take a few months for core configuration and testing. Multiple plants, variants, make-to-order or process manufacturing extend that considerably. Data migration usually takes longer than people expect.
Related
SAP 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.
How-toSAP MD01N (MRP Live) vs MD01: How to Run MRP Correctly
MD01N is MRP Live: the same planning logic as classic MD01, but executed inside the SAP HANA database instead of looping through materials in ABAP. Run it from MD01N by entering the plant, choosing a processing key (net change or regeneration), setting the purchase requisition and scheduling parameters, and executing in the background for large scopes.
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.
How-toHow to Create a Control Key in SAP PP (OPJ8)
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.
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.
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.
AI for ERPAI for SAP S/4HANA, Running On-Prem or in Your Private Cloud
Run AI on SAP S/4HANA without sending ERP data to a public API. On-prem and private-cloud architecture, CDS views, OData, and honest deployment trade-offs.
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 SD Configuration Transactions and IMG ReferenceFind the SAP SD customizing transaction for a setting, with the table it maintains and the question it answers.
- SAP PP Planning Process Maturity AssessmentA ten question self-assessment of how well your SAP PP planning and execution processes work, with recommendations by score band.
- SAP PP Go-Live Master Data and Cutover ChecklistA tick-box readiness check for production planning go-live, covering master data, configuration, cutover and support.
ERP fixes and how-tos
- How to Create a Control Key in SAP PP (OPJ8)Create and configure a routing control key in SAP PP with OPJ8: what each indicator does, which ones matter for confirmation and costing, and how to test it.
- 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.
- SAP PP, PM and MM API: Production Orders, Maintenance Orders and Material MasterWhich SAP APIs cover production orders, maintenance orders and material master (MM02)? OData service names, BAPI alternatives and a sample GET call.