How SAP experience is really measured

Written by an SAP Finance & Treasury practitioner working with SAP since 2008 · how the guides are written · Updated 2 October 2026

Years of SAP experience are counted from your first hands-on SAP role, but the market measures what filled them: completed implementation cycles, the phases you were present for, depth in each SAP area, the role you held and the release you worked on. Two people with the same year count can have records worth very different amounts.

How are years of SAP experience counted?

From the point you first worked in or on an SAP system as part of your job, and per area rather than in total. Recruiters screening against "five years of SAP SD" will count only the time you spent configuring or supporting sales and distribution, not the years you spent in finance before it; a second area starts its own clock once you have owned work in it. Training courses and sandbox practice are not counted as years at all, and part-time exposure — a key user who spent a fifth of the week in SAP — is read as the share it was. The year count is a filter that gets a CV past the first screen; what happens after that depends on what the years contained.

What counts as a full-cycle implementation?

A project you were on from design through go-live and into the first period-end afterwards. In SAP Activate terms that means the explore phase's fit-to-standard workshops, the realise phase's configuration and testing, the deploy phase's cutover and hypercare, and enough of run to see the first close. Each phase teaches something the others cannot, and interviewers probe the late ones because that is where people who joined only for testing are found out. Partial involvement is worth stating as partial — "joined at integration test, stayed through hypercare" is credible, and claiming more is not.

How do recruiters weigh each kind of SAP experience?

Differently by type, and the gap between types is wider than most candidates expect. The table sets out how each common kind of experience tends to be read.

The guides on moving from key user to consultant and on AMS and production support cover how to make the lighter-weighted rows read stronger.

Does S/4HANA experience count for more than ECC?

For most current roles, yes — because most current projects are S/4HANA projects. Clients migrating before the end of ECC maintenance want people who know what changed: the universal journal in finance, the business partner replacing separate customer and vendor masters, Fiori apps alongside or instead of classic transactions, and the clean-core approach to extensions. A conversion from ECC is valuable precisely because it needs both. Long ECC experience does not disappear — the business processes are largely the same — but it needs at least one S/4HANA project, or demonstrable S/4HANA training on top, to be read as current.

Do agencies, delivery managers and in-house teams read it the same way?

No. An agency recruiter screens for area, role and availability first, then for keywords that match the client's brief. A delivery manager staffing a workstream asks whether you could own it next month without supervision, which recent cycles in the same project shape answer and unrelated breadth does not. In-house teams weigh live-system experience — support rotations, closes survived — above programme count. The contract market reads the most recent comparable project heaviest and expects a reference from it.

Which experience counts for less than people expect?

Courses without delivery behind them, certificates standing alone, sandbox configuration once real projects exist, and areas you touched but never owned. Courses and a certification help open the first door, not the second, and listing every area you have seen widens a profile and thins it at once.

How should you state your SAP experience?

As four facts a screener can check before any detail: the year you started with SAP, your primary role, the two or three areas you would defend in a workshop, and the number of completed cycles. Round each one down rather than up, because the market is small and references travel. Laying those facts out project by project is the subject of the guide to an SAP CV that gets read.