303
PRACTITIONER LEVELSee real-world execution

MTO 303 · PRACTITIONER PROCESS MAP

How does Make to Order execute in SAP?

A practitioner-provided view of Make-to-Order execution from quotation and sales order through credit control, customer-specific manufacturing, delivery, goods issue, billing, accounts receivable, and accounting postings.

Make-to-Order practitioner diagram showing sales quotation and order, credit check, manufacturing requirement, confirmation, customer-specific manufacturing, delivery, goods issue, billing, accounts receivable, revenue, inventory, and cost-of-goods-sold postings.
Practitioner-supplied Make-to-Order business process discussion. Open the diagram for a full-size view.

READ THE PROCESS

The sales order is both a commercial document and a supply signal

MTO succeeds only when the requirement reference survives from the accepted customer promise through planning, production, stock assignment, delivery, billing, and financial closure.

01SPECIFY & ACCEPT

Create executable customer demand

Product or configuration, quantity, requested date, price, partners, credit, item and schedule-line behavior, and requirement transfer determine whether the sales order can trigger supply.

02PROMISE & PEG

Connect the date to feasible supply

Scheduling and availability expose the supply date. MRP creates internal or external proposals whose customer reference, firming, and exceptions must remain visible.

03PRODUCE & ASSIGN

Execute without losing ownership

BOM, routing, work center, production version, order release, goods issue, confirmation, inspection, and receipt create output assigned according to the approved MTO design.

04DELIVER & CLOSE

Make quantity, revenue, cost, and margin agree

Delivery and goods issue prove fulfilment; billing creates the receivable. Production cost, variance, results analysis where applicable, and settlement complete different parts of the story.

COMMON PP SPINE

Four foundations must retain the customer reference

When the chain breaks, follow the sales-order item and requirement rather than treating Sales, Planning, Production, Logistics, and Finance as separate investigations.

THE STRATEGY BRANCH

Order-specific demand does not force one stock or cost model

The approved design decides how tightly components, output, value, and profitability remain assigned to the originating sales-order item.

Design choiceOwnership behaviorPractitioner evidence
Individual requirementsSupply is planned for a specific sales-order requirement and protected from unrelated demand.Requirement assignment, pegged proposals, stock segment, availability, and document references.
Collective componentsSelected lower-level supply is shared while the finished requirement remains customer-specific.BOM-level strategy, collective stock, dependent requirements, allocation, shortage ownership, and date impact.
Valuated or non-valuated order stockQuantity and value may follow different assignment and settlement behavior.Requirements class, account assignment, valuation, goods movements, receiver, results analysis where used, and settlement proof.

QUANTITY AND VALUE HAND-OFFS

Production completion, delivery, billing, and profitability are different gates

A delivered order can still have incomplete billing or cost closure. Reconcile the customer requirement across logistics and Finance rather than relying on one completion status.

PRODUCTION EXECUTIONMaterial and activity cost collectYield and assigned output emerge

Confirm component ownership, issues, confirmations, scrap, receipts, stock assignment, valuation, reversals, and production-order status.

OUTBOUND GOODS ISSUEAssigned output leaves stockCost-of-sales impact follows the approved design

Confirm delivery quantity, batch or serial data, stock segment, movement, material document, accounting document, and reversal status.

BILLINGRevenue and receivable are recognizedCommercial status advances

Confirm billing relevance, quantity, price, tax, account determination, billing block, invoice, accounting document, and sales-order reference.

ORDER ECONOMICSCost, variance, and revenue are comparedApproved receivers are settled

Confirm cutoff, results analysis where applicable, production variance, settlement rules, profitability characteristics, ledger postings, and residual balances.

PRACTITIONER VIEW

What to watch across the customer-specific chain

The practitioner protects promise credibility, requirement ownership, change control, and explainable economics.

01

Requirement integrity

Configuration, quantity, requested date, rejection, cancellation, credit, incompletion, and change history can alter supply after it has been created.

02

Pegging and exceptions

Component shortages, external procurement, collective assemblies, rescheduling, firmed proposals, substitutions, and capacity constraints change the confirmed date.

03

Assigned execution

Release, component ownership, partial yield, rework, scrap, inspection, sales-order stock, batch or serial identity, and reversals must retain the correct reference.

04

Commercial closure

Delivery, billing, production cost, variance, results analysis, settlement, margin, open quantities, and residual balances must tell one customer-order story.

WHEN THE CHAIN BREAKS

Start with the sales-order item and its requirement

The missing production, delivery, or billing successor is often caused by an earlier determination or ownership decision.

NO ORDER-SPECIFIC SUPPLY

Was demand transferred correctly?

Check item and schedule-line categories, requirements type and class, strategy group, account assignment, configuration completeness, plant, transfer status, MRP relevance, planning run, and exception messages.

OUTPUT CANNOT DELIVER

Is the stock assigned and available?

Check production receipt, stock segment, sales-order assignment, batch or serial status, quality stock, confirmation, delivery relevance, schedule line, due date, blocks, and picking location.

MARGIN OR SETTLEMENT DIFFERS

Which commercial or cost event is incomplete?

Compare production issues and confirmations, receipts, goods issue, billing, price, revenue account, target and actual cost, variance, results analysis, settlement rule, profitability assignment, and reversals.

CONTINUE THE PATHContinue to MTO 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