Skip to content

Glossary

Every term linked from Atlas docs has an entry here. Starlight auto-generates an anchor from each heading; hover the term to copy the deep link.

A CDS view with the A_ prefix — SAP’s most stable public-API shape for a business object. Versioned, deprecation-tracked, C2 contract. Atlas prefers A_ over I_ when the choice exists.

@AccessControl.authorizationCheck forces an authorization check on the view. Its presence is a prerequisite for Atlas’s authorization gate.

SAP’s public API catalog. Atlas ingests structured entries as tier-2 evidence.

Business Application Programming Interface. A standardized SAP function module that acts as a published contract for a business operation. Many are deprecated in cloud releases; the Simplification Item Catalog tracks which.

A CDS view with @VDM.viewType: #BASIC — the foundation layer of the VDM, one-to-one with a physical table. See VDM layer architecture.

SAP Business Technology Platform. The extension surface outside the ERP core; where clean-core extensions live.

SAP’s three upgrade-stability contract tiers for CDS views. C2 is public and stable; C1 is system-internal; C0 is key-user or private. See SAP API stability tiers.

Core Data Services. The ABAP language feature used to define VDM views — a DDL-like projection syntax with annotation-based metadata.

The stage where Atlas decides the shape of a task — analytical or transactional, core or BTP, new build or conversion. A decision, not a condition: you can override it.

SAP’s principle that the ERP core is not modified; extensions live on BTP. See Clean core.

A CDS view with @VDM.viewType: #COMPOSITE — combines multiple basic views into richer business objects without reading physical tables.

A CDS view with @VDM.viewType: #CONSUMPTION — use-case-specific, carries UI, analytic, or OData annotations. Sits at the top of the VDM hierarchy.

A CDS view with @Analytics.dataCategory: #CUBE — the fact table at the center of an analytical star. See VDM analytical star.

Data Control Language. The annotation vocabulary that declares row-level authorization filters on CDS views.

A CDS view with @Analytics.dataCategory: #DIMENSION — a business object a query can filter by or slice on.

SAP’s earlier-generation ERP. Atlas reads ECC structures only to understand what a conversion is being asked to preserve; it does not emit code for ECC.

Atlas’s unit of provenance: a record tying a claim — a fact, a plan decision, a gate result — to its source, its tier, and its timestamp. Every artifact Atlas emits carries evidence.

One of four confidence bands: tier-1 (0.98), tier-2 (0.70), tier-3 (0.55), tier-4 (0.40). See Evidence and confidence.

A precise, testable condition a plan must satisfy before it advances. Non-bypassable; can be resolved or overridden with a stated reason. See Gates are non-bypassable.

A CDS view with the I_ prefix — an interface view, either basic or composite. Carries the core business semantics SAP publishes.

DJED’s knowledge-graph platform. Atlas is a consumer; the graph stores every fact Atlas knows about SAP.

SAP’s location identifier for help portal content. Stable across releases.

A CDS view with the P_ prefix — SAP-private. Can change without notice; C0 stability. Atlas refuses to bind without an override. See SAP API stability tiers.

The dependency-ordered graph of artifacts Atlas will build to satisfy a task. Four lifecycle states: Draft, Reviewed, Transport-ready, Transported.

The one-way state machine a plan moves through. See Plan lifecycle.

HANA’s ability to execute a CDS view as a single vectorized column-store scan rather than streaming rows to ABAP. See VDM runtime trace.

A CDS view with the R_ prefix — restricted reuse, intended for use only inside its owning application domain.

RESTful ABAP Programming Model. The transactional counterpart to the analytical VDM. Behavior definitions bound to CDS projection views.

A CDS view SAP has explicitly marked as public and stable — C2 contract. Atlas’s preferred binding target.

Atlas’s end-to-end pipeline has six stages: Task, Classify, Plan, Generate, Validate, Transport. The Studio UI rail shows five stations because Task is the trigger (the user typing the description), not a Studio-rendered station. Both descriptions are correct: “six stages end-to-end, of which five are visible Studio stations after task capture.”

Fix the cause the gate is flagging — usually by swapping an entity or adjusting a binding — so the gate re-runs clean.

SAP’s canonical list of things that change between releases. Atlas treats it as tier-1 evidence and refreshes its mirror nightly.

The query language Atlas uses against Keystone. See Why a knowledge graph.

SAP’s mechanism for moving changes between systems. Atlas’s final stage produces a TR and hands it off.

Virtual Data Model. SAP’s semantic layer on top of physical tables. A strict hierarchy of CDS views with declared annotations and stability contracts. Atlas plans against the VDM, not the tables. See VDM layer architecture.