Teams who have just gone live
The implementation ended, the consultants left, and the people now running the close were trained on a system that has since been configured differently. This is the most common reason we are called.
Corporate training
Training Built Around Your System, Not a Demo.
In-house workshops on SAP S/4HANA Group Reporting and SAP Analytics Cloud for finance and finance systems teams — delivered by the people who design these solutions, using your configuration rather than a standard sandbox.
Why this exists
Most teams were trained on a system that no longer looks like theirs.
Implementation training usually happens before the final round of design changes, on a system configured for a demonstration, delivered to whoever was available that week. By the second close, half the people running the process were not in the room, and the configuration has moved.
What is left is a team that can follow a runbook but cannot explain a result. That is fine until something is unexpected — and in group consolidation, something is always unexpected.
Who it is for
Four situations where this helps most.
Teams about to go live
Enablement ahead of cutover, run against your own configuration rather than a demo system — so the first close is not the first time anyone has seen it.
Finance teams inheriting a solution
New joiners, a restructured group function, or a team taking ownership back from an implementation partner and finding nobody can explain why it was built this way.
IT and finance systems teams
People supporting Group Reporting or SAC who understand the technology but need the accounting and process context behind the configuration.
Curriculum
Two programmes, shaped to your scope.
These are the areas we cover. Which of them matter, and in what depth, depends on your solution and who is in the room — we agree the scope before we build the material.
SAP S/4HANA Group Reporting
- Consolidation model: structures, versions, FS items and the data model behind them
- The consolidation monitor and what each task actually does
- Currency translation, including CTA and where differences come from
- Intercompany matching and elimination, and reading a reconciliation difference
- Ownership, non-controlling interests and consolidation of investments
- Group structure changes: acquisitions, disposals and step changes mid-period
- Validation, data collection and the controls around submission
- Reporting on the consolidated result, and where each figure originates
- Close-cycle operation: sequence, dependencies and what to do when it breaks
SAP Analytics Cloud
- Planning model architecture: dimensions, measures, versions and categories
- Data actions and multi-actions — reading, running and maintaining them
- Allocation logic and how to trace a number back through it
- Currency handling in planning models
- The planning cycle: seeding, submission, workflow and locking
- Story and reporting design, and building something maintainable
- Live versus imported connections and what each constrains
- Integration with S/4HANA and Group Reporting results
- Performance, model hygiene and knowing when a model needs rework
How it runs
What makes this different from product training.
Built around your configuration
We ask for access to your system, or a sanitised copy, and build the material around what you actually have. Generic product training is available from plenty of places and is not what this is.
Delivered by practitioners
The sessions are run by people who design and deliver these solutions, not by trainers working from a deck. That means questions about your specific design get answered in the room.
Accounting alongside the clicks
Knowing which button to press is the easy half. We teach why the consolidation behaves as it does, so the team can reason about an unexpected result rather than raise a ticket.
Scoped to the group
One to three days depending on scope and audience, on-site or remote, for a single team rather than a public cohort. Small enough that everyone can ask.
What changes afterwards
What a good workshop leaves behind.
- The close can be run and explained by the people who own it
- Fewer escalations that turn out to be misunderstandings rather than defects
- The team can trace an unexpected figure back to its source unaided
- Design decisions in your solution are understood, not just inherited
- A documented record of what was covered, for onboarding the next joiner
Beyond the two curricula
Tailored client training.
The two programmes above are our standard curricula. Where the need is broader — a handover, a close-cycle rehearsal, a super-user capability build, or a refresh after an optimisation changed how something works — we build the programme around your process and operating model rather than around a product.
Practicalities
How to scope one.
Tell us which platform, roughly how many people, what they do day to day, and what triggered the request — a go-live, a handover, a team change, or simply a close that was harder than it should have been.
From there we propose a scope and duration. Workshops run on-site or remotely, and are delivered for a single organisation rather than as a public course, so the material and the examples can be entirely yours.
- One to three days for the standard curricula, half a day upwards for tailored programmes
- Built on your configuration, or a sanitised copy of it
- Delivered by the people who design these solutions
- A documented record of what was covered, for onboarding the next joiner
Training enquiry
Start from what the team should be able to do afterwards. We reply by email, usually within one working day.
Thank you — your enquiry has been sent.
We have received your message and will come back to you by email, usually within one working day. If your question is time-critical, email us directly at info@radixa.co.uk.
Next step
Tell us what your team needs to be able to do.
Start with the capability gap rather than a course outline, and we will tell you honestly whether a workshop is the right answer or whether the problem is in the solution design.