SAP Manufacturing UAT Before Go-Live: A Business-Process Testing Guide

A manufacturing SAP go-live is not ready because a planner can create a production order or a warehouse user can post a goods movement. It is ready when demand can become a finished, quality-approved product, when the product can be shipped and invoiced, and when every operational event leaves the right inventory and financial record behind it.

That is why SAP manufacturing UAT has to be business-process testing. Production Planning, Materials Management, Warehouse Management or EWM, Quality Management, Sales and Distribution, and Finance are tightly coupled. A configuration gap in one module can leave a line short of components, release blocked stock to a customer, or create a production result that Operations trusts but Finance cannot reconcile.

Build UAT around the factory’s real process variants

Start with the products, plants, shifts, supply routes, and customer commitments that will put the most pressure on the new system in the first weeks of production. A clean, make-to-stock product at one plant is useful as a baseline, but it is rarely the scenario that exposes a go-live risk.

• —Make-to-stock and make-to-order products, including any customer-specific configuration or special packaging
• —Multi-level bills of material, alternative BOMs, co-products, by-products, and substitute components where they are used in production
• —Internal production, subcontracting, external processing, inter-plant transfer, and supplier-procured components
• —Batch-managed, serialised, shelf-life-controlled, or regulated materials that require traceability through the complete process
• —Planned and unplanned changes: a supplier shortfall, failed inspection, machine downtime, rework order, urgent customer order, or amended forecast
• —Named business roles — planner, buyer, production supervisor, warehouse operator, quality inspector, customer service representative, and finance controller — using production-like authorisations

Use master data that resembles production, including material masters, BOMs, routings, work centres, production versions, lead times, valuation classes, inspection plans, supplier data, customer data, and storage locations. Simplified test data hides the dependencies that will be present after cutover.

1. Production planning: prove that demand becomes an executable plan

Production Planning UAT should begin before the shop floor. Test whether demand from sales orders, forecasts, safety stock, or dependent requirements is interpreted correctly by MRP and whether the resulting procurement and production proposals support the way the plant actually operates.

• —Demand management and MRP — validate planning strategy, lot-sizing, safety stock, reorder point, lead-time scheduling, exception messages, and the treatment of existing stock and open supply
• —BOM explosion and routing selection — confirm the right components, quantities, operations, work centres, and production versions are selected for each product and plant
• —Capacity and sequencing — review the planned dates, capacity requirements, and dispatching outcomes for constrained work centres, shift patterns, and finite-capacity rules where used
• —Planned-order conversion and production-order release — verify order type, reservation, component availability, print or digital shop papers, status changes, and approval controls
• —Execution changes — test changed quantities, revised requirements dates, alternative components, component shortages, partial completion, order cancellation, and rework

A planner should be able to explain every proposal the system creates. If MRP creates an unexpected purchase requisition, ignores an available substitute, or dates a production order after the customer commitment, the defect is operational even if the planning run completes without a technical error.

2. Materials management and procurement: test supply before the line needs it

Materials Management connects the plan to the supplier and to usable stock. UAT should prove that the organisation can source the right component, receive it into the correct stock type, and pay for it without breaking the production-order cost or availability picture.

• —Purchase requisition, source determination, approval, and purchase-order creation for both planned and urgent component demand
• —Supplier, purchasing info record, source list, quota, price, currency, unit-of-measure, tax, and delivery-tolerance behaviour for representative components
• —Goods receipt against a purchase order, including partial delivery, over-delivery, damaged delivery, batch capture, and delivery to quality inspection or blocked stock
• —Invoice verification and three-way match, including price and quantity variance, invoice block workflow, credit memo, and the GR/IR clearing impact
• —Subcontracting and external processing where used: component provision, supplier consumption, receipt of the finished or processed item, and service-entry or invoice hand-off

Do not limit procurement UAT to a purchase order that matches its invoice exactly. Manufacturing teams need to know what happens when a partial receipt arrives, a substitute component is approved, a component fails inspection, or an invoice is received before the final quantity is delivered.

3. Inventory and warehouse: reconcile physical movement with SAP stock

Inventory defects become production stoppages quickly. Test that material can move from receipt through storage, picking, staging, consumption, and finished-goods putaway without creating stock discrepancies between the warehouse and SAP.

• —Stock type and location control — unrestricted, quality inspection, blocked, consignment, project, and sales-order stock must be visible and consumable only where the process allows
• —Production supply — component reservation, warehouse task or transfer order creation, picking, staging, reversal, and return of unused components
• —Goods issue and backflush — confirm the correct component, quantity, batch, serial number, storage location, and accounting impact for manual and automatic consumption
• —Finished-goods receipt and putaway — validate handling units, destination bin, batch assignment, stock availability, labels, and downstream availability for shipment
• —Cycle count and physical inventory — prove count entry, recount, difference approval, posting, and financial reconciliation for a realistic stock discrepancy
• —Mobile and RF execution — where operators use scanners or Fiori apps, execute the scenario on the actual devices, network, and labels planned for go-live

4. Quality management: make release and traceability part of the flow

Quality Management cannot be a separate demonstration after production UAT. Test inspection triggers at goods receipt, production operation, and finished-goods receipt, then prove that a quality decision changes what Warehouse, Production, and Sales can do next.

• —Inspection-lot creation, inspection plan selection, sampling procedure, results recording, defect recording, and usage decision for inbound and production receipts
• —Stock posting after the decision — release to unrestricted stock, transfer to blocked stock, return to supplier, scrap, or route to rework as the real process requires
• —Batch and traceability records — validate that the organisation can trace a finished-goods batch back to consumed component batches, inspection results, and production order
• —Quality notifications and corrective action — test ownership, workflow, follow-up actions, and the effect of a non-conformance on open production and delivery commitments

5. Production execution: complete the order, including the exceptions

A released order is only the start of the shop-floor process. UAT should follow it through partial confirmation, labour or machine time capture, component consumption, yield, scrap, rework, final confirmation, and receipt of the finished product.

• —Partial and final confirmations, including milestone confirmation, operation sequencing, yield, scrap, rework, and capacity updates
• —Component issue, backflush, reversals, and substitutions when actual consumption differs from the BOM
• —Finished-goods receipt, batch assignment, serialisation, inspection trigger, and status update on the production order
• —Order close, technical completion, settlement, and the handling of late postings after the order is complete
• —Exception paths: machine downtime, missing component, failed quality result, quantity overrun, order split, rework, and production cancellation

The high-value test is not whether the happy path confirms. It is whether the system preserves the right stock, order status, cost, and traceability when production deviates from plan — which it will.

6. Order-to-cash: prove that finished goods can become revenue

Manufacturing UAT must include the customer-facing end of the process. A finished product that cannot be promised, delivered, billed, or returned correctly is still a go-live failure, even when the production order is complete.

• —Sales order entry, pricing, availability check, allocation, credit check, and confirmed delivery date for manufactured products
• —Delivery creation, warehouse picking and packing, batch or serial selection, post goods issue, output, and transport or EDI integration
• —Billing, tax, revenue account determination, invoice output, cash application, and reconciliation to the originating sales order and delivery
• —Partial delivery, backorder, delivery split, customer return, credit memo, quality hold, and replacement shipment scenarios
• —ATP and rescheduling after a production delay, supplier shortage, quality rejection, or competing high-priority demand

7. Finance and controlling: reconcile every operational hand-off

Finance should participate in manufacturing UAT from the start, not receive a summary at the end. Every goods movement, confirmation, invoice, settlement, delivery, and bill creates a FI or CO consequence. Review the resulting accounting documents with the business event that created them.

• —Material valuation and account determination for component receipt, component consumption, finished-goods receipt, stock transfer, scrap, and inventory difference
• —Production-order actual costs, activity allocation, overhead, work-in-progress, variance calculation, settlement, and the receiving cost object
• —Procurement and accounts payable hand-offs — goods receipt, invoice receipt, GR/IR, blocked invoice, payment, and supplier-credit scenarios
• —Sales and accounts receivable hand-offs — post goods issue, cost of goods sold, billing, tax, revenue recognition where in scope, credit memo, and cash receipt
• —Cost centre, profit centre, plant, company code, and intercompany derivation for the process variants that cross organisational boundaries

“A manufacturing SAP test is not complete when the product exists in the system. It is complete when Operations can make it, Quality can release it, Warehouse can move it, Sales can ship it, and Finance can reconcile it.”

Set manufacturing go-live criteria around evidence, not script completion

Before recommending go-live, bring production, supply chain, quality, warehouse, customer service, and finance leads together to review evidence from the end-to-end scenarios. The decision should distinguish between a script marked passed and a process proven under conditions the business will actually face.

• —Critical manufacturing process variants have been run end-to-end by representative business users with production-like roles and data
• —Stock, batch, serial, and quality records reconcile across production, warehouse, and sales hand-offs
• —MRP, procurement, production, and delivery exceptions have named workarounds or resolved defects before cutover
• —FI/CO and subledger postings reconcile to the operational events, with Finance accepting the valuation, variance, and settlement outcomes
• —Open defects have a clear business impact, owner, workaround, target date, and accountable business acceptance; no unresolved defect can stop safe production, shipment, or financial control

Independent UAT makes this evidence more credible because it tests from the factory and business perspective rather than from the configuration specification. For a SAP manufacturing go-live, that is the difference between knowing the modules work and knowing the operation can run.