Atlan for SAP: Ground Your Agents in the System of Record

● Generally Available

This release turns SAP's notoriously opaque data into a governed, machine-readable context layer for AI. SAP is the system of record for most large enterprises — and the hardest source to ground agents in, thanks to cryptic tables, coded field names, and configuration-driven logic. SAP ECC and SAP S/4HANA are now GA with two new capabilities that give agents (and the people who supervise them) two things they've never had over SAP: provenance — where a number truly comes from — and a map of the human layer, where SAP data is actually created and consumed.

CDS View Column-Level Lineage

Provenance

What's new: Column-level lineage is now generally available for SAP CDS (Core Data Services) views. Trace every column in a CDS view back through its transformations to the exact source table columns that feed it.

What you can do:

• Follow a single field end to end, from the semantic CDS layer down to the underlying SAP table columns.
• Run precise impact analysis — see exactly what breaks downstream if a source field changes.
• Debug and validate at the column, not just the object, level.

Why it matters for agents: This is the provenance backbone of the context layer. When an AI agent surfaces a metric, it can cite the precise origin and transformation path of every value — making the output auditable and trustworthy, and letting governance and quality signals propagate accurately across the SAP estate.

Fiori Apps as a New Asset Type

The Human Layer · First to market for Atlan

What's new: SAP Fiori apps are now a native asset type in Atlan, with asset-level lineage from Fiori apps → CDS views → upstream SAP tables.

The problem this solves: Fiori is the modern SAP UI — where business users actually work, reading, entering, and changing data every day, with near-zero visibility into the data beneath the screen. This release connects the app the user sees to the data it actually touches.

What you can do:

• See, for any Fiori app, the chain of CDS views and source tables it draws from.
• Give business users and stewards a clear map from the interface to the underlying data.
• Trace where sensitive or business-critical data is exposed and modified at the point of use.

Why it matters for agents: Fiori is the human layer of the context graph — where data is created and consumed. Mapping it lets an AI agent understand what an app does in data terms, and lets governance follow data all the way to the screen.

On the roadmap: column-level lineage for Fiori apps · popularity & usage signals for Fiori apps.

What's Next

Next: SAP Business Data Cloud (BDC). Zero-copy data sharing across Snowflake, SAP Databricks, Google BigQuery, and Microsoft Fabric. Context that follows your data across platforms without ever moving or duplicating it — so lineage, meaning, and governance stay intact wherever SAP data is consumed. Connectors for SAP Datasphere and SAP Analytics cloud, complementing our ERP and BW connectors.

More context ingestion from the SAP ecosystem, coming soon:

• Field-level help text as glossaries — SAP's own field documentation, automatically converted into governed business glossary terms and linked to the exact columns they define. The semantic layer that gives agents authoritative meaning for every SAP field.
• Master data as data products — your unique SAP configuration, packaged into governed data products: material types, customer and vendor account groups, and Business Partner groupings, roles, and categories. Context that reflects how your enterprise actually classifies its master data.
• SAP long text as knowledge files — SAP's free-text long texts (notes, descriptions, and documentation) harvested and published as knowledge files, ready to ground agents — for retrieval in agent studios and RAG workflows.

Beyond that — context from across the SAP application landscape (actively working with customers on outcomes and use cases for the below):

• SAP Signavio — business process context (how work actually flows).
• LeanIX — enterprise architecture and application portfolio context.
• SAP IBP — integrated business planning and supply chain context.
• SAP Concur — travel, expense, and spend context.
• SAP SuccessFactors — people and HR context.

The Bigger Picture: SAP + the Leading Non-SAP Context Layer

Pair the deepest context layer for SAP with the leading context layer for everything outside it — cloud warehouses, lakehouses, BI, transformation, and AI tooling — and the whole enterprise becomes legible to AI in ways neither side can deliver alone. An agent can trace a metric from a BI dashboard, through the cloud warehouse, across a zero-copy SAP share, into the CDS view and its source table — with provenance at every hop.

The estate is opening. The connective tissue is here. The result is a single, trustworthy map of how the business really runs — and the foundation for enterprise AI you can actually rely on.