Glossary
Short, plain-English definitions of the terms used across these docs. Makion-specific terms and SAP terms are mixed together and listed alphabetically; where a term has its own page, it is linked.
A#
ABAP β SAP's programming language, used to build and extend business logic in an SAP system. Makion is an AI coding agent for ABAP.
ADT (ABAP Development Tools) β SAP's official Eclipse-based tooling and the interfaces developers use to work with ABAP objects. Makion drives SAP through these official interfaces rather than screen-scraping.
ATC (ABAP Test Cockpit) β SAP's static-analysis framework that checks code against quality and security rules. Makion can run ATC and fix its findings via the ATC and ATC remediation roles.
Autonomous mode β a mode where the agent works unattended and entirely read-only, proposing changes into a ship queue that a human approves and applies. The strongest safety gate in Makion. See Autonomous mode.
B#
Base rules β the always-applied standards an admin defines per project on the Methodology tab, so the agent follows your team's conventions on every task. See also Methodology.
BDEF / behavior definition β the object that defines the behavior (create, update, delete, actions, validations) of a RAP business object. Part of building a RAP service.
C#
CDS (Core Data Services) β SAP's modern data-modeling layer, used to build reusable views and data models on top of database tables. Makion has a dedicated CDS role.
Channel β the working unit in Makion: your developer identity Γ the selected project. Your SAP connection and chat history are scoped to this pair, which is why a task started on the phone continues on the desktop. The word "Channel" is rarely used in the interface; customer-facing pages usually just call this your developer identity Γ the selected project.
Cleaner β Makion's own deterministic, behaviour-preserving ABAP formatter. It normalizes whitespace, casing, line breaks, and safe token modernizations without ever changing what the code does. See How the cleaner works.
Connector β the component that opens the tunnel from your machine to your SAP system and carries the agent's SAP calls. It runs on the developer's own machine and is attached from the desktop Systems tab.
D#
DDIC (Data Dictionary) β SAP's central repository of data definitions: tables, structures, data elements, and domains. Makion can create these DDIC objects through ADT.
DEV / QAS / PROD β see Tier.
Dump β see ST22 / dump.
E#
Engine β the AI backend a project runs on. Makion is multi-engine β for example Claude, Gemini, Codex, Kimi, and Grok β chosen per project. See AI engines & login.
F#
Fiori β SAP's user-experience design system and its family of web apps, typically built on OData services. Makion's Fiori role makes an OData service Fiori-Elements-ready with a @UI annotation layer.
I#
IDoc β SAP's standard document format for exchanging data between systems (for example EDI and ALE integration). Makion's support roles can triage failed IDocs and hand off the manual reprocess step.
K#
Knowledge base β the reference files and examples an admin materializes into the agent's context on every run for a project, so the agent works from your standards. Part of Methodology.
M#
Methodology β the per-project configuration of base rules, per-role methodology, and knowledge base that steers how the agent works. See Methodology.
O#
OData β the REST-style protocol SAP uses to expose services consumed by Fiori apps and other clients. A RAP service is published as OData.
On-prem β self-hosted on infrastructure the customer controls. Makion is on-prem: the SAP connection, credentials, and AI login stay on the customer's own server and machines. See the Security model.
P#
Project β the pairing of a codebase / SAP system with the roles, methodology, and specifications that apply to it. You pick a project before you work. See Sign in & projects.
Q#
qRFC / tRFC β SAP's queued and transactional Remote Function Call mechanisms for reliable, ordered communication between systems, often underlying IDoc and integration flows.
R#
RAP (ABAP RESTful Application Programming model) β SAP's modern framework for building transactional business services (data model β behavior β service) on S/4HANA. Makion has a dedicated RAP role.
Read-only role vs write role β a read-only role is handed only the read set of SAP tools and physically cannot change SAP; a write role also gets the write tools, so it can lock, set source, create, and activate as part of a task you direct. See How roles work.
Role β the choice you make in the Chat composer that sets both the agent's methodology and its SAP permissions. See How roles work.
S#
Ship queue β the list of changes an Autonomous run proposes. Nothing in it touches SAP until a human approves and then applies it.
Specification β a client requirement turned into Makion's normalized spec format, which you can then run as a task. See Specifications.
SRVD / SRVB (service definition / service binding) β the objects that expose a RAP business object as a consumable service: the service definition lists what is exposed, the service binding publishes it (for example as OData).
ST22 / dump β the SAP transaction and record for a runtime error ("short dump"). Makion's support roles can read dumps to diagnose incidents.
Subscription vs API key β two ways to sign an engine in. A subscription signs in with an existing plan for a flat fee (no per-token cost); an API key is pay-as-you-go per use. See AI engines & login.
Superadmin β the first person to sign in to a Makion instance, who administers the whole instance and grants roles and project access to everyone else. See Users & access.
T#
Tier β the environment tag on a SAP connection: DEV, QAS, or PROD. QAS and PROD are read-only, so an agent can never change them; only DEV is writable. See Systems and the Security model.
Transport β SAP's mechanism for packaging changes and moving them between systems (DEV β QAS β PROD). Makion's roles work within your transport discipline.
tRFC β see qRFC / tRFC.
Related pages#
- What is Makion β the product in one page.
- How roles work Β· Systems Β· Autonomous mode
- Security model Β· FAQ