Document flow as evidence

Sign-off is a statement that the system does what the business needs. It should be backed by evidence another person can check. Document flow is the best evidence SAP gives you, because it shows the whole chain and the outcome, not just one step.

Why a success message is weak evidence

A message such as "Standard Order 1000457 has been saved" proves one thing: a document was created. It does not prove the price was right, the goods left stock, the invoice was correct, or finance received the right posting. Screenshots of success messages are the most common, and least useful, evidence in SAP test packs. A reviewer cannot tell from them whether the business result happened.

Weak: success messageA document was saved. Says nothing about values or downstream steps.

Better: document displayThe document holds the expected customer, product, quantity and price.

Strong: document flow with statusesEvery expected successor exists and each step is complete.

Strongest: flow plus accounting result checked against expected valuesThe journal entry shows the right accounts, amounts, profit center and segment.

Levels of evidence for a process test.

What to capture in a sign-off pack

For each end-to-end scenario, a reviewer should be able to answer: which documents were created, are they all complete, and is the financial result right? A compact evidence record does that:

Evidence item	Order-to-cash example (Contoso)	Procure-to-pay example (Contoso)
Scenario and data	Sell 50 CMC-ALT-100, sales area 1710 / 10 / 00, plant 1710	Buy 500 CMC-RTR-200, purchasing org 1710, plant 1710
Document numbers	Order 1000457, delivery 80001234, goods issue 4900007731, billing 90001877	PO 4500002210, GR 5000001876, invoice 5105600099
Statuses	Order completed; delivery goods issue posted; billing posted to accounting	PO history GR 500 / IR 500; invoice not blocked
Accounting result	Journal entries for goods issue and billing with accounts, amounts, profit center	Journal entries for GR and invoice; GR/IR nets to zero
Expected vs actual	Price, tax and revenue account as specified	Price per PO; inventory account per valuation class
Tester and date	Name, date, system and client	Name, date, system and client

A minimal evidence record per scenario. Numbers are fictional.

Capturing the flow well

A screenshot of the document flow tree, expanded so every successor and status is visible, is far more useful than a screenshot of the save message. Better still, record the document numbers in your test log as you go; anyone can then display the documents again in the test system. Where your project uses SAP Solution Manager or SAP Cloud ALM for test management, attach the evidence to the test case there so it is versioned with the run.

When the flow is incomplete

Incomplete flows are findings in their own right. A billing document without a journal entry, a delivery without goods issue, a PO with receipts but no invoice: each says the process stopped somewhere. Report the last complete document and the missing successor. That tells the fixer exactly where to look.

Are all expected documents present in the flow?Yes → check statuses · No → record the last complete document and the missing successor as a finding
Is every document's status complete?Yes → check values · No → record which status is incomplete and why
Do the values and accounting result match the expected result?Yes → pass, with evidence attached · No → fail, with expected and actual side by side

Judging a process test from its document flow.

What would you do?

A Contoso test pack for 25 order-to-cash scenarios contains, for each, a screenshot of the billing success message and the word "Pass". The release goes live tomorrow and the process owner is asked to sign. What is the most responsible action?

Key points