SAP S/4HANA Embedded Analytics Licensing: What's Included and What Costs Extra

The Architecture Behind S/4HANA Embedded Analytics

SAP S/4HANA was architected from the ground up to eliminate the traditional separation between transactional systems and reporting systems. In legacy SAP landscapes — ECC combined with Business Warehouse — analytical reporting required data to be extracted, transformed, and loaded into a separate BW system, creating reporting latency, additional infrastructure cost, and a complex ETL (extract, transform, load) layer that had to be maintained continuously. S/4HANA's HANA in-memory database collapses this architecture by allowing analytical queries to run directly against live transactional data in real time.

The technical mechanism for this is SAP's Virtual Data Model (VDM), implemented through Core Data Services (CDS) views. CDS views are predefined analytical lenses on the underlying HANA data model that expose operational data in reporting-ready formats without requiring physical data replication. SAP ships S/4HANA with thousands of standard CDS views covering every major business domain: finance, controlling, procurement, order management, manufacturing, and HR. These views are the analytical foundation of the embedded analytics capability — and they are covered by the standard S/4HANA user licence.

What Is Included in the S/4HANA Licence at No Additional Cost

Users with a valid S/4HANA user licence — Professional, Limited, or Self-Service, as appropriate — can access the full range of embedded analytics capabilities within the scope of their licence tier without incurring additional charges. This is a point that SAP's sales teams frequently underemphasise in favour of proposing additional SAP Analytics Cloud licences, so it is worth stating clearly.

The embedded analytics capabilities included in the S/4HANA licence include: all SAP Fiori analytical apps delivered as part of the standard S/4HANA application content (SAP ships thousands of standard Fiori apps covering reporting, dashboards, and operational analytics); SAP Smart Business KPI dashboards, which provide real-time KPI monitoring with drill-down to transactional detail; the S/4HANA Query Browser and Query Designer, which allow business users to build and customise reports based on the VDM CDS views without technical development skills; SAP Analytics for Microsoft Office, which allows users to consume CDS view data in Excel using live connections; and the S/4HANA Embedded BW capability (BW/4HANA on S/4HANA), which provides a subset of BW analytical functionality operating directly within the S/4HANA system without requiring a separate BW licence.

Fiori Analytical Apps: The First Line of Embedded Analytics

SAP's Fiori application framework provides the user interface for both transactional and analytical S/4HANA functionality. Fiori is included in the S/4HANA licence at no additional charge — there is no separate Fiori licence, and the analytical Fiori apps are not subject to any additional usage-based charging beyond the user's primary S/4HANA user type licence. The analytical Fiori apps range from simple operational overviews (aged receivables, open purchase orders) to sophisticated multi-dimensional analytical views with exception highlighting, trend visualisation, and interactive filtering.

The scope of standard Fiori analytical content grows with each quarterly release (for Public Edition) and annual update cycle (for Private Edition). Organisations that deployed S/4HANA in 2020 and have not reviewed the current standard content library frequently discover that analytical use cases they were meeting with custom development or additional tooling are now covered by standard Fiori apps — eliminating the need for those additional capabilities and their associated costs.

Where Additional SAP Analytics Cloud Licensing Becomes Required

The boundary between included embedded analytics and separately licensed SAP Analytics Cloud capability is crossed when organisations need specific advanced features that exceed the scope of S/4HANA's standard embedded framework. SAP Analytics Cloud (SAC) is a separate, cloud-native business intelligence and planning platform that offers capabilities beyond embedded analytics — but these capabilities come with their own per-user or per-session licence cost.

SAC licensing is required for: creating standalone SAC stories (interactive dashboards and reports that exist independently in the SAC cloud environment rather than within the S/4HANA system); SAC Predictive Analytics functionality (machine learning-based forecasting and anomaly detection); SAC Planning capabilities (integrated financial and operational planning, budgeting, and forecasting within the SAC environment); and multi-source analytics (SAC stories that combine S/4HANA data with data from other systems, whether cloud or on-premise).

SAC licensing is available under multiple models: per-named user for Business Intelligence users, per-named user for Planning users (at a higher price point), and through consumption credits for session-based access. The per-user pricing for SAC varies by volume and contract structure, but typical enterprise list pricing for SAC BI users runs $20 to $35 per user per month, with Planning users priced higher. Negotiated enterprise rates are typically 20% to 35% below list.

SAC in S/4HANA Cloud Public Edition: The Embedded Integration

SAP has developed an integrated analytics capability specifically for S/4HANA Cloud Public Edition that embeds SAC visualisation within the S/4HANA Public Edition interface. This integration allows users to view SAC-powered charts and stories within S/4HANA Fiori pages without navigating to a separate SAC environment. The basic version of this embedded SAC integration is covered by the S/4HANA Cloud Public Edition licence, providing chart and dashboard visualisation beyond what standard CDS view analytics deliver.

However, the embedded SAC integration in Public Edition does not grant full SAC licences — users cannot navigate to the SAC environment to create standalone stories, use predictive features, or access planning functionality without separate SAC licences. The distinction matters because organisations that deploy Public Edition and discover the embedded SAC visualisation capability sometimes assume they have full SAC access, only to find that the capabilities they want (particularly planning and predictive) require additional investment.

Third-Party BI Tools and the DDLC Intersection

A significant number of S/4HANA customers supplement embedded analytics with third-party business intelligence platforms — Power BI, Tableau, Qlik, or legacy SAP BusinessObjects. The licensing implications of these integrations depend critically on whether the third-party tool reads from S/4HANA or writes to it.

Read-only connections from third-party BI tools to S/4HANA data — whether via OData services, JDBC/ODBC connections to HANA, or CDS view-based APIs — do not create DDLC liability under SAP's Digital Access licensing model. SAP's Digital Access policy explicitly states that read-only access does not generate digital document charges. Organisations can therefore use Power BI, Tableau, or any other BI tool for reporting against S/4HANA data without incurring additional Digital Access charges, provided the integration is genuinely read-only.

The DDLC risk arises when third-party tools write data back to S/4HANA — a pattern that is more common than organisations recognise. Examples include: planning tools that write budget or forecast data back to SAP CO-PA; workforce management platforms that post time confirmations to SAP Project Systems; and procurement analytics tools that update purchase order status in the S/4HANA MM module. Each write-back interaction that creates or modifies one of SAP's nine chargeable document types is counted under the DDLC metric and charged accordingly. Organisations with planning tools that write back to SAP should conduct a DDLC assessment before any S/4HANA migration to quantify this exposure before it is included in their audit-risk profile.

Negotiating SAC in RISE with SAP Deals

SAP Analytics Cloud licensing is consistently one of the most negotiable elements in a RISE with SAP deal. SAP's account teams have significant discretion to bundle SAC user licences into RISE contracts at reduced or zero incremental cost — particularly when the RISE deal is large and the SAC requirement is presented as a competitive pressure point or as a condition of the overall deal structure.

The negotiation approach we recommend for organisations that need SAC capabilities alongside RISE is to treat SAC as a deal element rather than a post-signature add-on. SAP's maximum flexibility is available during the initial RISE negotiation, before the contract is signed. Once RISE is contracted and SAC is requested as an add-on, the negotiation leverage diminishes substantially and SAC is typically priced at or near list.

Specific tactics that have delivered results in our engagements include: requesting a free SAC pilot for a defined user population as a condition of the RISE agreement, with a contractual mechanism to convert pilot users to contracted licences at a negotiated rate; bundling a defined SAC user count (typically sufficient for your planning and executive analytics use cases) into the RISE contract at a fixed price per FUE or as a flat add-on; and using competitive alternatives — Qlik, Tableau, Power BI — as genuine fallback options that reduce SAP's leverage if SAC pricing is not competitive. SAP's account teams respond to credible alternatives differently than to theoretical ones; demonstrating that you have evaluated Power BI for your analytics requirements changes the negotiation dynamic materially.

SAP BTP Credits and Analytics Workloads

RISE with SAP contracts include a defined allocation of SAP BTP CPEA (Cloud Platform Enterprise Agreement) credits. Some SAC capabilities and data integration workloads consume BTP resources, meaning that organisations planning significant SAC deployment alongside RISE should model their BTP credit consumption before finalising the credit allocation in their RISE contract. Insufficient BTP credits are a common post-go-live cost surprise in RISE deployments — credits run out faster than anticipated when multiple teams deploy BTP-based analytics, integration, and extension scenarios concurrently.

Annual support costs within the RISE subscription are embedded and not separately negotiable, which distinguishes RISE analytics governance from on-premise S/4HANA where SAP support is approximately 22% of net licence value and is a distinct cost line. For organisations managing analytics cost holistically, the total cost of S/4HANA analytics must account for embedded analytics (included), SAC licences (additional), BTP credit consumption (included up to contracted allocation), and any third-party BI tool costs that sit outside the SAP ecosystem entirely.