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.

Vue du processus et contexte metier

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.

Flux end-to-end

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

Tables cles

Table	Explication
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.

Parcours etape par etape

Review planning inputs

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

A surveiller: MRP cannot compensate for bad master data.

Convert the right proposal

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

A surveiller: Do not convert every proposal without checking dates and quantities.

Control execution

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

A surveiller: Backflush errors often reveal missing components or wrong BOM validity.

Close the order

Post goods receipt, analyze variances and settle where required.

A surveiller: Unsettled orders hide production cost issues.

Erreurs courantes et resolution

No planned order created

Cause probable: MRP views, planning file, lot size or demand source is missing.

Chemin de correction: Check MD04, material master MRP views and planning file entry.

Component not backflushed

Cause probable: BOM item, storage location or backflush indicator is wrong.

Chemin de correction: Inspect BOM item, work center and production supply settings.

Order variance is unexpected

Cause probable: Actual consumption, activity confirmation or standard cost differs from plan.

Chemin de correction: Analyze component issue, confirmations and costing data.

Differences ECC vers S/4HANA

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

Glossaire

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.

Test de connaissances

Obtenez au moins 70 % pour débloquer le certificat.

Lancer le générateur