SAP glossary
Practical definitions of the SAP terms used across ERP Preflight, written for people who plan upgrades, migrations and operations. Each term links to the problems and tools that involve it.
A
- ABAP CloudABAP Cloud development model
- The restricted ABAP language version and development model for cloud-ready extensions: only released SAP objects, no direct access to SAP tables.
- Account determinationAutomatic account determination (OBYC, VKOA)
- The configuration that finds the G/L account for automatic postings — in materials management via OBYC, for revenue in sales via VKOA.
- Adobe FormsAdobe Forms (XDP form templates)
- The PDF form technology of SAP output management: an XDP layout template bound to a form data XML; the cloud replacement for SAPscript and Smart Forms.
B
- BAdIBusiness Add-In
- An enhancement spot defined by SAP where custom ABAP logic plugs into a standard process without modifying SAP code.
- BRFplusBusiness Rule Framework plus
- SAP’s rules engine for decision tables and expressions. Output determination and many custom business decisions are modelled in it.
C
- CBCSAP Central Business Configuration
- The configuration environment of SAP S/4HANA Cloud: scope items are activated first, then settings are maintained through their SSCUIs.
- CDS viewCore Data Services view
- A semantic data model on SAP HANA. Released CDS views such as I_PRODUCT are the upgrade-stable way to read SAP S/4HANA data.
- Change pointerChange pointer (ALE)
- A record SAP writes when a relevant master data field changes, so that ALE can later distribute the change as an IDoc.
- Clean Core
- Keeping the SAP S/4HANA core free of modifications so that extensions rely only on released, stable interfaces and upgrades stay predictable.
- Clean Core tiersClean Core extensibility tiers (Tier 1–3)
- SAP’s three-tier model for extensions: Tier 1 uses only released APIs (ABAP Cloud), Tier 2 wraps classic functionality, Tier 3 is classic custom code.
- Cloudification RepositorySAP Cloudification Repository
- SAP’s public, machine-readable list of the release state and successors of SAP objects for cloud development, per edition and release.
D
- Deprecated objectDeprecated SAP object
- An SAP object that still works but is marked for replacement: SAP names a successor and can withdraw the object in a later release.
F
- Fiori 403 errorHTTP 403 Forbidden in SAP Fiori
- The request reached SAP and the user is signed in, but access was refused: by an authorization check, an inactive ICF node, CSRF, Gateway or UCON.
G
- gCTSgit-enabled Change and Transport System
- SAP’s integration of the ABAP Change and Transport System with Git repositories, so that ABAP changes can be versioned and distributed through Git.
I
- IDocIntermediate Document
- SAP’s standard container for asynchronous EDI and ALE messages, for example ORDERS or MATMAS, exchanged between systems and partners.
K
- Key-user extensibilityKey-user extensibility (custom fields, custom logic, custom CDS views)
- Extending SAP S/4HANA in Fiori apps without development tools: custom fields, custom logic and custom CDS views, transported in software collections.
M
- Message logSAP message log (application log, Migration Cockpit messages)
- The list of messages an SAP process writes while it runs — for example the application log (SLG1) or the messages of a Migration Cockpit run.
- MFS telegramTelegram of the SAP EWM Material Flow System
- A message exchanged between the Material Flow System of SAP EWM and the programmable logic controllers (PLCs) of conveyors and other warehouse automation.
O
- OData service
- The REST-based protocol of SAP Fiori apps and many SAP APIs: entity sets, keys, properties and navigation properties described in a metadata document (EDMX).
- OPDOutput Parameter Determination
- The SAP S/4HANA output framework that decides from BRFplus decision tables whether, how and to whom documents such as purchase orders are sent.
P
- PFCG rolePFCG role (authorization role)
- A role maintained in transaction PFCG that bundles launchpad content, such as business catalogs, with the authorizations users need.
R
- RAPABAP RESTful Application Programming Model
- The cloud-ready programming model for transactional apps and OData services, built on CDS views and behavior definitions.
- Released APIReleased API (release contract)
- An SAP object — CDS view, class, interface, function module or BAdI — that SAP has released for customer use, so it stays stable across upgrades.
S
- Software collectionSoftware collection (key-user extensibility)
- The transport unit of key-user extensibility in SAP S/4HANA Cloud: extension items are exported together and imported into the next system.
- SPRO / IMGImplementation Guide (IMG), transaction SPRO
- The on-premise configuration tree of SAP ECC and SAP S/4HANA: each IMG activity, reached via transaction SPRO, maintains a group of customizing settings.
- SSCUISelf-Service Configuration UI
- A configuration UI of SAP S/4HANA Cloud for the settings SAP opens to customers for self-service — the cloud counterpart of many IMG activities.
- SuccessorSuccessor object
- The released SAP object that replaces a deprecated or not released one — for example a released CDS view that replaces reads of a classic table.
- System refreshSystem refresh (system copy)
- Copying production data into a test or quality system. The copy has to be isolated before it is released, or it acts like production.
T
- Transport of copiesTransport of copies (ToC)
- A transport request that carries copies of objects to a target system while the original change requests stay open.
- Transport requestTransport request (Change and Transport System)
- The unit in which the SAP Change and Transport System (CTS) moves development and customizing changes between systems.
W
- Work itemWork item (SAP Business Workflow)
- The runtime unit of SAP Business Workflow: each step of a workflow instance creates a work item that an agent or the system executes.
ERP Preflight is independent and not affiliated with SAP SE. SAP, ABAP, Fiori and S/4HANA are trademarks of SAP SE.