Now accepting guest editorial from SAP, Oracle, Workday and ServiceNow practitioners.Pitch a guide
The Sign-Off Table

Lesson 5 of 5

Testing strategies

9 min

Listen to this lesson

0:00 / 4:44

Strategy behavior is easy to test badly. Create a sales order, run MRP, see a planned order and call it passed. That proves MRP runs; it does not prove consumption, segments or overflow work as designed. A good strategy test sets up a known starting point, changes one thing, and compares the stock/requirements list before and after against a written expectation.

  1. PrepareClean product in CMQ client 100: no open orders, known stock, PIRs loaded
  2. Capture beforeStock/requirements list exported or captured; totals noted
  3. ActOne change: create, change or deliver one sales order
  4. Capture afterStock/requirements list again; run MRP Live if the step needs it
  5. CompareOpen PIR, total requirement, segments and proposals against the expectation
The before-and-after pattern for planning strategy tests.
The Sign-Off Table · thesignofftable.com/academy/sap-pp-202

Test cases for strategy 40

CaseSetupActionExpected result
Consumption inside the periodPIR 400 on 1 Oct; mode 1, 20 workdaysOrder 120 for 10 OctOpen PIR 280; total 400; no new planned orders beyond 400
OverflowSameOrder 500 for 10 OctPIR fully consumed; 100 extra planned after MRP
Outside the periodSameOrder 50 for 15 Dec with no December PIR and no forward periodNo consumption; total rises by 50
Order changeAfter case 1Reduce order to 80Open PIR back to 320
DeliveryAfter case 1Goods issue for 120Stock down 120; consumed PIR stays reduced

Contoso's strategy 40 cases for CMC-ALT-100. Expected values are written before execution.

Test cases for make-to-order

For CMC-ALT-240 with strategy 20, the evidence is in the segment. After the sales order: a new individual customer segment with the order's requirement. After MRP: a planned order in that segment, lot-for-lot. After conversion and goods receipt: the production order is linked to the sales order item and the finished units sit as sales order stock for that item only. A second order must get its own segment and must not see the first order's stock.

For a strategy 20 product the evidence follows one order through its own segment, from requirement to sales order stock to delivery.
The Sign-Off Table · thesignofftable.com/academy/sap-pp-202
CheckStrategy 40 (CMC-ALT-100)Strategy 20 (CMC-ALT-240)
Where the order appearsNet requirements segment, consuming PIRsOwn individual customer segment
PIRsOpen quantity reducedNone for the finished product
MRP proposalNet shortage across all demandLot-for-lot per order
Stock after goods receiptAnonymous plant stockSales order stock for that item
Negative testOrder outside consumption period adds demandSecond order cannot use first order's stock
What to compare for each strategy.
The Sign-Off Table · thesignofftable.com/academy/sap-pp-202

Making the evidence stick

  • Use a dedicated test product or plant copy so other testers' orders do not change your totals between captures.
  • Record the consumption settings and strategy group as part of the setup evidence; a changed MRP 3 view invalidates the run.
  • Note PIR and order creation sequence and timestamps; consumption depends on it.
  • For SAP S/4HANA Cloud Public Edition, capture the Fiori stock/requirements view; the logic is the same.

Expected results are only as good as the arithmetic behind them. For each case, write the starting numbers (stock, safety stock, PIRs by date, open orders), the consumption settings, and the expected open PIR, total requirement and proposals after the action. A second person checks the arithmetic before execution. When a result differs, the first question is whether the expectation was wrong, the second whether the configuration is; only then is it a defect in the system.

A strategy test is only as good as its expected result, so the arithmetic is written and checked by a second person before anyone touches the system.
The Sign-Off Table · thesignofftable.com/academy/sap-pp-202

What would you do?

A tester reports "strategy 40 passed" with one screenshot of a planned order after creating a sales order. What should Priya ask for?

Key points
  • Test strategies with a known start, one change, and before-and-after stock/requirements lists.
  • For strategy 40: consumption, overflow, outside period, order change and delivery.
  • For make-to-order: individual segment, lot-for-lot proposal, sales order stock, isolation between orders.
  • Protect the evidence: dedicated test data, recorded settings, and creation sequence.

Check your understanding · not graded

Lesson check

  1. 1. What makes a strategy test conclusive?

  2. 2. A strategy 40 order for 500 meets a PIR of 400. What do you expect after MRP?

  3. 3. Which evidence proves make-to-order isolation?

  4. 4. Why record the MRP 3 settings as part of the test setup?