SAP S/4HANA

What it is

SAP S/4HANA is SAP's current ERP suite, and the reason it belongs in an analytics corpus is not that it is an analytics product — it is that it is the source system that decides what analytics is possible. Where the data lives, which fields are populated, how a document flow is modelled: all of it is settled in S/4HANA before a warehouse or a semantic layer ever sees a row.

Why an analytics consultant meets it early. Two things changed with S/4HANA that a BW-trained consultant feels immediately. First, the simplified data model retired the aggregate and index tables that classic ECC extraction leaned on — a table a consultant reached for out of habit may simply not be there. Second, embedded analytics shipped in the suite: CDS views expose a semantic layer inside the ERP, so a class of operational reporting can be answered without leaving the system at all.

The question that actually gets asked on a project is therefore not "how do we extract S/4HANA into the warehouse", but what belongs where. Operational, real-time, single-source questions have an answer inside the suite. Cross-source, historised, cross-functional questions do not, and that is the case for Datasphere — where S/4HANA arrives as one source among several, and where the semantic work is about reconciling it with what the rest of the estate says.

Why it matters

• S/4HANA is the most-named product in this directory: 4,184 of the 9,116 published firm profiles mention it somewhere in their profile, against 244 for Databricks (measured 2026-08-29 on public/api/company-profiles.json).
• It is also the most-named product on the contract radar: 267 of the 3,307 live opportunity rows name it (measured 2026-08-29 on public/api/contracts.json).
• A consultant who can only speak about the warehouse side of a programme is speaking about the second half of it — the shape of the source has already settled what the warehouse can answer.

Key points

• It is a SOURCE system for analytics, not an analytics product — its data model decides what the warehouse can answer.
• The simplified data model retired aggregate and index tables classic ECC extraction relied on: a habitual table may simply not exist.
• Embedded analytics (analytical CDS views, Custom Analytical Queries, Fiori) answers operational, real-time, single-source questions inside the suite.
• Cross-source, historised, cross-functional questions are the Datasphere/BDC case — S/4HANA is then one source among several.
• Released CDS views are the sanctioned extraction surface; a missing field is an organisational path with the ERP team, not a development task.
• The deployment shape sets the surface: no direct table access in the public cloud edition; tables reachable but clean-core-costly in private cloud and on premise.
• Compatibility views preserve the old names, not the old performance profile — never size extraction from an ECC-era read plan.
• Extractability and delta are annotation decisions on the CDS view, taken by the ERP team long before the pipeline is built.

Terms used on this page

CDS view

Core Data Services view — the semantic, released extraction surface an S/4HANA system exposes to analytics consumers.

Released view

A CDS view SAP (or the customer's ERP team) commits to keep stable across upgrades. Only released views are safe to build a pipeline on.

Embedded analytics

Reporting served from inside the ERP on live transactional data, without extraction to a warehouse.

Simplified data model

The S/4HANA table design that removed the aggregate and index tables classic ECC reporting read from.

Universal Journal (ACDOCA)

The single finance line-item table that replaced the separate FI/CO totals and index tables of classic ECC.

Compatibility view

A CDS view delivered under a classic table name so existing code keeps running. It preserves the name and the semantics, not the read-performance profile.

Clean core

The discipline of building only on released, versioned surfaces so an upgrade stays an upgrade instead of becoming a re-implementation.

Sources

1. SAP S/4HANA — official product page
2. SAP Help Portal — SAP S/4HANA (on premise)
3. SAP Help Portal — SAP S/4HANA Cloud (ODP/CDS extraction reference)
4. SAP Help Portal — SAP Datasphere (CDS views for data extraction)
5. What is SAP S/4HANA Embedded Analytics and How Can I Develop My Skills? — SAP Community
6. Embedded Analytics in SAP S/4HANA Cloud: Leveraging Data for Success — SAP Community
7. SAP S/4HANA Cloud — Embedded Analytics: Custom Analytical Queries — SAP Community
8. Creating Custom CDS Views for Analytical Scenarios — Modelling Rules — SAP Community
9. “I now have SAP S/4HANA Embedded Analytics. Do I still need a data warehouse?” — SAP Community
10. S/4HANA Analytics: From Fiori app to a CDS view — SAP Community
11. Creating SAP S/4HANA Embedded Analytics in Public Cloud with Developer Extensibility — SAP Community
12. SAP S/4HANA Integration with SAP Datasphere: Replication Flow, Data Flow and Model Import — SAP Community
13. CDS view with Change Data Capture (CDC) for Replication Flow — Part 1 — SAP Community
14. SAP CDS View — CDC based Delta: Nuts & Bolts — SAP Community
15. The Question of Full Loading Large CDS Views from S/4HANA: Problems and Solutions — SAP Community
16. CDS View Performance Best Practices — SAP Community
17. SAP Datasphere Integration with SAP S/4HANA: SAP Cloud Connector Setup Guide — SAP Community
18. How to Connect S/4HANA Public Cloud with SAP Datasphere — SAP Community
19. SAP Business Data Cloud Series — Part 2: Extend SAP S/4HANA Managed Data Products — SAP Community
20. Sharing SAP S/4HANA Data with Databricks Using BDC Connect and Delta Sharing — SAP Community
21. Dynamic Labels in CDS Views: Making S/4HANA Embedded Analytics Truly Parameter-Driven — SAP Community