What is data lineage in SAP S/4HANA?

Data lineage describes the path data takes from physical database tables through CDS View chains (Basic → Composite → Consumption) to OData services and Fiori applications. It shows which tables feed into which views and how fields are mapped through the chain.

How can I trace data lineage for a CDS View?

CDSee provides a Lineage Tree (horizontal upstream/downstream view), a 3D Force Graph (interactive dependency visualization), and Field Mapping (source table column tracking) for every CDS View and table in the system.

Guide March 3, 2026

Understanding Data Lineage in SAP S/4HANA

Explore how data flows from physical tables through CDS View chains to consumption layers in SAP S/4HANA, and how to trace field lineage.

What Is Data Lineage?

Data lineage describes the path that data takes from its origin (physical database tables) through intermediate transformations (CDS Views) to its final consumption point (OData services, Fiori apps, analytical reports). Understanding lineage is critical for impact analysis, debugging, and data governance.

The CDS View Chain

In SAP S/4HANA, data flows through a multi-layered chain:

Physical tables — Where data is stored (e.g., BKPF, BSEG)
Basic CDS Views — Clean abstraction over tables with business-friendly names
Composite CDS Views — Join multiple Basic Views for richer entities
Consumption CDS Views — Application-ready views with UI and authorization annotations
OData Services — Expose Consumption Views as REST APIs
Fiori Applications — Consume OData services for end-user interaction

Tracing Lineage with CDSee

CDSee provides three ways to explore data lineage:

Lineage Tree — A horizontal tree showing upstream (data sources) and downstream (consumers) for any CDS View or table
3D Force Graph — An interactive 3D visualization of the dependency network with color-coded VDM layers
Field Mapping — Drill into individual fields to see which source table column they originate from

Why Lineage Matters

Impact Analysis — When a table or view changes, which downstream consumers are affected?
Debugging — If data looks wrong in a Fiori app, trace backward to find where the transformation goes wrong
Data Governance — Understand where sensitive data fields (like personal data) flow through the system
Custom Development — Find the right released CDS View to build on