SAP terms explained: the working vocabulary

Written by an SAP Finance & Treasury practitioner working with SAP since 2008 · how the guides are written · Updated 9 October 2026 · facts checked against the SAP Help Portal and SAP's maintenance pages, October 2026

SAP terms are the working vocabulary of SAP projects: the product names, system words and process language used in a project room without definition. Each entry gives the meaning a consultant would give a colleague, not a dictionary's.

As of October 2026, the vocabulary is current for SAP S/4HANA, which SAP now releases on premise every two years. Where a term carries a date, it is taken from SAP's own pages, starting with the S/4HANA documentation on the Help Portal.

How does SAP ECC differ from S/4HANA?

SAP ECC: ERP Central Component: the previous ERP generation, and the successor to R/3. It runs on any of several databases, keeps finance and controlling in separate sets of tables, and is worked in mostly through classic transaction codes. Many landscapes still run it, so ECC on a CV describes maintenance, rollout and conversion work rather than something obsolete; on a project, "the old system" usually means this (and for anyone weighing the vendors, how SAP compares with Oracle ERP as a career). As of October 2026, its mainstream maintenance ends on 31 December 2027, optional extended maintenance runs to 31 December 2030, and RISE with SAP customers who qualify and have moved to SAP ERP, private edition can pay for a transition option that keeps it running until the end of 2033.
SAP S/4HANA: The current ERP generation and the successor to ECC: it runs only on the HANA database, holds finance and controlling postings in one Universal Journal, uses Fiori as its standard interface, and is sold in on-premise, private cloud and public cloud editions. HANA is the database; S/4HANA is the business suite that runs on it, and the two are constantly used as if they were one thing. Which edition a client runs decides how much of the work is configuration and how much is extension — and the generation change asks something different of every area. SAP commits to maintaining it until at least the end of 2040.

What does landscape mean in SAP?

Landscape: The chain of connected systems a change travels through, classically development → quality/test → production.
Transport: The packaged unit that carries configuration or code between those systems; "it's in transport" means a change is on its way. Managing them is Basis craft, the work of the Basis consultant.
Client (Mandant): A self-contained data partition inside one system; the same word as "customer" but unrelated.
Instance: A unit of an SAP system that is started and stopped together under its own instance number: the ABAP central services instance (ASCS), which runs the message server and the enqueue server, the primary application server, and any additional application servers. Not the same thing as the system, and not the same thing as the edition.
Deployment model / edition: Where and how the software runs: on-premise, private cloud or public cloud editions of the same product line. This is what people usually mean when they ask "which S/4 are you on?". SAP's newer marketing names, SAP Cloud ERP and SAP Cloud ERP Private, describe the same public and private editions.

What is customizing in SAP?

Customizing / configuration: Adapting standard SAP through settings rather than code; the daily work of a functional consultant, and the clearest marker of the functional versus technical divide.
The IMG: The Implementation Guide: the tree of every customizing activity, opened with transaction SPRO; "check the IMG" is where configuration answers live.
ABAP: SAP's own programming language; the developer track's home.
User exit / BAdI / enhancement: Sanctioned hooks where custom logic extends standard behaviour.
Clean core: A core kept unmodified and extended only through released extension points — in-stack (key-user tools, ABAP Cloud) or side by side on SAP BTP, the platform beside the core. SAP grades how clean an extension is in four clean core levels, from A (released APIs only) to D (modifications).
Z-development: Custom objects (historically named Z*); "too many Z's" is shorthand for a heavily modified system.
RICEFW / WRICEF: Reports, Interfaces, Conversions, Enhancements, Forms and Workflows: the six kinds of custom development a project may need on top of configuration. WRICEF is the same list with the workflow first, and RICEF the older form without it. The RICEFW list is a project's inventory of those objects, each with an owner, a complexity rating and a status; on a clean-core project every entry is a candidate to remove, to replace with a standard app, or to build as an extension outside the core.

What is master data in SAP?

Master data: The long-lived records everything references: materials, business partners, cost centres. Governing it is its own field — MDG.
Transactional data: The documents daily business creates: orders, deliveries, invoices, postings.
Document flow: The linked chain from order to delivery to invoice; reading it is core diagnostic skill in SD.
IDoc: The classic electronic document format for exchanging data with other systems; still everywhere, and bread and butter for integration consultants.

What do order-to-cash and procure-to-pay mean?

Order-to-cash / procure-to-pay / record-to-report: The end-to-end processes spanning SD, MM and FI.
Period-end close: The monthly finance crunch; if production support goes quiet mid-month, it won't at close.
Fit-gap: The blueprint-era gap analysis: the business's requirements written down first, then compared with a design of what standard SAP does; the gaps become configuration, development or process change.
Fit-to-standard: The SAP Activate workshop that replaced it: the standard process is shown running in the system, the business confirms it fits, and only the deltas are logged. The default in the cloud editions.
Cutover / go-live / hypercare: The launch sequence, walked hour by hour in the cutover guide and lived in full in what a day looks like in each phase.

What do greenfield and brownfield mean in SAP?

Greenfield / brownfield: A greenfield project builds a new system from a clean design; a brownfield project converts an existing system in place, history and custom code included. The two shapes staff and feel differently.
Selective data transition: The third route beside greenfield and brownfield: a new system is built to a fresh design, then chosen parts of the old one — particular company codes, a slice of history, configuration worth keeping — are carried into it with specialist tooling. Large landscapes rarely fit either pure route, and this one staffs like both at once.
Rollout: Deploying a corporate template to another country, plant or company code; the design is largely settled and the work is localisation.
Stream: The team for one area inside a project — the finance stream, the logistics stream — each with a lead; the project's organisational unit.
Key user: The person on the business side who knows the process and the system best, sits in the workshops, tests and trains colleagues; the origin of one of the classic routes into consulting.
SAP Activate: SAP's own implementation method: phases from discover and prepare through explore, realize and deploy to run, with fit-to-standard workshops at its centre. Project plans and job ads borrow its phase names.
Steering committee: The client's senior decision body for a project; where the scope, budget and go-live decisions nobody lower can take are made.
AMS: Application Management Services: running and maintaining live SAP systems under a service contract — incidents, small changes, monitoring — as opposed to project work.
Utilisation and bench: Consultancy words for the share of a consultant's time billed to clients, and for the time between assignments when it is not.

What is SAP HANA, and how is it different from S/4HANA?

SAP HANA is a database; S/4HANA is the ERP application that runs on it. The shared name causes most of the confusion, so keep four points apart:

HANA holds data. It keeps tables in memory and in columns, which is why reporting can run on live transactions.
S/4HANA runs processes. Orders, deliveries, invoices and postings live in the application, which needs HANA underneath.
ECC can run on HANA too. A client on "ECC on HANA" has changed its database but not its ERP generation, so it still faces the S/4HANA move.
Different people own each. Basis and database administrators run HANA; functional consultants and developers work in S/4HANA.

SAP HANA: SAP's in-memory database, and the platform the current ERP generation runs on; "on HANA" says which database, not which application.

Platform and extensions

BTP: SAP Business Technology Platform: the cloud platform beside the ERP for extensions, integration, data and application services; where clean-core extensions live.
Fiori: SAP's design system and the web-based user interface for its applications; a Fiori app is a tile-launched screen rather than a classic transaction. Building and designing those apps is a specialism of its own — Fiori developer and UX careers.
CDS view: Core Data Services: the way data models and views are defined inside the ABAP stack; the basis of modern reporting and of many Fiori apps.
RAP: The ABAP RESTful application programming model: the current way to build services and Fiori apps in ABAP, as opposed to classic report and dialog programming.
Side-by-side extension: Custom functionality built on BTP and connected to the ERP through APIs rather than coded inside it; the clean-core alternative to a Z-development.
BAPI: A released, stable function interface into standard SAP business objects; the classic way other systems create or read documents programmatically.
OData: The web protocol SAP exposes services through; what a Fiori app talks to, and what most modern integrations call.
Integration Suite: SAP's cloud integration platform on BTP for building and running interfaces between SAP and other systems; the cloud successor to SAP's on-premise middleware, and integration consultants' daily tool.
Tenant: One customer's isolated instance of a cloud service; in the cloud editions the tenant is what "our system" means, and it is provisioned rather than installed.
Joule: SAP's generative AI assistant, built into its cloud applications and development tools and set up through BTP; the name on most of SAP's AI announcements.

Products and packages

RISE with SAP: SAP's subscription bundle for cloud ERP — most often the private cloud edition — with the infrastructure and the services around the move sold as one contract, to existing SAP customers leaving ECC and to new customers alike.
GROW with SAP: The counterpart bundle for the public cloud edition, aimed at net-new, mostly midsize customers, with the standard-first approach built in.
Cloud ALM: SAP's cloud tool for application lifecycle management — implementation tasks, testing, monitoring; the cloud counterpart of Solution Manager.
SuccessFactors: SAP's cloud HR suite: core HR, talent and employee experience for companies that moved off classic HCM, updated in two major releases a year, 1H and 2H.
Ariba: SAP's cloud procurement network and applications — sourcing, supplier collaboration, spend; the cloud-side neighbour of MM.
EWM: Extended Warehouse Management: the warehouse application for complex warehouses; the depth end of the logistics area.
SAP Analytics Cloud: SAP's cloud tool for reporting, dashboards and planning; where analytics on top of the ERP is built today, beside or in place of BW.
Datasphere: SAP's cloud data warehouse and data-integration service; where data from SAP and non-SAP sources is combined for analytics; since 2025 also sold inside SAP Business Data Cloud. How Datasphere and BW sit next to each other is a question every analytics landscape now answers differently.
BW: Business Warehouse: the classic SAP data warehouse; still running in many landscapes and the origin of most SAP analytics careers.
Business Data Cloud: SAP's managed data offering, launched in February 2025: Datasphere, SAP Analytics Cloud and BW under one subscription, with SAP-built data products and Databricks as a built-in data service.

Finance, planning and control

Universal Journal: The single line-item table that holds financial and controlling postings together in the current ERP; the reason FI and CO no longer reconcile against each other.
MRP: Material requirements planning: the run that turns demand into planned orders and purchase requisitions; the heart of PP and the point where planning meets procurement.
Segregation of duties: The control principle that no single user may hold conflicting permissions — creating a vendor and paying it, say; what authorization design and SAP GRC, the access-risk tooling, exist to enforce.
Authorization role: The bundle of permissions assigned to a user; designing and maintaining these bundles is the security consultant's craft.

Why does SAP vocabulary matter?

Interviews and project rooms assume it silently — interviewers hear instantly whether these words are lived-in or memorised. If most were new, start with the module map; if most were familiar, you're further along than you think.