Getting Started

Overview & Simplification

SAP S/4HANA (SAP Business Suite 4 SAP HANA) is SAP's next-generation Enterprise Resource Planning (ERP) suite, built entirely on the advanced in-memory platform, SAP HANA.

The Core Philosophy: Simplification

Unlike its predecessor, SAP ECC, S/4HANA drastically simplifies the underlying data model. By leveraging the speed of the HANA database, SAP eliminated redundant tables, indices, and aggregate tables that were previously necessary for performance on traditional databases.

Smaller Data Footprint: Removing aggregate tables significantly reduces database size and maintenance costs.
Real-Time Analytics: OLTP (Transaction Processing) and OLAP (Analytical Processing) are merged into a single system. You can report on live transactional data instantly without waiting for overnight ETL batches.
New User Experience: The traditional SAP GUI is largely replaced by the modern, role-based SAP Fiori web interface.

The Simplification Item Catalog

For customers migrating from ECC to S/4HANA, SAP provides the Simplification Item Catalog. This is a comprehensive list of what has changed, been replaced, or been deprecated. For example, traditional vendor and customer master data transactions (XK01, XD01) are replaced by a single Business Partner (BP) transaction.

Getting Started

Deployment Options

SAP offers S/4HANA in several deployment models to accommodate different IT strategies, customization needs, and cloud readiness.

☁️

Public Cloud Edition

A pure SaaS model. Highly standardized, fast time-to-value, managed entirely by SAP. Customizations are strictly limited to in-app extensions or side-by-side extensibility via SAP BTP. Upgrades are automatic and mandatory.

🏢

Private Cloud Edition (RISE)

A dedicated cloud environment offering the flexibility of an on-premise system with the benefits of cloud infrastructure. Allows for classic ABAP enhancements and full system control, while SAP manages the technical backend.

🖥️

On-Premise

Traditional deployment hosted in the customer's own data center or chosen IaaS provider. Maximum control over infrastructure, data residency, and upgrade cycles. Full customization allowed.

Data Architecture

The Universal Journal (ACDOCA)

The most profound architectural change in S/4HANA Finance is the introduction of the Universal Journal, represented by a single database table: ACDOCA.

Eliminating Data Silos

In SAP ECC, financial data was stored across dozens of separate tables depending on the sub-module: General Ledger (BSEG/BKPF), Controlling (COEP), Asset Accounting (ANEK/ANEP), and Material Ledger (MLIT). This required constant reconciliation programs at month-end to ensure FI and CO matched.

In S/4HANA, all of these modules write their transactional line items into one single table: ACDOCA.

Benefits of the Universal Journal

Single Source of Truth: Financial Accounting (FI) and Controlling (CO) are instantly and always reconciled by design.
Multi-Dimensional Reporting: You can query profitability, asset values, and general ledger balances from one table simultaneously.
High Speed: Because there is only one table, database inserts and reads are exponentially faster, enabling real-time financial close capabilities.

Logistics Equivalent: A similar simplification occurred in Logistics with the introduction of table MATDOC, which consolidates inventory management tables (MKPF, MSEG) into a single material document table.

Data Architecture

Core Data Services (CDS) Views

CDS Views are the foundation of SAP's new programming model and analytics strategy, replacing traditional ABAP dictionary views.

What are CDS Views?

CDS is a data modeling infrastructure. Instead of just joining tables, CDS views add rich business semantics (like currency conversions, authorizations, and analytical aggregations) directly at the database level.

Because CDS logic is executed in the HANA database layer (Code-to-Data paradigm), they are incredibly fast and form the basis of the Virtual Data Model (VDM) in S/4HANA.

The Virtual Data Model Architecture

SAP organizes CDS views into a layered architecture to build complex analytics from simple tables:

Layer	View Type	Purpose
Basic Views	`I_` (Interface)	Directly read from raw tables (e.g., ACDOCA). Contains no complex calculations. Reusable foundations.
Composite Views	`I_` (Interface)	Join multiple Basic Views together. Perform calculations, currency translations, and complex aggregations.
Consumption Views	`C_` (Consumption)	The final layer exposed to the end-user or UI. Tailored for specific Fiori apps, SAC reports, or external APIs. Often includes OData annotations.

Data Architecture

Fiori UX & Embedded Analytics

Fiori is the modern face of SAP, transforming the user experience from complex, transaction-code-driven screens to role-based, intuitive web apps.

Fiori Launchpad

The central entry point for S/4HANA. Users log into a web portal tailored to their role (e.g., Accounts Payable Clerk, Plant Manager) containing only the tiles (apps) they need.

S/4HANA Embedded Analytics

Because S/4HANA runs on the HANA database, it provides powerful analytics directly inside the ERP system without needing a separate BW system. This is known as Embedded Analytics.

Analytical List Pages (ALPs): Interactive dashboards blending charts and transactional data grids.
Overview Pages (OVPs): High-level dashboards showing multiple KPIs at a glance.
Multi-Dimensional Reports: Pivot-table style reporting inside Fiori, driven directly by underlying CDS Views.

Embedded vs. Enterprise Analytics: S/4HANA Embedded Analytics is strictly for real-time operational reporting on data within the S/4HANA system. If you need to blend S/4HANA data with Salesforce, SuccessFactors, or historical BW data, you need an Enterprise solution like SAP Datasphere or SAP Analytics Cloud.

SAP Analytics Cloud

Embedded vs Enterprise SAC

SAP Analytics Cloud (SAC) interacts with S/4HANA in two distinct ways: Embedded within the ERP, or as a standalone Enterprise tenant.

Embedded SAC in S/4HANA Cloud

SAP embeds a lightweight version of SAC directly into S/4HANA Cloud (and it is also available for On-Premise via specific setups). This is accessed through the Fiori Launchpad.

Use Case: Creating highly formatted operational dashboards directly on live S/4HANA data.
Capabilities: Story building and Data Analyzer.
Limitations: No planning features, no Smart Predict, and you cannot connect to external non-S/4HANA data sources. The tenant is managed by the S/4HANA system.

Enterprise SAC

This is the full, standalone SAP Analytics Cloud product. It connects to S/4HANA as a source system, alongside other data sources.

Use Case: Cross-enterprise reporting, financial planning, and augmented analytics.
Capabilities: Full suite (BI, Planning, Predictive). Can blend S/4HANA data with HR, CRM, and flat files.

SAP Analytics Cloud

Live & Import Connections

When connecting Enterprise SAC to S/4HANA, architects must choose between Live and Import connections based on the reporting requirements.

Live Data Connection

In a Live connection, SAC only queries the S/4HANA CDS Views when the user opens the dashboard. The data never leaves the ERP system.

Technology: SAC connects to S/4HANA via the Information Access (InA) service over HTTPS. For on-premise systems, this requires configuring CORS (Cross-Origin Resource Sharing) and SAML SSO so the user's browser can securely request data from the ERP.
Security: Authorizations defined in S/4HANA (PFCG roles, DCLs on CDS views) are strictly respected.
Best For: Real-time operational reporting on highly sensitive data.

Import Data Connection

Data is extracted from S/4HANA and physically stored in SAC's internal HANA database.

Technology: Connects to S/4HANA via OData Services. For on-premise, this requires the SAP Cloud Connector and SAC Agent to facilitate the secure tunnel.
Best For: Complex data blending, utilizing Smart Predict features, and establishing the base data for Enterprise Planning models.

SAP Analytics Cloud

Planning Write-back

S/4HANA integrates bidirectionally with SAC, allowing organizations to execute complex financial plans in the cloud and push the results back into the ERP.

Integrated Financial Planning

SAP provides standard Business Content in SAC specifically for S/4HANA Integrated Financial Planning (IFP). This includes pre-built models for OPEX, CAPEX, Sales, and Headcount planning.

The Write-back Process

Once planners have finished simulating budgets in SAC, the approved plan data needs to be pushed back into S/4HANA (specifically into the ACDOCP table, which is the planning equivalent of ACDOCA).

OData API Setup

An OData service for financial plan data write-back must be activated in S/4HANA.

Data Export Service

Within SAC, an Export Job is configured targeting the S/4HANA OData connection.

Execution

When triggered (manually or via a Multi-Action), SAC maps its dimensions to the S/4HANA fields and sends the records back, where they are stored as Plan versions in S/4HANA for variance reporting against Actuals.

SAP Datasphere

Connection Types (ODP, Cloud)

SAP Datasphere acts as the Business Data Fabric, and connecting it to S/4HANA is the most critical integration point for enterprise analytics.

Connecting S/4HANA On-Premise

Connecting an on-premise S/4HANA system to the cloud-based Datasphere requires secure tunneling and extraction agents.

SAP Cloud Connector: The fundamental tunnel that allows Datasphere to securely ping the on-premise network without opening firewalls.
Data Provisioning Agent (DP Agent): Installed locally, the DP Agent handles the actual data transfer protocols (Smart Data Integration - SDI).

Connecting S/4HANA Cloud

Connecting S/4HANA Public Cloud is much simpler, as it is already a cloud-native SaaS product. It relies on direct HTTPS connections and standardized communication arrangements.

Extraction via ODP Framework

Datasphere extracts data from S/4HANA using the Operational Data Provisioning (ODP) framework. Instead of extracting raw tables, Datasphere connects to ODP-enabled ABAP CDS Views.

Delta Capability: By utilizing ODP-CDS extractors, Datasphere can subscribe to Delta queues. When a new transaction happens in S/4HANA, only the changed record is sent to Datasphere, ensuring high-performance replication.

SAP Datasphere

Semantic Onboarding

Extracting data is only half the battle. Preserving the business context (semantics) when moving data from S/4HANA to Datasphere is crucial.

What is Semantic Onboarding?

When you import an S/4HANA CDS View into Datasphere, Semantic Onboarding ensures that the rich metadata associated with that view is not lost.

Associations (Joins): If an S/4HANA Sales Order CDS view has an association defined pointing to a Customer view, Datasphere automatically recognizes this relationship and builds the corresponding join in its Data Builder.
Texts and Descriptions: Technical field names are automatically mapped to their business descriptions in multiple languages.
Hierarchies: Financial Statement Versions (FSVs) or Cost Center hierarchies defined in S/4HANA are imported natively into Datasphere so they function perfectly in downstream SAC reporting.

Federation vs Replication

Once connected, Datasphere allows you to build models using two approaches:

Approach	How it works	Use Case
Federation (Remote)	Data stays in S/4HANA. Datasphere translates queries into SQL and pushes them to S/4HANA at runtime.	Real-time operational queries, highly sensitive data, infrequent access.
Replication (Snapshot/Delta)	Data is physically copied into Datasphere's HANA Cloud database via ODP.	Heavy historical analysis, blending S/4HANA data with massive external datasets, performance optimization.

Quick Reference

Interview Quick Reference

Key concepts and common interview questions across S/4HANA architecture and analytics integrations.

Key Terms to Know Cold

Universal Journal (ACDOCA): The single source of truth table combining FI and CO line items.
CDS Views: Core Data Services; the semantic modeling layer built on the HANA database replacing traditional ABAP views.
Virtual Data Model (VDM): The layered architecture of CDS views (Basic > Composite > Consumption).
Fiori: The modern, role-based HTML5 user experience for S/4HANA.
ODP-CDS: Operational Data Provisioning. The framework used to extract delta records from S/4HANA to Datasphere.

Common Interview Questions

What is the main difference in the financial data model between SAP ECC and S/4HANA? (Explain ACDOCA).
Explain the Virtual Data Model (VDM) in S/4HANA and the different types of CDS views.
What is the difference between Embedded SAC within S/4HANA and Enterprise SAC?
If a customer wants real-time reporting from S/4HANA in SAC without moving data, what connection type do you use and what are the security implications?
How do you write planning data from SAP Analytics Cloud back into S/4HANA?
When connecting an On-Premise S/4HANA system to SAP Datasphere, what components must be installed in the customer's landscape?
What is the benefit of "Semantic Onboarding" when bringing S/4HANA CDS views into SAP Datasphere?
In SAP Datasphere, when would you choose to Federate S/4HANA data versus Replicating it?