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.

Process overview and business context

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 flow

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

Key tables

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

Step-by-step walkthrough

Review planning inputs

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

Watch out for: MRP cannot compensate for bad master data.

Convert the right proposal

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

Watch out for: Do not convert every proposal without checking dates and quantities.

Control execution

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

Watch out for: Backflush errors often reveal missing components or wrong BOM validity.

Close the order

Post goods receipt, analyze variances and settle where required.

Watch out for: Unsettled orders hide production cost issues.

Common errors and troubleshooting

No planned order created

Likely cause: MRP views, planning file, lot size or demand source is missing.

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

Component not backflushed

Likely cause: BOM item, storage location or backflush indicator is wrong.

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

Order variance is unexpected

Likely cause: Actual consumption, activity confirmation or standard cost differs from plan.

Fix path: Analyze component issue, confirmations and costing data.

ECC to S/4HANA differences

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

Glossary

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.

Knowledge check

Certificate unlock करने के लिए कम से कम 70% score करें।

जेनरेटर शुरू करें