E ERP Atlas
404
CONFIGURATION WORKBENCHDesign the P2M loop and prove one production order

P2M 404 ยท AT THE KEYBOARD

Plan to Make Configuration Workbench

Configure the minimum discrete-manufacturing spine so demand becomes executable production supply, physical execution creates accounting evidence, and actual results feed the next planning cycle.

IMPLEMENTATION CONTEXT

P2M Implementation Context

This guide starts after the manufacturing strategy and fit-to-standard direction are understood. It focuses on the configuration, execution and proof spine required to plan, produce, receive and financially reconcile one manufactured product.

Advanced Planning, detailed scheduling, repetitive manufacturing, process manufacturing, subcontracting, complex batch determination, advanced quality integration and full Product Costing design are outside the minimum scope of this guide.

  1. Manufacturing Strategy
  2. Fit-to-Standard
  3. Confirm Planning / Execution Design
  4. Configure
  5. Produce
  6. Reconcile

CONFIGURATION SPINE

Manufacturing behaves as a planning feedback loop

Use this hierarchy before opening the 87-entry technical register. The register supports the workbench; it does not define the teaching sequence.

FOUNDATION→PRODUCT DESIGN→PLAN→EXECUTE→ACCOUNT & CLOSE→FEEDBACK→PLAN

P2M MENTAL MODEL

One product, one executable plan, one feedback signal

FOUNDATION

FOUNDATION

Plant -> Material -> MRP Parameters -> Work Center

PRODUCT DESIGN

PRODUCT DESIGN

BOM -> Routing -> Production Version

PLAN

PLAN

Demand -> MRP -> Planned Order -> Supply Decision

EXECUTE

EXECUTE

Production Order -> Release -> Component Issue -> Confirmation -> Finished-Goods Receipt

ACCOUNT & CLOSE

ACCOUNT & CLOSE

Material Consumption -> Activity Cost -> Inventory Credit -> Variance -> Settlement

FEEDBACK

FEEDBACK

Actual Quantity -> Actual Time -> Shortage / Exception -> Updated Stock / Capacity Reality -> Next Planning Cycle

01

P2M PRACTITIONER WORKBENCH

Enterprise and planning foundation

Set the organizational and planning foundation before any material is tested. Treat MRP Area as a design decision, not a casual mandatory switch.

Configuration and data focus

Plant, planning horizon, plant MRP parameters, MRP controller, plant-level planning or MRP-area planning, scheduling assumptions, valuation area and FI/CO handoff assumptions.

Maintain in dependency order

  1. Confirm the plant, valuation area, factory calendar, planning horizon and owner of the discrete-manufacturing scenario.
  2. Choose Plant-Level Planning or MRP-Area Planning. Add MRP Areas only where a requirement needs separate planning for storage locations, subcontractors or distinct planning segments.
  3. Confirm plant MRP parameters, planning file behavior, scheduling assumptions and accounting handoff assumptions before creating test demand.
RUNCreate or extend one test material at the intended plant and verify that planning can evaluate it at the selected organizational level.
EXPECTED PROOF

The material is visible to planning in the intended plant or MRP area, with explainable planning horizon, controller, calendar and valuation/accounting context.

If it fails, check here first

  • Material is not planned: check plant extension, planning file, MRP type, controller, plant parameters and planning scope.
  • MRP Area behaves unexpectedly: confirm whether the scenario truly needs MRP-area planning and whether material/storage-location/subcontractor assignments are complete.
02

P2M PRACTITIONER WORKBENCH

Material and MRP master data

A material can only plan correctly when its planning, procurement, availability and strategy fields agree with the selected manufacturing scenario.

Configuration and data focus

Material Master, MRP type, lot size, procurement type, in-house production time, scheduling margin key, strategy group, availability-check setting and accounting/costing views where relevant.

Maintain in dependency order

  1. Maintain the finished-good and component material views needed by planning, production, inventory and accounting.
  2. Set MRP type, lot size, procurement type, in-house production time and scheduling margin key so quantity and date logic are explainable.
  3. Place demand architecture here: Make-to-Stock uses Planned Independent Requirements; Make-to-Order uses sales-order-driven requirements.
  4. Connect Strategy Group -> Requirement Type / Requirement Class -> Consumption / Planning Behavior -> MRP without trying to teach every strategy group.
RUNCreate demand for the material and inspect whether planning treats it as the approved MTS or MTO signal.
EXPECTED PROOF

The material shows the intended demand behavior, make-or-buy decision, lot-size response, dates, availability relevance and planning exception behavior.

If it fails, check here first

  • Demand is ignored or doubled: inspect strategy group, requirements type/class, PIR or sales-order transfer, consumption settings and material/plant context.
  • Supply form is wrong: inspect procurement type, special procurement, lot size and source decision.
03

P2M PRACTITIONER WORKBENCH

Work center and capacity foundation

Work centers give routing operations their scheduling, capacity and costing context. Do not wait until order execution to discover that operation time or cost cannot be explained.

Configuration and data focus

Work Center, standard-value key, formulas, capacity where relevant, cost center, activity type and control-key defaults where applicable.

Maintain in dependency order

  1. Create or confirm the work center with the required plant, category, standard-value key and basic scheduling data.
  2. Maintain formulas and capacity only where the scenario needs them; keep advanced capacity planning outside the minimum spine.
  3. Link cost center and activity types where operation confirmation should create activity cost.
RUNCreate a routing operation using the work center and verify that scheduling and, where relevant, activity costing can be derived.
EXPECTED PROOF

The operation can schedule with explainable duration and can carry activity values to the production order when costing is in scope.

If it fails, check here first

  • Operation cannot schedule: inspect work-center formula, standard values, calendar, capacity category and routing control key.
  • Activity cost is missing: inspect cost center/activity type relationship, activity price, formula and valuation settings.
04

P2M PRACTITIONER WORKBENCH

BOM, routing and production version

Production Version is the first-class object that ties the executable manufacturing design together for a material and plant.

Configuration and data focus

BOM, routing/task list, Production Version, validity dates, lot-size range, BOM alternative, routing or task-list assignment, material/plant production data.

Maintain in dependency order

  1. Maintain a valid BOM for the finished good and components, including quantity, validity, status and usage.
  2. Maintain a valid routing with operations, work centers, control keys and standard values.
  3. Create the Production Version that binds the valid BOM alternative and routing/task-list combination for the material and plant.
  4. Confirm validity dates, lot-size range and use in MRP, planned-order creation, production-order creation and costing where applicable.
RUNRun planning or create an order and verify that the selected production version determines the intended BOM and routing.
EXPECTED PROOF

BOM + Routing -> Production Version selection is visible and the same version supports MRP, planned order, production order and costing evidence.

If it fails, check here first

  • Production version is not selected: inspect material/plant assignment, validity dates, lot-size range, BOM status/usage, routing status and selection method.
  • Components or operations are wrong: inspect BOM alternative, routing group/counter and production-version assignment.
05

P2M PRACTITIONER WORKBENCH

Demand and MRP

Demand becomes supply only after MRP converts the approved demand signal, stock and receipts into a visible proposal. Keep this before execution.

Configuration and data focus

Demand source, PIR or sales-order requirement, strategy/requirements behavior, MRP Live / MD01N, MD04 coverage review, planned order and conversion decision.

Maintain in dependency order

  1. Create controlled demand for 10 finished goods using the selected demand architecture.
  2. Run MD01N / MRP Live or the approved planning run for the material and plant.
  3. Review MD04 / coverage to explain demand, stock, receipts, shortages, exception messages and the planned order.
  4. Decide whether to convert the planned order individually with CO40 or collectively with CO41.
RUNDemand = 10 FG -> MD01N / MRP Live -> MD04 / Coverage Review -> Planned Order -> Convert Planned Order -> Production Order.
EXPECTED PROOF

The demand creates an understandable supply proposal with explainable quantity, date, production version and conversion path.

If it fails, check here first

  • No planned order: inspect demand validity, stock/receipts, planning file, MRP type, procurement type, lot size and firming.
  • Wrong date or quantity: inspect lead times, calendars, scheduling margin key, lot sizing, safety stock and exception messages.
06

P2M PRACTITIONER WORKBENCH

Production order control

The production order is the governed execution object. Conversion must preserve the production model and create an order that can be released and costed.

Configuration and data focus

Production order type, order-type-dependent parameters, number range, scheduling, availability checking, release controls, production scheduling profile, settlement profile and costing linkage where relevant.

Maintain in dependency order

  1. Confirm the order type, number range, plant/order-type parameters, scheduling type and release controls.
  2. Connect order type to settlement profile and costing/valuation assumptions where the order should settle.
  3. Convert the planned order and verify dates, components, operations, production version, status and release readiness.
RUNConvert the planned order, inspect the generated production order, run availability where relevant and release only when the order is executable.
EXPECTED PROOF

The planned order converts into a valid production order with the expected type, dates, production version, components, operations, statuses and settlement/costing controls.

If it fails, check here first

  • Order cannot release: inspect status, missing components, capacity, availability check, release control, user status and authorization.
  • Order lost its design: inspect production-version selection, BOM/routing validity, order-type parameters and conversion settings.
07

P2M PRACTITIONER WORKBENCH

Shop-floor execution

Execution turns the plan into actual quantity, actual time, material movement and stock. Batch management is optional unless the scenario requires traceability or batch-specific selection.

Configuration and data focus

Reservation behavior, component issue, confirmation, backflush where relevant, goods receipt, movement types, optional batch-controlled manufacturing, stock status and order status.

Maintain in dependency order

  1. Release the order and issue components manually or through approved backflush behavior.
  2. Confirm operation quantity and time, deliberately using a partial confirmation to expose remaining work and cost state.
  3. Post finished-goods receipt for the completed quantity and inspect reservations, order status, component consumption and finished stock.
  4. Use optional batch-controlled manufacturing only when traceability, shelf life, characteristics or batch-specific production selection are required.
RUNIssue components, confirm 8 of 10, receive 8 finished goods, then inspect remaining quantity, reservations, stock and order cost before completing the final 2.
EXPECTED PROOF

Inventory and order status show what actually happened: component consumption, operation confirmation, partial receipt, remaining quantity and updated stock are all explainable.

If it fails, check here first

  • Goods issue fails: inspect reservation, available component stock, storage location, batch/serial requirement, period and movement control.
  • Confirmation or receipt is wrong: inspect control key, confirmation parameters, backflush/auto-GR settings, yield/scrap and stock type.
08

P2M PRACTITIONER WORKBENCH

Accounting and settlement

A production order is financially complete only when component consumption, activity cost, finished-goods credit, variance and settlement can be reconciled.

Component Issue

Dr Production Order - Material Consumption
Cr Raw Material Inventory

Activity Confirmation

Dr Production Order - Activity Cost
Cr Cost Center / Activity Allocation

Finished-Goods Receipt

Dr Finished Goods Inventory (BSX)
Cr Order Credit / Inventory Change (GBB/AUF)

Period End

Actual Order Cost - Order Credit = Remaining Order Balance -> WIP / Variance as applicable -> Settlement

Configuration and data focus

Component consumption, activity allocation, finished-goods receipt, OBYC account determination, BSX, GBB/VBR, GBB/AUF, GBB/AUA where separately configured, variance, settlement and production-order status.

Maintain in dependency order

  1. Prove component issue: Dr Production Order - Material Consumption / Cr Raw Material Inventory.
  2. Prove activity confirmation: Dr Production Order - Activity Cost / Cr Cost Center or Activity Allocation.
  3. Prove finished-goods receipt: Dr Finished Goods Inventory (BSX) / Cr Order Credit or Inventory Change (GBB/AUF).
  4. Where separately configured, use GBB/AUA for order settlement. AUF is associated with the goods-receipt/order-credit side and may also act as fallback depending on design.
  5. Close the order through Actual Costs - Order Credit = Remaining Order Balance -> WIP / Variance as applicable -> Settlement.
RUNProduction Order -> Actual Costs -> Finished-Goods Credit -> Delivery / TECO Status -> Variance -> Settlement -> Reconciled Order.
EXPECTED PROOF

Quantity, inventory, order cost and accounting agree: material consumption, activity cost, FG inventory, order credit, variance and settlement tell one story.

If it fails, check here first

  • Accounting is missing or wrong: inspect valuation class, price control, movement type, OBYC key, account modifier, order status and FI period.
  • Settlement fails: inspect settlement profile, receiver, variance calculation, TECO/delivery status, period-end sequence and CO/FI ownership.

Transport and data boundary

Customizing: MRP types, planning strategy configuration, order types, order-type-dependent parameters, scheduling parameters, control keys, availability-check controls, production scheduling profile where used, settlement profile, valuation/costing controls where in scope, and OBYC account determination.

Master / planning data: Material Master, Work Center, BOM, Routing, Production Version, Planned Independent Requirements, and Production Resources / Tools where used.

Transaction data: Planned Order, Production Order, Reservation, Goods Issue, Confirmation, Finished-Goods Receipt, variance calculation result, and settlement posting.

Level 3 technical reference

87 checkpointsRetained as the detailed SPRO / T-code / configuration inventory below the practitioner flow.
Open technical configuration reference

GOLDEN TRANSACTION

Prove one partial production scenario

Settings are not evidence. Use one material, plant, demand, production version and order to expose both perfect-flow and in-process state.

Demand = 10 FG

  1. Run MRP
  2. Planned Order Created
  3. Convert to Production Order
  4. Release
  5. Issue Components
  6. Confirm 8 of 10
  7. Receive 8 FG
  8. Inspect Remaining Quantity / Cost / Reservations
  9. Complete Remaining 2
  10. Calculate Variance
  11. Settle Order
  12. Reconcile

Inspect demand remaining, planned and production order status, component reservations, component consumption, finished-goods stock, operation confirmation, actual order cost, order credit, variance and settlement.

P2M Configuration Proof Model

  1. PLAN

    Does demand generate the intended supply proposal?

  2. EXECUTE

    Can the production order be released and physically processed?

  3. ACCOUNT

    Do inventory, material consumption and activity cost post correctly?

  4. RECONCILE

    Do quantity, inventory and order cost agree?

  5. FEED BACK

    Does actual execution leave the next planning cycle with the correct reality?

FINAL P2M LOOP

Execution creates the next planning reality

One Demand -> One Executable Production Plan -> One Produced Quantity -> One Reconciled Production Order -> One Updated Planning Reality.

Demand→Plan→Produce→Receive→Account→Actual Stock / Lead Time / Exceptions→Next MRP Cycle
READY FOR THE PROJECT?Continue to P2M 505

Apply the control model through design, build, integrated proof, cutover, and stabilization.

Enter the project