Executive Summary
What CIOs need to know about S/4HANA embedded features
SAP S/4HANA introduces powerful embedded features that did not exist in legacy ECC: real-time analytics, Fiori UX, proactive alerts, and machine learning. These are included as part of the core S/4HANA licence for named users at no extra cost. However, missteps can lead to unintended costs or audit exposure when features are used beyond their intended scope, exposing analytics to non-S/4 users, connecting third-party BI tools, or triggering Digital Access documents through API integrations.
CIOs must understand exactly what is covered versus what requires additional licensing, and build governance that maximises the value of included features while avoiding compliance pitfalls.
Table of Contents
1. S/4HANA Embedded Capabilities Overview
Four powerful features included in your S/4HANA licence
Embedded Analytics
Real-time operational analytics via CDS views, Smart Business cockpits, Query Browser/Designer. “BW-lite” approach eliminating separate data warehouse for operational reporting.
Fiori User Experience
Consumer-grade, role-based interface replacing SAP GUI. Thousands of standard apps covering transactions and analytics. Web and mobile-friendly.
Situation Handling
Proactive exception-driven framework detecting exceptional conditions automatically. Alerts users via Fiori notifications with context and recommended actions.
Predictive ML
Embedded predictive analytics and machine learning via HANA ML libraries. Predictive Accounting, predictive stock, cash application matching, sales forecasting.
Need Help Understanding Your S/4HANA Licensing Entitlements?
Our SAP advisors provide independent clarity on what is included, what requires additional licensing, and how to maximise the value of your S/4HANA investment. See our SAP licence optimisation service.
SAP Licence Optimisation →2. Licensing Clarity: What Is Included vs. Extra
Feature-by-feature breakdown of licensing requirements
| Feature | Included in S/4HANA? | When Extra Licence Required |
|---|---|---|
| Embedded Analytics | ✓ Yes: CDS views, Fiori analytical apps, Smart Business KPIs, Query Browser | SAP Analytics Cloud (SAC), SAP BW/4HANA, or third-party BI tools (Power BI, Tableau) |
| SAP Fiori UX | ✓ Yes: Fiori Launchpad, standard apps, SAP Gateway/OData | Fiori apps on SAP BTP (requires BTP account). Exposing Fiori to unlicensed external users |
| Situation Handling | ✓ Yes: core S/4HANA functionality, no separate licence | Alerting for non-SAP systems requires other tools (outside S/4HANA scope) |
| Predictive ML | ✓ Yes: PAi, ISLM, HANA ML libraries, prebuilt ML scenarios | SAP AI Business Services, SAP Data Intelligence, SAP AI Core on BTP, third-party ML |
3. Scenarios That Trigger Licence Escalations
Five common situations that create additional licensing requirements
Exposing Analytics to Non-S/4 Users
Sharing S/4HANA analytics with users who are not licensed on S/4 constitutes indirect usage. Examples: dashboards for executives who do not log into S/4, publishing analytics on a portal for customers or suppliers, or connecting Power BI or Tableau to S/4 data for a broad audience. SAP considers any individual accessing S/4-derived data in real-time as needing a licence. Analytics kept within S/4 for S/4 users is fine. Broadcasting outside S/4’s user base requires a licensing check. See our SAP Digital Access advisory service.
Standalone Dashboards and Advanced Reporting
Extracting S/4 data into SAP Analytics Cloud, SAP BusinessObjects, or non-SAP BI platforms requires additional licences for those tools. SAC licensing is entirely separate: each user needs an SAC subscription even when viewing S/4 live data. The act of having an automated third-party system query S/4 data could be seen as indirect access.
Digital Access: Indirect Document Creation
SAP’s Digital Access model licenses outcomes (documents) of indirect usage rather than requiring named users. 9 document types (sales orders, invoices, purchase orders, and others) created in S/4 by external applications count against your Digital Access allocation. Common triggers: custom mobile apps creating orders, e-commerce front-ends pushing orders via API, RPA bots creating transactions, predictive scenarios auto-generating purchase orders. See our SAP DAAP guide and Top 10 Pitfalls in SAP Digital Access white paper.
Enterprise Data Warehouse Scenarios
S/4HANA’s embedded analytics is not meant to replace an enterprise data warehouse. If you need extensive data modelling, multi-system combination, or large historical data retention, you need SAP BW/4HANA, which requires a separate licence. The embedded BW component in S/4 is only for limited integrated scenarios.
Advanced ML, IoT and AI Scenarios
S/4HANA’s built-in ML capabilities (PAi, ISLM, HANA ML) are free. But advanced scenarios (training complex models on large datasets, NLP, computer vision, IoT device integration) require additional platforms: SAP Data Intelligence, SAP IoT, SAP AI Core on BTP, each separately licensed. If an external AI service writes back into S/4, consider whether that triggers a digital document under Digital Access licensing.
Concerned About Indirect Access or Digital Access Compliance?
Our specialists have defended enterprises against millions in SAP audit claims related to indirect access and embedded feature usage.
SAP Audit Defence Service →4. Strategic Guidance for CIOs
Maximise included functionality, avoid violations, plan add-ons deliberately
Maximise Adoption of Included Functionality
Drive teams to fully utilise embedded capabilities that come with S/4HANA. Often companies underutilise these features due to unawareness or legacy habits. During implementation, identify all relevant features and include them in project scope. Train end-users on Fiori analytical apps, self-service query tools, and Situation Handling. Build a culture where the first question for any reporting or UX need is “Can S/4HANA do this internally?” before purchasing new software. Every included feature you use is one less separate licence needed. SAP adds embedded features with each release. Stay on current releases and review release notes for new analytics or intelligent scenarios.
Avoid Inadvertent Licence Violations
Establish clear internal policies for any integration or access involving S/4HANA data. Require departments to involve SAP architecture teams before connecting third-party analytics tools. Educate developers on indirect access rules. A well-meaning team might build a customer mobile app calling S/4 APIs without realising licensing implications. Incorporate licence impact as a checkpoint in solution design reviews. Use SAP’s Digital Access Evaluation Service periodically to estimate document counts. Institute governance and awareness to prevent accidental overuse that surfaces during audits.
Plan for Add-Ons Deliberately
When S/4HANA’s included functionality is not enough, make conscious decisions with cost-benefit analysis. If you need global analytics for all employees, budget for SAC rather than stretching embedded analytics. If advanced planning is needed, licence SAP Analytics Cloud Planning or IBP. Align your IT roadmap with licensing requirements. When extending S/4 with new functionality, engage SAP and independent licensing advisors to determine if it falls under current entitlements. Negotiate favourable terms when planning expansions rather than being caught by surprise.
5. Contract & Audit Tips
Written clarity, entitlement understanding, DAAP, and audit readiness
Get Clarity in Writing
When negotiating your S/4HANA contract, explicitly document understanding about included features. Ask SAP to provide a licence clarification document affirming that Fiori, embedded analytics, Situation Handling, and embedded ML are included at no additional charge. If you foresee specific scenarios (using embedded BW for a particular purpose, or an ML scenario), describe them and get confirmation they are covered. Document boundaries explicitly and append these to your contract or keep in formal meeting records. For more on negotiating S/4HANA licensing conversions and discounts, see our guide.
Understand Your Entitlements Fully
Ensure procurement and SAP Basis teams understand user types (Enterprise, Professional, Functional) and which level grants which access. Higher-tier users can run all apps and analytics; limited users may be restricted. Allocate the right licences to users leveraging advanced features. If you have “Engine” metrics for add-ons, monitor usage against the contract. Keep an internal licence usage register aligned with SAP’s definitions.
Leverage SAP’s Digital Access Adoption Program
If migrating from ECC to S/4HANA, SAP offers the Digital Access Adoption Program (DAAP): a one-time opt-in to document-based licensing with incentives (often large discounts). If indirect access is significant for your enterprise, consider negotiating a conversion to the document model. Avoid paying twice: do not be charged for named users and digital documents without knowing it. Clarify with SAP how they will treat your indirect scenarios. For the full framework, see our detailed guide on SAP DAAP: evaluate, negotiate, and avoid cost traps.
Audit Readiness
Treat SAP licence compliance as ongoing, not an annual scramble. Log how embedded features are used: custom Fiori apps and their data exposure, third-party systems integrated with S/4HANA. Conduct “mock audits” using SLAW, USMM reports, and SAP’s Digital Access estimation tool. Engage external licensing experts for health checks before official audits. During audits, having documentation that certain usage is permitted can save you. See our SAP Audit Readiness: 10-Step Strategy white paper.
Preparing for an SAP Contract Renewal?
Our negotiators specialise in S/4HANA licensing terms, Digital Access, and embedded feature entitlements. See our SAP contract negotiation service.
SAP Contract Negotiation →6. CIO Recommendations & Next Steps
Eight-point action plan for S/4HANA embedded feature licensing
Educate and Align Stakeholders
Brief IT architects, project managers, and business power users on which features are free and which require caution. Create a culture of compliance and smart usage from day one of your S/4HANA deployment.
Inventory Your Usage of New Features
Post-migration, catalogue which embedded features you are using and plan to enable. Map against licence entitlements. Identify gaps early, for example a team wanting SAC with S/4 data. Spot the licence need immediately.
Engage SAP Early for Clarification
Do not wait for audits. Ask scenario-based questions proactively (“We want to feed S/4 data to a supplier portal. What licensing?”). Get written guidance.
Govern Integration and BI Architecture
Establish an architecture review board that includes SAP licensing knowledge. Mandate compliance checkpoints for any system interfacing with S/4HANA or new reporting on S/4 data.
Optimise Licence Allocation
Analyse whether your user mix is optimal given embedded feature usage. If many users need occasional analytics only, lower-tier licences may suffice. Work with SAP to adjust as usage evolves. For guidance on user role mapping, see our article on mapping legacy SAP ERP licences to S/4HANA user roles.
Document and Train for Audit Defence
Keep contracts, SAP notes, and clarifications centrally. Train software asset management team on S/4-specific licensing. Conduct internal audits regularly. See our SAP audit defence service.
Leverage What You Paid For
Champion embedded capabilities throughout the enterprise. Communicate new tools gained with S/4HANA. Every included feature used is one less separate licence needed. Align digital strategy to maximise S/4’s built-in suite before looking outside.
Engage Independent Licensing Expertise
SAP’s embedded feature licensing is nuanced and evolving. Independent advisors provide clarity, benchmark entitlements, and ensure your contract reflects accurate usage rights. Our case studies demonstrate consistent savings.
4 Embedded Features = Included
Embedded Analytics, Fiori UX, Situation Handling, and Predictive ML are all included in the standard S/4HANA licence for named users. No separate module charges.
Indirect Access = Audit Risk
Exposing S/4 data to non-S/4 users, third-party BI, or API-based integrations creating documents triggers additional licensing. Digital Access with 9 document types is SAP’s model for indirect use.
SAC & BW/4HANA = Always Extra
SAP Analytics Cloud and SAP BW/4HANA are never included in S/4HANA licensing. Each requires separate subscriptions even when connected to S/4 data.
Get It in Writing
Document all licensing understandings in your contract. Get SAP to confirm in writing which embedded features are covered. This prevents disputes during audits.
Frequently Asked Questions
Common questions about S/4HANA embedded feature licensing
No. All embedded analytics (CDS views, Fiori analytical apps, Smart Business KPIs, Query Browser) are included in the standard S/4HANA licence for named users. No separate analytics module charge applies. However, SAP Analytics Cloud (SAC), SAP BW/4HANA, and third-party BI tools like Power BI or Tableau require their own separate licences, even when connected to S/4 data.
Fiori is fully included. The Fiori Launchpad, standard Fiori apps, SAP Gateway/OData technology, and custom Fiori app development within S/4HANA are all covered. No separate Fiori licence exists. The only time additional licensing applies is building Fiori apps on SAP BTP (requires BTP account) or exposing Fiori to users who are not S/4HANA-licensed.
Any time an external application (not a human using SAP GUI or Fiori) creates one of the 9 document types in S/4HANA, it counts as Digital Access. Common triggers: custom mobile apps, e-commerce front-ends, RPA bots, and IoT systems creating transactions via API. Even ML predictions auto-generating purchase orders through integration may trigger document counts.
Generally no. SAP considers third-party BI tool access to live S/4HANA data as indirect access unless every viewer is also a named S/4HANA user. If you are feeding data to a broad audience who are not S/4 users, you need to address this through named-user licensing for viewers, Digital Access, or by extracting data to a separate environment.
Yes. The embedded ML capabilities (PAi, ISLM, HANA ML libraries, prebuilt ML scenarios like Predictive Accounting and cash application matching) are included. No additional ML engine fee applies. However, advanced AI (training complex models, NLP, computer vision, or using platforms like SAP Data Intelligence, SAP AI Core on BTP) requires separate licensing.
Treat compliance as ongoing: maintain user assignment records, log custom Fiori apps and their data exposure, catalogue third-party integrations. Run mock audits using SLAW and USMM reports. Use SAP’s Digital Access estimation tool. Get written confirmation from SAP that embedded features are covered in your contract. Engage independent licensing experts for pre-audit health checks.