SAP terms explained: the working vocabulary

Every profession has a dialect; SAP's is denser than most. This is the working vocabulary — not marketing definitions, but what practitioners mean when they say these words in a project room.

The system landscape

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.
Client (Mandant): A self-contained data partition inside one system; the same word as "customer" but unrelated.
Instance: A running application-server unit of an SAP system, each with its own instance number (ASCS, primary application server, additional app 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?".

Configuration and code

Customizing / configuration: Adapting standard SAP through settings rather than code; the daily work of a functional consultant.
The IMG: The tree of every customizing activity; "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 BTP.
Z-development: Custom objects (historically named Z*); "too many Z's" is shorthand for a heavily modified system.

Data

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.

Process language

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; lived in full in a day in the life.

Projects and delivery

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.
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.

Platform and extensions

SAP HANA: SAP's in-memory database, and the platform the current ERP generation runs on; "on HANA" says which database, not which application.
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.
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.

Products and packages

RISE with SAP: SAP's bundle for moving an existing ERP customer to the cloud: the private cloud edition, the infrastructure and the services around the migration, sold as one subscription.
GROW with SAP: The counterpart bundle for the public cloud edition, aimed at new adopters, 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.
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.
BW: Business Warehouse: the classic SAP data warehouse; still running in many landscapes and the origin of most SAP analytics careers.

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 GRC 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.