Lesson 1 of 5
Training by role
8 min
In the SAP Activate methodology, end-user training sits in the Deploy phase, alongside cutover and go-live. By then, key users know the new system better than anyone outside the project team. That makes them the natural trainers, and it makes training one of their most important deliverables. Users who were not trained, or were trained on the wrong things, become the first wave of hypercare tickets.
The principle of this lesson is simple: train people for the job they will do on Monday, using scenarios that have been tested. Not every app, not every option, and not a tour of the menu.
Start from roles, not from transactions
SAP S/4HANA grants access through business roles, and the launchpad shows each user the apps in their role. Training should follow the same structure. List the business roles in scope, count the people in each, and map each role to the scenarios it performs. At Contoso, Maria builds the map for order to cash.
| Business role at Contoso | People | Scenarios to train | Format | Duration |
|---|---|---|---|---|
| Internal sales representative | 14 | Create and change sales orders; check availability; handle credit blocks; returns | Classroom with hands-on exercises in the training client | 1 day |
| Shipping specialist | 9 | Create deliveries; pick, pack, post goods issue; print documents | Hands-on at the warehouse, plus work instructions | 0.5 day |
| Billing clerk | 4 | Billing due list; release blocked billing; credit memos | Classroom | 0.5 day |
| Sales manager | 5 | Sales KPIs and reports; approve price exceptions | Short demo and a work instruction | 1 hour |
Contoso's order-to-cash training map (extract).
- List rolesBusiness roles in scope and the people assigned to each
- Map scenariosWhich tested scenarios each role performs, by frequency and risk
- Choose formatClassroom, hands-on lab, short demo, work instruction or e-learning
- Build materialsExercises and work instructions from tested scenarios
- Deliver and verifyTrain in the training client; check users can do the job, not just attend
Teach the change, not just the screen
Contoso's users have worked in SAP ECC for years. Many will find the same business steps in new places: the Fiori launchpad instead of the SAP Easy Access menu, business partners instead of separate customer and vendor masters, new apps for credit management or billing. For each role, list the three to five changes that matter most compared with how they work today and open each session with them. Users forgive a new screen; they struggle with an unexplained change in who does what, such as a credit check that now stops orders earlier in the process.
Large rollouts often use train-the-trainer: key users train a group of super users in each department, who then train their colleagues and stay as the first point of contact in hypercare. It scales well, but only if the super users are trained on the same tested materials and get time in the training client to practice before they teach.
Why training must use tested scenarios
Training on untested steps teaches users a process that may change or not work. When a trainer improvises a variant in front of 14 sales reps and it fails, confidence in the system drops in the room. Build every exercise from a scenario that passed in integration or user acceptance testing, with the same data patterns: Great Lakes Fleet Services as the customer, CMC-ALT-100 as the product, sales area 1710 / 10 / 00. If configuration changes after the test, the training material needs a re-check too.
The training environment
Train in a dedicated training client, Contoso's client 200, with training users that mirror the real business roles. A training client that grants everyone broad access hides authorization problems until Monday. Refresh the data before each wave so exercises work: enough stock in plant 1710, open orders to deliver, customers without credit blocks unless the exercise needs one. Agree the refresh with the basis team early; it is often the first thing forgotten.
- Go-live minus 8 weeksTraining plan signedRoles, people, scenarios, formats, trainers and rooms agreed
- Minus 6 weeksMaterials builtExercises and work instructions from tested scenarios; training client prepared
- Minus 4 to 2 weeksTraining wavesRole-based sessions; attendance and proficiency recorded
- Minus 1 weekRefresher and readinessShort refreshers; training completion reported to go/no-go
Measuring readiness, not attendance
An attendance list says people were in the room. It does not say they can do the job. End each session with a short practical check: each sales rep creates an order for a given customer and product and releases it from a credit block, unaided, in the training client. Record the result per person. The go/no-go meeting needs a readiness figure such as "13 of 14 sales reps completed the practical check; one rescheduled for Thursday", not "training delivered".
What would you do?
Two weeks before go-live, a configuration change alters how Contoso's sales reps release orders from credit block. Training for that role is scheduled for tomorrow and the materials show the old steps. What should Maria do?
- End-user training belongs to the Deploy phase and is a key user deliverable.
- Plan training by business role: people, scenarios, format and duration.
- Build exercises only from tested scenarios with realistic data.
- Train in a training client with role-based users and refreshed data.
- Measure readiness with practical checks, not attendance.
Check your understanding · not graded
Lesson check
1. In which SAP Activate phase does end-user training take place?
2. Why should training exercises use tested scenarios?
3. What is the best measure of training readiness?
4. Why should training users mirror real business roles?