Why train Plan-to-Produce as an end-to-end process?

Because the user-facing step depends on upstream master data, status, integration and period-end controls.

What should support check first when the process fails?

Start with the source document, status, log, master data and authorization before changing configuration.

PP · Production Planning

Plan-to-Produce SAP S/4HANA training

Convert demand into planned orders, production orders, confirmations and goods receipt.

Prozessueberblick und Geschaeftskontext

Plan-to-Produce turns demand into executable production. It depends on material master data, BOMs, routings, work centers, MRP, capacity and shop-floor confirmations.

Learners can explain how MRP proposals become production orders and how confirmations and goods receipts affect inventory and finance.

End-to-End-Ablauf

1
Capture demand
MD61 / Sales order
Fiori-App: Manage PIRs; Monitor Demand
ACDOCA-Auswirkung: No direct posting; creates planning requirement.
2
Run MRP
MD01N
Fiori-App: Schedule MRP Runs
ACDOCA-Auswirkung: Creates planned orders or purchase proposals.
3
Convert planned order
MD04 / CO40
Fiori-App: Manage Planned Orders
ACDOCA-Auswirkung: Creates production order with BOM and routing.
4
Confirm production
CO11N
Fiori-App: Confirm Production Operation
ACDOCA-Auswirkung: Posts activity and can trigger backflush.
5
Post goods receipt
MIGO / CO15
Fiori-App: Post Goods Movement
ACDOCA-Auswirkung: Updates stock and financial inventory value.

Wichtige Tabellen

Table	Erklaerung
MARA / MARC	Material master and plant planning data.
STKO / STPO	Bill of material header and item data.
PLKO / PLPO	Routing header and operation data.
AFKO / AFPO	Production order header and item data.
RESB	Component reservations for production orders.

Schritt-fuer-Schritt-Anleitung

Review planning inputs

Validate MRP type, lot size, procurement type, BOM and routing before running MRP.

Achten Sie auf: MRP cannot compensate for bad master data.

Convert the right proposal

Use stock/requirements list and exception messages before converting planned orders.

Achten Sie auf: Do not convert every proposal without checking dates and quantities.

Control execution

Release order, stage components and confirm operations with realistic yield and scrap.

Achten Sie auf: Backflush errors often reveal missing components or wrong BOM validity.

Close the order

Post goods receipt, analyze variances and settle where required.

Achten Sie auf: Unsettled orders hide production cost issues.

Haeufige Fehler und Fehlerbehebung

No planned order created

Wahrscheinliche Ursache: MRP views, planning file, lot size or demand source is missing.

Loesungsweg: Check MD04, material master MRP views and planning file entry.

Component not backflushed

Wahrscheinliche Ursache: BOM item, storage location or backflush indicator is wrong.

Loesungsweg: Inspect BOM item, work center and production supply settings.

Order variance is unexpected

Wahrscheinliche Ursache: Actual consumption, activity confirmation or standard cost differs from plan.

Loesungsweg: Analyze component issue, confirmations and costing data.

ECC zu S/4HANA Unterschiede

S/4HANA improves planning and execution visibility with MRP Live, Fiori monitoring and real-time inventory/finance integration.

Glossar

MRP: Material Requirements Planning calculation for supply proposals.
BOM: Bill of material listing components required to make a product.
Routing: Sequence of production operations and work centers.
Backflush: Automatic goods issue of components during confirmation.

Wissenstest

Schließen Sie den Test mit mindestens 70 % ab, um das Zertifikat freizuschalten.

Generator starten