Scoping UAT with process owners

UAT scope is not "everything we tested in SIT." It is the set of business processes, variants and roles that process owners need to see working before they will accept the system. Getting there takes a working session with each process owner, a list of what is in the solution, and a clear view of who does what in the business.

Your solution scope already exists. In an SAP Activate project it is expressed as SAP Best Practices scope items and solution processes (for example BD9, Sell from Stock), plus the customer-specific processes added in Explore. If the project uses SAP Cloud ALM, the solution processes live in the project's scope and can be linked to requirements and test cases. If it uses SAP Solution Manager, the equivalent is the solution documentation. Either way, start UAT scoping by listing in-scope processes, then ask the process owner three questions about each one.

Does the business run this regularly, or is it critical when it happens? Daily order entry and month-end close are both in, for different reasons.
What variants matter? Contoso sells from stock to fleet customers and also ships aftermarket orders from plant 1720 Chicago. Those are different variants of the same process.
Who performs each step? The answer gives you roles, and roles give you testers and test users.

Solution scopeScope items and solution processes in the project (e.g. BD9 Sell from Stock)
Process owner reviewMark business-critical processes and the variants that matter
Role mappingMap each process step to the business role that performs it
UAT scenariosWrite day-in-the-life scenarios that span steps and roles
Agreed scopeProcess owner confirms in writing what UAT will and will not cover

Deriving UAT scope from scope items and roles.

The Sign-Off Table · thesignofftable.com/academy/sap-tst-204

Prioritize with risk

No program has time to accept every variant. Use a simple two-factor view with the process owner: how often the process runs, and how much damage a failure would do. High-frequency, high-impact processes get full UAT with several variants. Rare but critical ones, such as year-end close or a recall, get at least one scenario. Low-impact, low-frequency variants may rely on SIT evidence, and the process owner should agree that explicitly.

Rely on SITRare, low-impact variants; process owner accepts SIT evidence in writing

Must test, one scenarioRare but critical, such as year-end steps or credit memo reversals

Light UATFrequent but forgiving; one happy path per role

Full UATDaily and critical: order entry, goods issue, billing, supplier invoice, payment run

Use frequency and impact to set UAT depth per process.

The Sign-Off Table · thesignofftable.com/academy/sap-tst-204

Why roles belong in scope

An SAP S/4HANA process is performed by people in business roles. A sales order at Contoso is created by someone in an internal sales representative role, released from credit block by a credit controller, picked by a warehouse clerk and billed by a billing clerk. SAP delivers business role templates (for instance SAP_BR_INTERNAL_SALES_REP) that projects copy and adjust, and in on-premise and private cloud systems those roles are maintained as PFCG roles assigned to users.

UAT must run with production-like role assignments. If testers log on with a broad test profile, every authorization gap is hidden until go-live morning, when Maria's team cannot release a delivery because the role lacks one authorization object. Running UAT with the real roles is the cheapest authorization test you will ever do, and it also proves the Fiori launchpad shows each role the apps it needs.

Process step (BD9-style flow)	Contoso role	UAT tester
Create sales order for Great Lakes Fleet Services	Internal sales representative	Maria
Release credit block	Credit controller	AR team lead
Pick and post goods issue, shipping point 1710	Warehouse clerk	Detroit shift lead
Create billing document	Billing clerk	Billing specialist
Review revenue and COGS postings in 1710	General ledger accountant	Dan's delegate

A role map turns a process into testers and test users.

What would you do?

Dan wants UAT for finance to cover "all of finance, exactly like SIT." Priya has three weeks and six finance testers. What is the best next step?

Key points

Derive UAT scope from the solution scope: scope items, solution processes and customer-specific processes.
Use frequency and impact with each process owner to decide depth.
Map process steps to business roles, and roles to named testers.
Run UAT with production-like role assignments to expose authorization gaps early.
Record exclusions and their reasons in a scope agreement the process owner approves.

Prioritize with risk

Why roles belong in scope

Lesson check