Welcome to edition 06 of /n Procurement.
In my September edition, I highlighted the list of source-to-pay AI assistants & agents SAP has committed to its customers: https://nprocurement.com/p/sap-spend-management-ai-agents
This month, I want to introduce my readers to the foundational layer SAP is banking on to deliver those agentic promises: the enterprise data foundation underneath it all.
SAP calls its vision the autonomous enterprise. But AI agents cannot autonomously run business processes on application data they cannot understand, connect, or trust. And that is exactly why SAP is placing such a big bet on SAP Business Data Cloud.
The ambition is much bigger than building another data platform. SAP wants to turn raw enterprise data into governed, reusable data products, connect SAP and non-SAP data without moving everything into SAP, and establish the trusted master data foundation its AI agents will need to make real business decisions.
Two acquisitions sit at the heart of that strategy: Dremio, which helps SAP reach and process data beyond its own application landscape, and Reltio, which helps turn fragmented records into trusted golden records.
Which raises the question every large SAP customer will eventually need to answer:
“How does SAP’s data strategy fit with the enterprise data strategy we already have?”
Three important takeaways:
SAP’s autonomous enterprise is also a data play. Joule Assistants and agents may be the visible layer, but their success depends on the governed data products and business context underneath them.
Dremio and Reltio fill two very different gaps. Dremio gives SAP an open path to non-SAP data without moving everything into SAP. Reltio addresses the trust problem by matching fragmented customer, supplier, and product records into unified golden records.
The biggest challenge may not be technical. Large enterprises already have their own data platforms, architecture principles, MDM capabilities, and central data teams. Aligning SAP Business Data Cloud with that existing enterprise data strategy is where the real-world trade-off begins.
SAP has made a major investment in the data foundation behind its autonomous enterprise vision. Whether customers make the same bet will depend on how well that strategy can coexist with the data landscape they already have.
Let’s get into it.
📢 What you'll find in this edition:
🔗 Worth Bookmarking
🔁 SAP’s Next Big Bets on Enterprise Data: Inside SAP Business Data Cloud, Dremio, and Reltio
🔵 Best LinkedIn Post of the Month
💬 Worth Repeating…
🌯 Wrap Up
Note: Some of the content listed above is only available in the email version of this newsletter. Don’t miss out! Sign up for free to get the next edition.
The Monthly Update
SAP’s Next Big Bets on Enterprise Data: Inside SAP Business Data Cloud, Dremio, and Reltio
If you have attended any SAP event, in person or online, over the past two years, you will know that SAP has doubled down on a future where enterprise business transactions are increasingly led by AI agents. SAP calls this vision the “autonomous enterprise” and has repositioned its entire portfolio around it.
In my September newsletter, I wrote in detail about the first set of autonomous spend management assistants and agents that SAP has promised its customers for source-to-pay processes: https://nprocurement.com/p/sap-spend-management-ai-agents
Delivering on the promise of this agentic future depends fundamentally on the structure and semantic context of the underlying data.
SAP Business Data Cloud is SAP’s approach to preparing enterprise data for that future. It is a fully managed SaaS data platform that unifies and governs SAP and third-party data through a business data fabric while grounding AI in the business policies, logic, and context that give your data meaning.
In simple terms, SAP Business Data Cloud (BDC) is where SAP wants business data to be organized, governed, connected, and made usable for analytics, reporting, planning, and AI agents.


The platform promises to deliver its unique value through data products rather than raw data.
Raw ERP tables are too complex, cryptic, and disconnected for analytics or AI agents to use reliably. Tables from systems such as SAP S/4HANA use abbreviated, German-based names (such as BSEG, VBAK, or MARA), have thousands of columns, and require complex join rules. Extracting these raw tables strips away the relationships that explain what each record actually represents.
By packaging data into pre-built, governed data products, SAP BDC preserves business context, eliminates costly data engineering, and provides trustworthy inputs for AI.
What exactly is a data product?
A data product is business data packaged for reuse. It is a curated, reusable, and self-contained dataset that includes everything needed to make it trustworthy and easy to consume—just like a commercial software product. Rather than raw database tables, it provides analysts or AI systems with clean, standardized business information (such as “Customer 360” or “Monthly Sales”) ready for immediate use.

In the real world, end-to-end business processes span multiple technology platforms beyond the SAP landscape and, by definition, rely on more than just SAP data. Today, human users navigate multiple systems and platforms to execute these processes. Tomorrow, AI assistants and agents will need to do the same.
Consider an AI agent processing an employee expense report. It would need access to data in HR and finance tables, often spread across SAP, Workday, and other systems. Similarly, to resolve a contractor timesheet mismatch, an AI agent would often need information about contracted hours, the service order, the timesheet, and the invoice from SAP and non-SAP procurement, HR, and finance systems.
The key question many are struggling with is this: How do you bring this data together in a consistent, AI-ready way?
To address this, SAP BDC needed to do two things:
Adhere to open industry standards for data structures and storage formats to enable seamless bidirectional data sharing with leading cloud data platforms such as Databricks and Snowflake, as well as leading hyperscalers. This allows SAP BDC to receive non-SAP data and enables third-party platforms to access SAP data when needed.
Create data products from the non-SAP data it receives, not just from the SAP application data it can access.
To achieve those objectives, SAP announced its acquisition of Dremio, an open data lakehouse company, in May 2026.
Dremio:
Dremio is a high-performance, federated SQL query engine that integrates with SAP Business Data Cloud (BDC) as its lakehouse compute and acceleration engine. Through the acquisition and integration of Dremio into SAP Business Data Cloud, SAP BDC adopted open table and data catalog formats such as Apache Iceberg and Apache Polaris.
In simple terms, Dremio helps SAP access and process data outside the traditional SAP world. Many companies already have important data stored in cloud data platforms, data lakes, and non-SAP systems. They do not want to move everything into SAP just to use it with SAP analytics or AI. Dremio helps address this challenge. Dremio enables SAP customers to access non-SAP data virtually, without replicating it. In technical terms, this capability is known as “zero copy.”

Dremio plays a key role in creating non-SAP data products. Alongside SAP HANA Cloud (the primary engine for creating SAP data products in SAP BDC), Dremio enables the creation of derived data products in SAP BDC. These data products meet future enterprise needs for AI, applications, and analytics, giving SAP Joule AI assistants and agents the end-to-end context needed for complete process execution.

SAP Business Data Cloud is only as powerful as the data that flows through it, with master data as the foundation. The data products, especially those related to master data, must serve as “golden records.” This requires unifying, cleansing, and enriching data from source systems, resolving duplicates, and building trusted profiles. Reltio fulfills this role within the SAP Business Data Cloud portfolio.

Reltio:
The same customer, supplier, or product can appear differently across enterprise systems. Each system may use different identifiers, attributes, and relationships. To make trusted decisions, an AI agent must recognize that these records represent the same business entity. Reltio addresses this problem.
Reltio is a cloud-native master data management (MDM) solution that addresses the trust problem by ensuring data accuracy and consistency across systems. SAP announced its acquisition of this company in May 2026, along with that of Dremio.
SAP Reltio’s AI-based entity resolution capability matches and reconciles records across SAP and third-party systems. Reltio resolves these fragments into a single trusted golden record in real time, then publishes it back into the lakehouse as a governed data product with the help of Dremio.
SAP is positioning Reltio alongside its own Master Data Governance (MDG) solution. SAP MDG governs master data quality at the source. It helps organizations enforce governance and control master data processes within operational SAP ERP environments. Reltio unifies data across SAP and non-SAP systems. It creates trusted, 360-degree views of customers, suppliers, products, and other core business entities for analytics and operations.
SAP’s future product positioning in this space is moving toward a single master data management layer within SAP BDC. Customers would consume MDM capabilities using SAP BDC capacity units. They would not need to worry about which underlying component—SAP MDG or Reltio—is doing the work.

Here’s what the complementary architecture would potentially look like:
Producers (bottom): SAP Cloud ERP, SAP Ariba, SAP SuccessFactors, SAP Commerce Cloud, and non-SAP applications feed data into BDC.
Master Data Management in BDC (middle): SAP MDG and Reltio, side by side. SAP MDG provides central governance at the point of entry in SAP Cloud ERP. Reltio provides cloud-native data unification across sources. Both produce high-quality master data that contributes to trusted, unified data products.
Consumers (top): Joule agents, SAP CAP applications, SAP Analytics via SAP Datasphere, and SAP and non-SAP business applications consume data in real time—including AI workloads grounded in trusted data.
Ultimately, this is an architectural decision, not an either/or choice between SAP MDG and Reltio. What matters is your governance model, your mix of source systems, and what you need to achieve:
Use SAP MDG when the priority is governance and process control at the source within SAP applications.
Use Reltio when the priority is bringing records together, building 360-degree views, and improving data quality across systems—including non-SAP sources.
Use both when you need control over how master data is created and a unified view across the enterprise. Increasingly, enterprises need both the challenges to be addressed.
Licensing and Consumption:
SAP Business Data Cloud licensing is based on SAP BDC capacity unit consumption. Further details from SAP on licensing and consumption for Dremio and Reltio are still pending. These capabilities are being made available gradually within SAP BDC during 2027.
In my own assessment, Dremio usage is expected to be embedded in SAP BDC’s capacity unit consumption model. Reltio is expected to be available under SAP BDC licensing and as a standalone SaaS subscription with its own usage model.
Final Takeaway for Readers:
If you are active in the SAP ecosystem, you have likely come across SAP’s autonomous enterprise pitch recently. The demos of this agentic enterprise future at SAP events are impressive. But all these promises rest on the data play SAP has built underneath: SAP Business Data Cloud and the capabilities within it.
Buying into the autonomous enterprise pitch also means, implicitly, embedding yourself in SAP’s data play. The degree to which SAP AI assistants and agents can deliver in a customer environment will depend on how thoroughly the customer has established the underlying SAP BDC foundation for them. And that is where I think the real-world trade-off starts.
Large organizations already have central, organization-wide data teams defining the broader data strategy, architecture, and platforms for the company, often independently and without explicit ERP alignment. So how feasible will it be to align SAP’s direction with that broader enterprise data strategy?
Customers will need synergy between the SAP ERP data journey of the future and their organization’s own data strategy. Striking that balance in the real world, particularly in large enterprises, is a different challenge altogether.
Disclosure: This article represents the understanding and views of the author at the time of writing. /n Procurement is an independent publication and is not affiliated with, endorsed by, or sponsored by SAP. Readers should independently validate all information provided before making any major business decisions. Use at your own risk.
#️⃣ Number of the Month
0
None of SAP’s four 2026 acquisitions is a procurement product. In the same stretch, Coupa bought Tonkean as the fourth piece of its autonomous spend strategy, which tells you where SAP thinks the procurement fight gets won: in the data layer, not the app.
Worth Repeating…
Data is a precious thing and will last longer than the systems themselves.
👀 From the Archives…
Wrap Up
Get more from your SAP investment.
AI-powered intake and orchestration can help close the gap between what your ERP can do and what your process actually needs. This ebook, developed with Tonkean, looks at how to reduce manual work, streamline P2P flows, and create better coordination across your procurement tech stack.
Download it here.Process mapping should not start from scratch every time.
Bring more structure, consistency, and clarity to the way you document procurement workflows.
— The /n Procurement Team

