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

Lesson 6 of 6

Testing service and consumable procurement

7 min

Service and consumable tests have one thing in common: the evidence is on the cost object and in the approval history, not in stock. A tester who looks only for a PO and an invoice will miss the two things that go wrong most often: the wrong approver and the wrong account.

Contoso's test set

TestSetupExpected result and evidence
SV-01 planned servicePO with 4 inspections; entry sheet for 1Approved; $4,800 on cost center Detroit maintenance; open quantity 3
SV-02 limit item within limitEntry sheet $2,000 against the limit itemApproved; remaining limit reduced
SV-03 limit exceededEntry sheet beyond the remaining limitRefused
SV-04 approval thresholdEntry sheets at $4,999 and $5,001Below: automatic or simple approval per design; above: maintenance supervisor
SV-05 rejectionApprover rejectsNo receipt, no journal entry; creator can correct
SV-06 revocationRevoke after approval, then after invoiceFirst allowed, receipt reversed; second refused
SV-07 invoice matchRiverbend invoice equals approved entry sheet; then one $500 higherFirst posts unblocked; second blocked per tolerance
CN-01 consumable valuated GRGloves, K, cost center Detroit assemblyExpense at receipt on the right G/L account
CN-02 wrong account assignmentEquipment over $5,000 with KRouted to asset accountant per design
CN-03 classic run-outConverted item category D PORecorded in ML81N; accepted; invoiced

Service and consumable tests with their evidence.

  1. BeforeCost center balance for Detroit maintenance; PO open quantity and remaining limit
  2. ExpectedApprover, posting amount, G/L account, cost object, remaining limit
  3. ExecutePlanner records; approver approves with real roles
  4. AfterEntry sheet status, approval history, receipt document, journal entry
  5. CompareCost center up by expected amount; limit and quantity reduced correctly
The before-and-after method for a service entry sheet.
The Sign-Off Table · thesignofftable.com/academy/sap-mm-206

Approval evidence

For every approval test, keep the workflow history from the entry sheet (who received it, who approved, when), not just the final status. A test that ends in "approved" can still fail: if it was approved by the planner who created it, the separation of duties is broken. Run tests with separate users for creator and approver, and include one test where the creator tries to approve their own entry sheet.

No proof, no approvalUnacceptable: invoice paid on trust
Proof, no approvalWeak: planner records and nobody checks
Approval, no proofWeak: approver signs without seeing the work report
Proof and independent approvalTarget: work report attached, supervisor approves in My Inbox
What a strong service confirmation looks like.
The Sign-Off Table · thesignofftable.com/academy/sap-mm-206

Period-end and accounts

Approve one entry sheet on the last day of a period and one on the first day of the next, and check the posting period of each. Then ask Dan's team to check the expense accounts and the GR/IR balance for Riverbend: after SV-07, GR/IR for the PO should equal approved-but-not-invoiced entry sheets. Services are a common source of unexplained GR/IR balances, so this check belongs in the sign-off.

Plan test data with the same care as for stock materials. Each test needs a service supplier set up in client 100 with an email address for output, a cost center with an owner who exists as a test user, approvers with the right roles, and service products or material groups that map to the intended G/L accounts. Reusing Lakeside Components for a service test is tempting but proves nothing about the service supplier's master data, which is where many real defects hide.

What would you do?

SV-04 passes: the $5,001 entry sheet was approved. But the history shows the approver was the same maintenance planner who created it, because he also holds the supervisor role in client 100. What should Priya do?

Key points
  • Evidence for services and consumables is on the cost object and in the approval history.
  • Test planned items, limits, thresholds, rejection, revocation and invoice matching.
  • Use separate users for creator and approver; test self-approval explicitly.
  • Check posting periods at month end and explain GR/IR by entry sheet.

Check your understanding · not graded

Lesson check

  1. 1. What evidence shows who approved a service entry sheet?

  2. 2. How should a limit check be tested?

  3. 3. Why approve one entry sheet on the last day of a period and one on the first day of the next?

  4. 4. After invoices, what should GR/IR for a service PO equal?