Lesson 1 of 5
Coverage from scope items
13 min
Order-to-cash sign-off starts with one question: what exactly are we signing off? If the answer is "whatever the testers happened to run", the signature means little. This course brings the sales track together into a test and sign-off plan for Contoso Motor Co.'s move to SAP S/4HANA, from master data through to the customer's payment, and it starts with coverage.
Scope items as a baseline
SAP Best Practices describes standard processes as scope items, each with a process flow and test script that you can browse in the SAP Signavio Process Navigator. They make an excellent coverage baseline because they list the steps SAP considers part of the process. Your project then adds what is specific to Contoso. Scope item IDs and content change between releases and editions, so check the ones below in the Process Navigator for your release.
| Scope item | Process | Relevant course |
|---|---|---|
| BD9 | Sell from Stock | Core sales order to billing |
| BDG | Sales Quotation | Pre-sales (SD 209) |
| BDD | Customer Returns | Returns (SD 208) |
| 1EZ / 1F1 | Credit Memo Processing / Debit Memo Processing | Memos (SD 208) |
| BKK | Sales Order Fulfillment Monitoring | Monitoring (SD 302) |
| BDK | Third-party sales without shipping notification | Third-party (SD 301) |
| 1HO | Intercompany Sales Order Processing – Domestic | Intercompany (SD 301) |
Order-to-cash scope items used as a coverage baseline. Verify IDs for your release.
From scope items to Contoso scenarios
A scope item describes a process; a test scenario runs it with specific data. For each scope item, list the variants that change system behavior at Contoso: sales area, plant (1710 Detroit or 1720 Chicago), customer type (fleet or aftermarket), payment terms, pricing agreements, output channel (EDI or email), and order entry channel (manual or EDI). Each variant that drives a different configuration path needs at least one scenario.
The coverage matrix
Put scenarios in rows and the things that must be proven in columns. Every cell marked "required" needs at least one executed test with evidence before sign-off. The matrix becomes the first page of the sign-off package, so the process owner can see coverage at a glance.
| Scenario | Plant 1710 | Plant 1720 | EDI order | Credit block | Invoice by email | Cash applied |
|---|---|---|---|---|---|---|
| Sell from stock, fleet customer | Required | Required | Required | Required | Required | Required |
| Sell from stock, aftermarket | Required | Optional | Not used | Required | Required | Required |
| Return for refund | Required | Optional | Not used | Not used | Required | Required (credit applied) |
| Third-party bracket kit | Not used | Not used | Required | Optional | Required | Required |
Finding gaps
Gaps hide in three places. Custom code and interfaces: anything Contoso built or connected, such as EDI order intake or an external tax engine, is outside SAP's scope items by definition. The ends of the process: master data at the start (customer and product setup) and cash application at the end are often left to other teams and never tested end to end. Negative paths: credit blocks, rejections and authorization failures rarely appear in happy-path scripts. Walk the matrix with Maria and Dan and ask, for each column, "where is this proven?"
Master data belongs in scope
Order to cash begins before the first order: the customer must exist as a business partner with the customer role and sales area data for 1710 / 10 / 00, with partner functions, payment terms, tax classification and credit data; the product must be extended to the sales organization and plant with the right item category group and tax classification. Many go-live incidents in sales are master data defects, especially in migrated records. Include at least one scenario that creates a new customer and product through the real maintenance process and then sells to that customer, and one that sells to a migrated customer chosen at random by Luis's cutover team.
What would you do?
Grace asks Priya to confirm that order-to-cash coverage is complete. The scenarios cover every step of BD9, BDD and 1EZ. Nothing covers the EDI interface that brings in 60% of Contoso's fleet orders. What should Priya report?
- Start sign-off by defining exactly what is covered.
- Use scope items (for example BD9, BDD, 1EZ, BKK) from the Signavio Process Navigator as a baseline.
- Add company variants, extensions, interfaces and cross-process links.
- A coverage matrix shows scenarios against what must be proven, and opens the sign-off package.
- Look for gaps in custom code and interfaces, at the ends of the process and in negative paths.
Check your understanding · not graded
Lesson check
1. Where can you browse SAP Best Practices scope items with process flows and test scripts?
2. Which scope item is Sell from Stock?
3. Why are scope items not the whole coverage story?
4. Where do coverage gaps commonly hide?