Node types
The graph is a small number of node classes organized into ten families. Nine families live under the atlas: prefix and cover the product-shaped model Atlas reasons over; the tenth (sap:) is the detailed SAP source-intelligence sub-graph Atlas’s planner walks when picking CDS bindings.
Every class has a rdfs:label. Subclasses inherit from their parent and can be queried by either specific class or parent class. The tables below list every class, its parent, and a one-line purpose.
Family 1 — SAP artifacts
Section titled “Family 1 — SAP artifacts”Technical objects in the SAP ecosystem.
| Class | Parent | Purpose |
|---|---|---|
atlas:SAPArtifact | — | The root class for everything technical SAP owns. |
atlas:Transaction | atlas:SAPArtifact | An SAP transaction code (MM01, VA01, …). |
atlas:Table | atlas:SAPArtifact | A physical database table (VBAK, MARA, T001). |
atlas:BAPI | atlas:SAPArtifact | A Business Application Programming Interface. |
atlas:FunctionModule | atlas:SAPArtifact | A plain ABAP function module. |
atlas:ABAPClass | atlas:SAPArtifact | An ABAP global class. |
atlas:Report | atlas:SAPArtifact | An ABAP report program. |
atlas:SAPNote | atlas:SAPArtifact | An SAP Note or KBA. |
atlas:Fiori | atlas:SAPArtifact | A Fiori app. |
atlas:CDS | atlas:SAPArtifact | A CDS view (the coarse atlas: view; see sap:CDSView for the modeling-grade detail). |
atlas:BAdI | atlas:SAPArtifact | A Business Add-In extension point. |
Family 2 — Documents
Section titled “Family 2 — Documents”The source material Atlas reads. The DITA subclasses mirror the SAP Help topic-type taxonomy, so the evidence writer can reason over what kind of topic a statement came from.
| Class | Parent | Purpose |
|---|---|---|
atlas:Document | — | Any crawled document from an SAP knowledge source. |
atlas:DocumentSection | — | A semantic section within a document. |
atlas:HelpDocument | atlas:Document | SAP Help portal content. |
atlas:MigrationGuide | atlas:Document | A release migration guide. |
atlas:ReleaseNote | atlas:Document | A release note. |
atlas:BlogPost | atlas:Document | Community blog post (tier-4 evidence). |
atlas:BAHEntry | atlas:Document | A Business Accelerator Hub entry. |
atlas:ConceptTopic | atlas:Document | DITA concept topic — explanatory, not procedural. |
atlas:TaskTopic | atlas:Document | DITA task topic — ordered procedural steps. |
atlas:ReferenceTopic | atlas:Document | DITA reference topic — structured facts and signatures. |
atlas:APITopic | atlas:Document | DITA API topic with api-state metadata. |
Family 3 — Guidance
Section titled “Family 3 — Guidance”Actionable knowledge derived from documents. What Atlas recommends, not what Atlas was told.
| Class | Parent | Purpose |
|---|---|---|
atlas:Guidance | — | Root for derived guidance. |
atlas:MigrationPath | atlas:Guidance | A from → to migration path between artifacts. |
atlas:BestPractice | atlas:Guidance | A recommended way of doing something. |
atlas:Deprecation | atlas:Guidance | A deprecation notice. |
atlas:Replacement | atlas:Guidance | A replacement recommendation. |
Family 4 — Version and scope
Section titled “Family 4 — Version and scope”The release context that scopes every SAP fact.
| Class | Parent | Purpose |
|---|---|---|
atlas:VersionScope | — | Product-and-release context for an artifact. |
atlas:SAPProduct | — | An SAP product (S/4HANA, ECC, BW). |
atlas:SAPRelease | — | A release of an SAP product (S/4HANA 2023 FPS02). |
atlas:SAPModule | — | A functional module (FI, MM, SD). |
atlas:SAPProgrammingModel | — | Cross-cutting paradigm (RAP, ABAP-CLOUD, KEY-USER-EXT, CLEAN-CORE, BTP-EXT, FIORI). Orthogonal to SAPModule. |
Family 5 — Plans
Section titled “Family 5 — Plans”The dependency-ordered plan Atlas emits for a task.
| Class | Parent | Purpose |
|---|---|---|
atlas:Plan | — | A migration or implementation plan. |
atlas:PlanStep | — | One node in the plan graph. |
atlas:PlanTemplate | — | A reusable blueprint Atlas instantiates plans from. |
Family 6 — Cases
Section titled “Family 6 — Cases”The engineering work Atlas is supporting.
| Class | Parent | Purpose |
|---|---|---|
atlas:EngineeringCase | — | A tracked migration or modernization case. |
atlas:Recommendation | — | A recommended action for a case. |
atlas:MigrationDecision | — | A recorded migration choice and its rationale. |
Family 7 — Bundles
Section titled “Family 7 — Bundles”The transportable output Atlas assembles for a case.
| Class | Parent | Purpose |
|---|---|---|
atlas:BundleArtifact | — | A generated delivery bundle. |
atlas:Pattern | — | A modernization pattern Atlas can recommend. |
atlas:WrapperRequirement | — | An adapter or wrapper Atlas identified during generation. |
atlas:ReleasedAPI | — | A released SAP API suitable for clean-core use. |
Family 8 — Estimates and outcomes
Section titled “Family 8 — Estimates and outcomes”The calibrated estimate model.
| Class | Parent | Purpose |
|---|---|---|
atlas:EstimateSnapshot | — | A persisted effort forecast for a case (P50/P80/P90). |
atlas:EstimateFactor | — | A single contributing factor that shifts the estimate. |
atlas:DeliveryOutcome | — | Observed actuals Atlas calibrates against. |
Family 9 — Governance signals
Section titled “Family 9 — Governance signals”The risks that block plans.
| Class | Parent | Purpose |
|---|---|---|
atlas:RiskSignal | — | A governance or clean-core risk identified for a case or portfolio. |
Family 10 — SAP source intelligence (sap: prefix)
Section titled “Family 10 — SAP source intelligence (sap: prefix)”The detailed sub-graph Atlas’s planner walks when picking a CDS binding. Richer than the coarse atlas:CDS class above, with modeling-grade properties (view type, data category, release contract, tenant observation).
| Class | Purpose |
|---|---|
sap:CDSView | A single CDS view, keyed by its name. |
sap:CDSField | A field on a view, with role (key / measure / currency / dimension). |
sap:CDSAssociation | A declared association between views. |
sap:ReleaseContract | The C0 / C1 / C2 contract attached to a view. |
sap:ODataService | An OData service that exposes one or more views. |
sap:EntitySet | An entity set inside an OData service, backed by a view. |
sap:TenantObservation | A tenant-specific confirmation that a view exists in a customer’s system. |
Prefix declarations
Section titled “Prefix declarations”Every SPARQL example on this site begins with these two lines:
PREFIX atlas: <https://atlas.naburis.cloud/ontology#>PREFIX sap: <https://atlas.naburis.cloud/ontology/sap#>The typed clients inject them automatically.