Getting started · Lesson

SAP terminology

Last updated 7 August 2026

Quick answer

You do not need to memorise everything at once.

Key takeaways

Client: a self-contained tenant within a system, with its own data.
Instance: a set of work processes and memory on an application server.
Landscape: the connected DEV/QAS/PRD systems.
Watch out: Confusing master and transaction data, a foundational distinction.

System and landscape terms

Client: a self-contained tenant within a system, with its own data.
Instance: a set of work processes and memory on an application server.
Landscape: the connected DEV/QAS/PRD systems.
Transport: a package of changes moved between systems.

Data and configuration terms

Master data: long-lived reference data (customers, materials, vendors).
Transaction data: business events (orders, invoices, postings).
Customizing (IMG/SPRO): configuration of standard SAP to your business.
Organizational structure: company code, plant, storage location and the like.

TCode (transaction code): a shortcut that launches a function, e.g. VA01 to create a sales order.
ABAP: SAP’s programming language.
Table: where data is stored, e.g. MARA for materials.
BAPI/RFC/IDoc: the integration mechanisms.

How to use this vocabulary

You do not need to memorise everything at once. Refer back here (and to the full glossary) as terms come up, and they will quickly become second nature once you see them in context.

Common pitfalls

Confusing master and transaction data, a foundational distinction.
Mixing up system, client and instance, different layers.
Guessing at TCodes, learn the common ones deliberately.

Want to learn this properly?

Our live, instructor-led SAP Training covers this hands-on, with real projects and a certification path.

See the course Ask a question

Check your understanding

Which statement is true of SAP terminology?
- A. You do not need to memorise everything at once.
- B. The Transport Management System (TMS) is how SAP moves configuration and development changes between systems…
- C. These API examples show calling SAP over its interfaces, an OData request, a BAPI call, illustrating how…
Show answer
A. You do not need to memorise everything at once.
Covered in the “How to use this vocabulary” section of this lesson.
Which of these also applies to SAP terminology?
- A. Using downloads in production without testing.
- B. Refer back here (and to the full glossary) as terms come up, and they will quickly become second nature once…
- C. Upgrading without reading the notes.
Show answer
B. Refer back here (and to the full glossary) as terms come up, and they will quickly become second nature once…
Covered in the “How to use this vocabulary” section of this lesson.
Which part of the Learn SAP curriculum covers SAP terminology?
- A. Getting started
- B. SAP fundamentals
- C. SAP interview questions
Show answer
A. Getting started
This lesson sits in the Getting started section of the Learn SAP course.

Frequently asked questions

What does the term SAP terminology refer to in SAP?

SAP has a dense vocabulary that intimidates newcomers, much of it rooted in German-engineered software from the 1970s. Learning the core terms early makes every later topic far easier to follow. This page defines the words you will meet constantly.

What is involved in configuring SAP terminology?

Master data: long-lived reference data (customers, materials, vendors). Transaction data: business events (orders, invoices, postings). Customizing (IMG/SPRO): configuration of standard SAP to your business.

What is connected to SAP terminology in an SAP landscape?

TCode (transaction code): a shortcut that launches a function, e.g. VA01 to create a sales order. ABAP: SAP’s programming language. Table: where data is stored, e.g. MARA for materials.

What tends to go wrong with SAP terminology?

Confusing master and transaction data, a foundational distinction. Mixing up system, client and instance, different layers. Guessing at TCodes, learn the common ones deliberately.