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.

🎉 What’s new

Atlan just became smarter, faster, and AI-native.

Data teams today need more than a catalog, they need a foundation built for AI. The new Atlan is that foundational context layer: a space to enrich your assets, build enterprise context, and give your LLMs what they need to be accurate and reliable at scale. 

✨ Let’s dig deeper

Here is what you can expect from the new Atlan experience:

✦ Ask Atlan anything
You no longer need to know where something lives to find it. Just ask Atlan. Search for assets, understand lineage, get instant answers about your data, or even ask how a specific feature in Atlan works. Atlan understands your intent and surfaces exactly what you need, without requiring filters, exact names, or technical queries.

🧠 Work smarter & faster
The new Atlan is built to make your AI work better over time. Enrichment agents help you keep your data assets accurate, well-described, and consistently up to date. That enriched data feeds directly into enterprise context.
The result: more reliable, more accurate AI outputs across your entire data stack.

🏠 Clean home for everything
Assets, governance, and your admin center are all reorganized into one focused, clean experience. What used to take extra clicks is now surfaced upfront — so you spend less time navigating and more time doing the work that matters.

👏 Give it a shot

Keep an eye out for an email with more details as we continue rolling this out to all users over the coming weeks.

• Once enabled, switch between old and new UI at any time from your profile dropdown
• A quick onboarding walkthrough will guide you through the changes.

Give the new Atlan a try and let us know what you think. We'd love your feedback as we keep refining the experience!

We are excited to share that Atlan has officially launched a revamped in-product dbt experience designed to give you cleaner metadata, clearer lineage, and dramatically improved troubleshooting workflows. This upgrade brings your dbt models closer to the native dbt experience, including… 

• environment-specific assets, with a new filtering option and expansive lineage
• table-level sources allowing a full and complete lineage view
• compiled/raw SQL for improved impact analysis
• detailed error messages
• A heads up view of the last 5 tests and their status
• Increased visibility of the status of the most recent test on asset search, profile & lineage
• An improved overall crawler run-time

…all to help you trust, understand, and fix issues faster!

Upgrading is simple. Workflow admins just head to Workflow Center > Manage, open your dbt connection, and click Upgrade to new dbt experience. New connections already run on this improved version, and all future fixes and capabilities will be supported only on the new experience.

Going forward, Atlan will create a separate dbt asset for each environment (e.g., customers – Production and customers – Staging), ensuring each one has accurate metadata and lineage. Some quick callouts: 

1. The first workflow run after upgrading will take longer because old assets are replaced with new ones, which means FQNs, GUIDs, access policies linked to old assets, and any manually applied metadata will need to be updated. 
2. Favorites may also need to be re-added. 
3. If your data products were manually selected, you’ll need to re-select the new assets; filter-based data products will update automatically.

We recommend upgrading soon to take advantage of all enhancements, and note that the previous version will no longer be supported starting February 15, 2026. 

If you need guidance or help planning your migration, see documentation here, reach out to your CSM or contact us at support@atlan.com.

🎉 What’s new

Make your ReadMes and rich text content pop!

With new Badges, Buttons, and Asset Cards, you can now add interactive and visual elements to your rich text content—making it easier to highlight key information, drive action, and improve navigability across your metadata experiences.

✨ Let’s dig deeper

Until now, ReadMes and custom metadata often relied on plain text—making it harder to spotlight important notes, add useful CTAs, or reference related assets. That changes today.

🏷️ Badges

Use badges to highlight key terms, statuses, or definitions.

• Add via markdown:
  ![badge](Your badge message)
• Or use /badge directly in the Rich Text editor

🔘 Buttons

Insert call-to-action buttons right inside your documentation—for links, requests, or redirections.

• Add via markdown:
  ![button](Your button label)
• Or use /button in the editor

🧩 Asset Cards

Paste any asset URL or GTC URL from the same Atlan tenant, and it will automatically render as a rich Asset Card, complete with name, icon, and a preview of key details.

No more messy links—just clean, contextual references to other assets.

🌍 Where does this work?

These enhancements are available everywhere Rich Text is supported, including:

• ✅ Custom Metadata (Rich Text properties)
• ✅ ReadMe editor for assets
• ✅ Product ReadMes
• ✅ ReadMe templates

Why it matters: This makes your documentation more engaging, more structured, and way more useful—especially for consumers trying to understand data context at a glance.

👏 Give it a shot

Jump into any ReadMe or Rich Text field and try out a badge, button, or paste an asset URL to see it transform.
With these upgrades, your metadata storytelling just got a major boost ✨

Let us know how you’re using them—we’d love to see what you build!

When viewing asset profiles, users often see technical identifiers for users and groups - like john.doe or tenant-cdxgl1. These make ownership challenging, especially for business users trying to understand who owns or maintains an asset.

• Human-readable names everywhere: Show First + Last Name for users and display names for groups.
• Consistent experience: Visible across Owners, Data Access tab, Activity tab, Custom metadata & Filters.

Give it a shot

This is currently configurable by Admins in Labs ("Show full user and group names"), default toggled off for now. Pending any concerns it will become the default and only option in the coming weeks.

We’re thrilled to announce that Atlan’s SAP ECC and SAP S/4HANA connectors are now live in Public Preview!

This marks a major milestone in our mission to bring deep metadata discovery, lineage, and governance to the SAP ecosystem — helping enterprises unlock visibility into their most complex, business-critical systems.

Why This Matters

End-to-End SAP Metadata Discovery and Governance
Atlan now natively connects to SAP ECC and SAP S/4HANA to extract comprehensive metadata directly from the application layer — including Components, TCODES, Function Modules, ABAP Programs, application components, tables, views, fields, check tables, CDS views and the relationships between them. This allows teams to understand the “what” behind their SAP Components like FI, LO, MM, SD and CO and how the data flows and is consumed within the modern data stack.

New Features from PrPr Release

Column-Level Check Table Relationships
The connector now automatically discovers column-level check table relationships, enabling precise data lineage and semantic context. 

Application Component Hierarchy
We’ve added Application Component Hierarchy relationships — allowing automatic discovery of related SAP tables, fields, and data objects by business domain or component (FI, MM, SD, LO, PP, PM, etc.).
These hierarchies can now be leveraged to build rich business semantic Data Products in Atlan that align directly with SAP’s organizational structure, driving cleaner discovery and business alignment.  If interested in more automation around this please contact your Atlan account representative.  

This helps users discover and connect transactional and master data across key SAP for use as data products such as:

• Business Partners
• Customer & Vendor Master
• Material Master
• Sales & Purchase Orders
• Work Centers
• G/L Accounts
• Profit Centers
• Maintenance Plans
  …and more.

Smarter Metadata Scoping

New flexibility lets users filter the SAP metadata extraction scope by:

• Application Component(s) – focus on only the modules relevant to your use case (e.g., FI, SD, MM).
• Atlan Asset Types – choose which metadata objects (tables, function modules, Programs, TCODEs, views) to include or exclude based on business requirements.

This enables faster, more targeted metadata ingestion and reduces noise across massive SAP landscapes.

 What’s Next

This Public Preview is just the start of Atlan’s journey in the SAP ecosystem.
Coming soon on our roadmap:

• SAP Business Data Cloud
• SAP BW on HANA
• SAP BW/4HANA
• SAP Datasphere
• SAP Analytics Cloud
• SAP Business Objects

Together, these will provide an end-to-end metadata lineage bridge across SAP’s legacy and modern data SAP Business Data Cloud ecosystems — from SAP to cloud analytics and beyond.

Interested in early access or upcoming connectors?
Reach out to your Atlan Account Representative to learn more or join the next preview cohort.

📘 Learn More

• SAP ECC
• SAP S/4HANA

🎉 What’s New

Atlan now supports concatenation of multiple tag values for Snowflake objects when reverse sync is enabled.

✨ What’s in Store

• Multiple tag values can now be concatenated and reverse-synced to Snowflake, which are propagated via hierarchy or lineage. 
• Tag values are automatically sorted alphabetically.
• Concatenated into a single string using a configurable delimiter.

👏 Give it a Shot

Enable tag value concatenation in Atlan now  — and let us know what you think!

📘 Learn More

• Manage Snowflake tags
• Manage tag values and concatenation

🎉 What’s new
Atlan now supports Databricks Struct datatypes, giving you complete visibility into nested fields for the first time.

✨ What’s in Store

• Explore Struct fields with an interactive tree view—expand & collapse for clear visualization.
• Seamlessly navigate Structs just like simple columns.
• Full metadata context now available for all Struct fields.

👏 Give it a shot

Start exploring Databricks Struct fields in Atlan today — and let us know what you think!

📘 Learn More

• What does Atlan crawl from Databricks?

🎉 What's new

Introducing a refined bulk glossary upload process for real time visibility, increased stability and more actionable insights into what changes your team is making.

👏 Give it a shot

Start curating your glossary via spreadsheets.