SAP products

• S/4HANA, the current-generation ERP suite on HANA.
• SAP ERP (ECC), the previous-generation suite still widely in use.
• SAP Business One / Business ByDesign, ERP for smaller and mid-market companies.

• SuccessFactors, cloud human capital management.
• Ariba, cloud procurement and supplier networks.
• Concur, travel and expense.
• SAP Customer Experience (CX), cloud CRM/commerce.
• IBP, integrated business planning for supply chain.

• SAP HANA, the in-memory database.
• SAP BTP (Business Technology Platform), the cloud platform for extension, integration, analytics and AI.
• SAP Analytics Cloud, Datasphere/BW, analytics and data warehousing.
• SAP Integration Suite, cloud integration (formerly CPI/PI-PO).

This is the distinction that trips up nearly everyone new to SAP, and it decides whether a job advert is describing your skills or somebody else's.

A product is something a company buys and runs: S/4HANA, SuccessFactors, Ariba, Concur. A module is a functional area inside one of those products: FI, MM and SD are modules of the ERP core, not products in their own right. So "we are implementing SuccessFactors" and "we are implementing FI" are sentences about different levels of the stack.

The confusion has a cost. People describe themselves as an SAP consultant when they mean an S/4HANA MM consultant, and then find the interview was about SuccessFactors, which shares almost no skills with it. See SAP modules for the module side of the map.

Five minutes, on any system you have access to, and it answers a question people get wrong in interviews all the time.

1. In SAP GUI, choose System, then Status.
2. In the SAP System data block, click the magnifier next to Component version. You now have the installed software components and their releases.
3. Read the component list. S4CORE means you are on S/4HANA. SAP_APPL without S4CORE means ECC. EA-HR or SAP_HRCM tells you personnel administration is installed.
4. Note the database. An ECC system can run on HANA and still be ECC, which is why "we are on HANA" does not answer "are you on S/4HANA".

The ERP core runs operations; line-of-business clouds specialise in HR, procurement and CX; and BTP is the glue that extends and connects everything without modifying the ERP core. This "keep the core clean, innovate on the platform" model is central to modern SAP strategy.

The joins are worth naming, because integration work is where a lot of the jobs are. Employee data flows from SuccessFactors into the ERP core for cost assignment and payroll posting. Ariba carries sourcing and pushes purchase orders back into materials management. Concur pushes expense postings into finance. BTP is where the extensions live that used to be written directly in the core, which is what the clean core principle asks for.

• Follow the installed base, not the announcement. A great many companies still run ECC, and 2027 and 2030 maintenance deadlines mean migration work will be paid for years.
• Cloud or on-premise changes the job. Public cloud editions limit what you can configure and rule out classic custom code, so the work shifts toward fitting the standard. Private cloud and on-premise keep the configuration depth.
• Platform skills travel. BTP, integration and analytics sit beside every product, so they stay useful when a customer changes direction.

The naming is inconsistent because it accumulated over fifty years, and knowing the pattern saves a lot of confusion.

R/3 was the client-server generation, and the 3 referred to three tiers rather than a version. ECC, ERP Central Component, was its successor and is what most people mean by "old SAP". S/4HANA is the current suite, where the 4 is the generation and HANA is the database it requires.

Cloud products mostly carry the name of the company SAP bought: SuccessFactors, Ariba, Concur, Qualtrics. That is why they feel different from each other, because they were built by different companies and are still being aligned.

Editions matter more than the name suggests. S/4HANA Cloud public edition, S/4HANA Cloud private edition and S/4HANA on-premise are the same product family with materially different amounts of configuration freedom, and a job advert that says only "S/4HANA" has not told you which. See SAP licensing for how that is sold, and where the product line is heading.

Product choice is a career choice, so it helps to know roughly what the market is buying.

Migration work is the large one. A great many companies still run ECC and have a maintenance deadline to plan around, so conversion and greenfield S/4HANA projects will be staffed for years. That work rewards people who understand the old system as well as the new, because the hard part is deciding what to carry over and what to leave behind.

Cloud implementation is a different job. Public cloud editions limit configuration and rule out classic modifications, so the skill is fitting a business to a standard process and knowing where the extension points are, rather than building whatever was asked for.

Integration sits between everything and is consistently under-supplied. A landscape with S/4HANA, SuccessFactors and Ariba in it has more integration than any one of those products has configuration.

Support and operations is where most people start and it is not a lesser path. A year of resolving real incidents teaches document flow and configuration cause and effect faster than any course, including this one.

Whichever you aim at, the first job is usually the one that will have you, and the module matters more than the product at that stage. See SAP job roles for how these are advertised.

A useful test of whether you have understood the map: describe a landscape in one sentence that names the product, the edition and the modules. "S/4HANA private cloud, finance and procurement, with SuccessFactors for core HR and payroll still on-premise" tells another consultant almost everything they need. "We use SAP" tells them nothing, and in an interview it is the answer that ends the conversation early.

Practise it on the system you have access to, using the component list from the exercise above. If you cannot fill in the edition, that is worth finding out before somebody asks.

• Confusing products with modules, SuccessFactors is a product; FI is a module of the ERP core.
• Assuming everything is on-premise, many products are cloud-only.
• Overlooking BTP, it is where modern SAP extension happens.

• Reading "SAP" on a CV as one skill. Naming the product and the module is the difference between a screening call and a rejection.
• Assuming the newest product replaced the old one everywhere. Hybrid landscapes are the norm, not the exception.

Two shifts matter for anyone learning now. RISE with SAP repackaged S/4HANA as a subscription that bundles infrastructure and services, which changes who runs the system rather than what it does. And the clean core principle asks for extensions to be built on BTP or through released APIs instead of modifying the core, so upgrade projects stop being rewrites. See SAP editions for how the cloud and on-premise variants differ.

Knowing the map is the start, and choosing one product and going deep enough in it to configure a real process is the part you do in the course.