The "Embedded" Promise and the Commercial Reality
SAP markets S/4HANA as a platform with analytics "embedded" throughout — and in a narrow technical sense, this is accurate. S/4HANA Cloud includes Fiori-based reporting, CDS (Core Data Services) views that expose transactional data, and a set of standard analytical apps covering Finance, Supply Chain, and Procurement. The commercial reality, however, is that "embedded" does not mean "unlimited" or "included for all use cases."
SAP's embedded analytics capabilities operate across three distinct tiers with very different licensing implications: included Fiori analytical apps (part of the S/4HANA subscription, no separate licence required); SAP Analytics Cloud for Planning functionality (sometimes bundled, sometimes requiring a separate SAC licence depending on your contract vintage and RISE tier); and Live Data connections from SAC to S/4HANA (which consume BTP infrastructure and can trigger additional costs depending on query volume and frequency). Understanding where your organisation sits across these tiers is the starting point for any analytical licensing review — and our SAP advisory team regularly finds enterprises paying for SAC licences that substantially overlap with included S/4HANA analytics capabilities. You can also explore the SAP Knowledge Hub for the full context on SAP's analytics product landscape.
SAP Analytics Cloud: Included vs Full Licence
This is the most commercially consequential distinction in SAP's embedded analytics landscape. RISE with SAP customers and S/4HANA Cloud Public Edition customers typically receive a restricted SAC bundle — covering planning capabilities for Finance and some standard reporting — but not the full SAC licence required for advanced analytics development, custom story creation, predictive analytics, or organisation-wide BI deployment.
SAP's account teams routinely blur this distinction in renewal conversations. The question to force clarity on is: "Does our current SAC entitlement cover all users who will access analytics, all use cases we intend to deploy, and all development capabilities our analytics team requires?" If the answer to any of those is no, you have a licensing gap that SAP will eventually surface in an audit or renewal. The gap is particularly acute for organisations that have moved SAC usage beyond Finance planning into operations, sales, and HR analytics — domains where the bundled SAC tier does not apply. For organisations also using SAP Datasphere, the interaction between SAC licensing and Datasphere live connections is a common source of unexpected cost escalation.
Need Expert Help With SAP Analytics Licensing?
Our SAP specialists can audit your current SAC entitlements and embedded analytics usage to identify gaps before SAP's audit team does.
Talk to a SAP SpecialistDigital Access and Third-Party Reporting Tools
One of the most significant — and most frequently misunderstood — embedded analytics licensing risks in S/4HANA is the interaction between third-party reporting tools and SAP's digital access licensing rules. When a third-party BI tool (Power BI, Tableau, Qlik) queries S/4HANA data directly — via OData APIs, BAPIs, or SAP's BW extractors — each document created or processed as a result of that query may constitute a digital access event under SAP's indirect access model.
SAP introduced the digital access model in 2018 to address indirect use, but implementation remained inconsistent until the audit enforcement wave of 2022–2024. The practical risk is this: a reporting platform pulling daily S/4HANA data feeds to produce management dashboards for 200 users may be generating hundreds of thousands of digital access events per year — each of which could be in scope for SAP's document-based access pricing. This is not theoretical — we have worked with organisations facing seven-figure digital access claims stemming from Power BI deployments they believed were fully licensed. To understand your specific exposure, book a confidential call with our SAP advisory team.
Fiori Reporting: What's Genuinely Included
The standard Fiori analytical apps included in S/4HANA — spanning key financial reporting apps (Journal Entry Analyser, Cash Flow Analyser, Profitability Analysis), supply chain visibility apps (Inventory Turnover, On-Time Delivery), and procurement monitoring apps (Purchase Order Monitoring, Invoice Processing Analytics) — are genuinely included in the S/4HANA licence at no additional cost. These apps are built on CDS views and the embedded analytics framework and do not require separate SAC licences or trigger digital access events.
The limitation is that these apps are read-only analytical surfaces — they cannot be extended, combined into custom dashboards within SAC, or used as data sources for planning models without additional licences. Organisations that attempt to build custom Fiori apps extending the standard analytical apps using SAP Build Tools are consuming BTP credits even for low-code development — a cost that SAP's pre-sales team rarely highlights proactively.
Assess Your SAP Analytics Licensing Risk
Use our SAP assessment tools to evaluate your SAC entitlements, digital access exposure, and third-party BI tool risk before your next audit or renewal.
Start Free Assessment →Negotiation: Protecting Analytical Access in Renewals
The embedded analytics negotiation has four critical objectives. First, get explicit contractual confirmation of which SAC capabilities are included in your S/4HANA or RISE subscription — in writing, with specific feature references rather than generic "bundled analytics" language. Second, negotiate a digital access safe harbour for defined third-party reporting use cases — securing contractual protection for named BI tools connecting to S/4HANA in read-only mode for specific documented reporting scenarios.
Third, if you need full SAC licences beyond the bundled tier, negotiate them as part of the S/4HANA renewal rather than as a separate purchase — SAP discounts SAC significantly when it is part of a larger deal structure, and a standalone SAC negotiation invariably yields worse pricing. Fourth, clarify the Live Data connection volume that is included versus billable — prevent SAP from treating high-frequency reporting queries as consumption-based BTP events mid-contract. Our guide on SAP Joule AI licensing is also relevant, as Joule-powered analytics insights are being positioned as the next embedded analytics upgrade — creating new bundling complexity. For a full view of SAP's analytics strategy, explore our SAP Knowledge Hub.