303
PRACTITIONER LEVELSee real-world execution

MTS 303 · PRACTITIONER PROCESS MAP

How does Make to Stock execute in SAP?

A practitioner-provided view of Make-to-Stock execution from production-order creation and release through material issue, inspection, confirmation, finished-goods receipt, accounting postings, and settlement.

Make-to-Stock practitioner diagram showing BOM and routing readiness, production-order creation and release, goods issue, parts inspection, planned-price recalculation, production work, time confirmation, finished-goods inspection and receipt, settlement, and related accounting postings.
Practitioner-supplied Make-to-Stock execution business process discussion. Open the diagram for a full-size view.

READ THE PROCESS

The diagram starts after the most important MTS decision

The production-order flow is the execution core, but MTS begins earlier: an approved forecast and stocking policy become planned independent requirements, MRP nets them against available supply, and a planner decides which proposal should become executable production.

01DEMAND & POLICY

Decide what deserves stock

Forecast, service target, safety stock, consumption behavior, horizon, lot size, shelf life, and obsolescence exposure define the inventory risk accepted before an order exists.

02PLAN & CONVERT

Turn the net requirement into feasible supply

MRP creates dated proposals after considering stock, receipts, requirements, lead times, lot sizing, and procurement type. Conversion firms quantity and dates into a production order.

03EXECUTE & RECEIVE

Replace assumptions with shop-floor evidence

Release, component availability, goods issue, operation confirmation, inspection, and finished-goods receipt progressively update status, quantity, dates, inventory, and actual cost.

04FULFIL & LEARN

Prove the stocking policy worked

Customer demand consumes forecast where configured and draws from common stock. Fill rate, shortage, excess, coverage, forecast error, and variance feed the next planning decision.

COMMON PP SPINE

Four foundations explain the production result

When the order behaves unexpectedly, locate whether demand, engineering data, execution evidence, or stock and cost closure first became unreliable.

THE STRATEGY BRANCH

MTS is not one forecast behavior

The stocking decision remains common, but the relationship between forecast and actual customer demand changes planning, consumption, excess risk, and exception ownership.

PatternDemand behaviorPractitioner evidence
Forecast-led replenishmentSupply is planned from independent forecast demand before sales orders.PIR history, MRP result, stock coverage, forecast error, and planner decisions.
Forecast consumptionActual sales consume forecast within defined periods; excess demand can create additional supply.Requirements reduction, consumption windows, unconsumed forecast, confirmations, and exceptions.
Stock-policy replenishmentInventory thresholds and coverage rules carry more weight than a detailed sales forecast.Replenishment parameters, stock history, lead time, service level, and shortage frequency.

QUANTITY AND VALUE HAND-OFFS

Execution creates four different kinds of evidence

Order status alone does not prove inventory or cost closure. Reconcile material quantities, operation activity, received output, period-end calculation, and settlement separately.

COMPONENT ISSUERaw material leaves stockActual material cost reaches the order

Confirm movement, batch or serial data, quantity, valuation, reversal status, reservation, and order assignment.

CONFIRMATIONYield, scrap, and activity are recordedLabor or machine activity may allocate cost

Confirm operation, work center, activity quantity, rate basis, partial or final status, backflush, and correction history.

FINISHED-GOODS RECEIPTCommon stock increasesThe order receives delivery evidence

Confirm material, plant, storage and stock type, quantity, valuation, inspection, order delivery status, and reversal behavior.

PERIOD END & SETTLEMENTWIP and variance are calculated where applicableResidual order value reaches approved receivers

Confirm status, cutoff, target cost, variance categories, settlement rule, account determination, ledger posting, and zero-balance expectation.

PRACTITIONER VIEW

What to watch beyond the happy path

A strong MTS review follows both the replenishment loop and the inventory consequence.

01

Demand quality

Bias, seasonality, promotions, missing history, frozen horizons, overrides, and ownership can create supply before production ever sees an order.

02

Master-data feasibility

Procurement type, lead time, lot size, BOM validity, routing, work-center capacity, production version, and component availability must describe the same operating reality.

03

Execution differences

Late issues, excess consumption, substitutions, yield loss, scrap, rework, partial confirmations, quality stock, and reversals change future availability and order cost.

04

Inventory learning

Fill rate, shortages, slow movement, excess, shelf life, blocked stock, turns, coverage, and variance determine whether the strategy should be adjusted.

WHEN THE CHAIN BREAKS

Start with the last trustworthy planning or execution event

Do not correct a production symptom until demand, supply, status, quantity, and value have been traced in sequence.

NO SUPPLY PROPOSAL

Did MRP see a net requirement?

Check active demand, planning file, plant and MRP area, stock and receipts, MRP type, procurement type, lot size, dates, firming, planning scope, and run log.

ORDER WILL NOT COMPLETE

What readiness evidence is missing?

Check BOM and routing validity, production version, components, capacity, inspection, release checks, status, confirmations, reservations, delivery tolerance, and technical completion.

STOCK OR COST DIFFERS

Which quantity or value event differs?

Compare issues, reversals, confirmations, scrap, receipts, stock type, target and actual cost, WIP, variance, settlement rule, account determination, and receiver posting.

CONTINUE THE PATHContinue to MTS 404

Connect the practitioner flow to the configuration decisions, dependencies, transport boundaries, and end-to-end proof required to make it work.

Open configuration guide