SAP runs the back office of a large share of German industry: the enterprise software that tracks inventory, runs payroll, manages supply chains and closes the books at companies most of the DACH job market is built around. Because of that, "SAP skills" shows up constantly in job ads and CV advice aimed at students in Germany. It is also one of the most confusing phrases you can put on a CV, because it does not describe one job. It describes at least five.
Five different jobs hiding behind one phrase
- Using SAP. The day-to-day end-user work: entering orders, checking stock, running standard reports inside the software. This is the least specialised version, closer to basic office competence than a genuine differentiator.
- Configuring SAP. Setting up modules, workflows and permissions for a specific company's processes. Closer to IT administration than programming, and usually needs training on the module involved.
- Developing on SAP. Writing custom code inside the SAP environment, traditionally in ABAP, increasingly on SAP's newer cloud and AI platforms. This is proper software engineering, aimed at a specific ecosystem.
- Analysing SAP's data. Working with the data that flows out of an SAP system, sales figures, supply chain events, financial records, using standard data and analytics skills rather than SAP-specific ones.
- Managing projects around SAP. Coordinating an SAP implementation or upgrade: timelines, stakeholders, testing, rollout. Closer to project management than to any technical specialism.
A recruiter reading "SAP skills" on a graduate CV has no way to know which of these five you mean, and many assume the least useful reading, using SAP, unless you are specific. Naming the actual category you can evidence is worth far more than the phrase on its own.
A single job advert can blur two or three of these categories in one paragraph, which is part of why "SAP experience" survives as a phrase despite being nearly useless on its own. A posting asking for SAP knowledge next to a requirement for SQL and Excel is very likely describing the data-analysis category. The same phrase next to a requirement for ABAP or a computer science degree is describing the development category instead. Reading the rest of the posting, not just the SAP mention, tells you which of the five you are actually being asked about, and it is worth doing that translation before you apply so your CV answers the right question rather than the one you assumed.
SAP skills tells a recruiter almost nothing. Which of the five jobs you actually mean tells them everything.
Why the data work is the accessible entry point
Of the five, developing on SAP and configuring SAP both usually need a corporate login, a licensed environment, and often a specific employer's training before you can build anything real. That is a genuine barrier for a student, not a lack of effort on your part.
Working with the data that enterprise systems produce is different. Supply chain events, sales transactions, inventory movements, the kind of data an SAP system generates every day, can be represented, modelled and analysed with the same tools used everywhere else in data work: SQL, Python, a BI tool, standard statistics. You do not need SAP's own login screen to prove you can reason about supply chain data, forecast demand, or build a pipeline that would sit downstream of a system like SAP in a real company. You need the data and the problem, which is exactly what a well-built project can hand you.
This is also the version of "SAP skills" most useful to a company in practice, because most graduate roles that touch SAP are not development roles. They are analyst, planning or operations roles that consume SAP's data rather than write code inside the system itself.
Two ways to build the evidence
Two ProoV projects sit squarely in this data-around-SAP category, from opposite ends of it.
The rescue-the-supply-chain project puts you inside an operations-style decision: given supply chain data shaped the way SAP produces it, what should the company actually do. The real-time data engineering project goes the other direction, toward the engineering end: it hands you a stream at genuine SAP-scale volume and asks you to build a pipeline that can keep up with it. Between the two, you get evidence for both the analysis and the engineering side of "SAP skills", without a corporate login involved in either.
How to talk about it afterwards
Once you have finished either project, be specific on your CV about which of the five categories your evidence actually supports. "Built a supply chain forecasting model using SAP-scale transaction data" is a sentence a recruiter can act on. "SAP skills" is not. The difference costs you one extra clause and buys you a claim that survives a follow-up question in an interview, which is the actual test most CV lines fail.
What German employers look for covers this pattern more broadly: specific, checkable evidence beats a broad skill claim almost every time the two are compared side by side, and SAP is one of the clearest examples of why.
