What is the Virtual Data Model (VDM) in SAP S/4HANA?

The VDM is SAP's layered architecture of CDS Views: Basic (table abstraction), Composite (enrichment), Consumption (application-ready), and Transactional (CRUD). It provides a structured, stable, and secure way to access S/4HANA data instead of querying tables directly.

Why does SAP use a Virtual Data Model instead of direct table access?

The VDM provides stability (released views are backward-compatible), security (authorization at the view level), reuse (shared views across applications), and performance (optimized for SAP HANA). Direct table access bypasses all of these guarantees.

Guide March 3, 2026

VDM (Virtual Data Model) in SAP S/4HANA Explained

The SAP Virtual Data Model (VDM) is a layered architecture of CDS Views. This guide explains each VDM layer and its purpose.

What Is the Virtual Data Model?

The Virtual Data Model (VDM) is SAP's layered architecture for organizing CDS Views in S/4HANA. Rather than allowing applications to access database tables directly, SAP provides a structured hierarchy of CDS Views that abstracts, enriches, and secures data access.

VDM Layers

The VDM consists of four layers, from bottom to top:

1. Basic Layer (Interface Views)

Direct abstraction over database tables. These views provide stable, business-friendly field names and serve as the foundation for all higher layers. Typically prefixed with I_.

2. Composite Layer

Joins and enriches Basic Views to create more complete business entities. Still generic and reusable across multiple consumption scenarios.

3. Consumption Layer

Application-specific views with UI annotations, authorization checks, and filters. Designed for direct use by Fiori apps and OData services. Typically prefixed with C_.

4. Transactional Layer

Enables create/update/delete operations as part of the RAP (RESTful Application Programming) model. Used for Fiori apps with editing capabilities.

VDM Data Flow

Database Tables (BKPF, VBAK, ACDOCA, ...)
       ↓
Basic Views (I_SalesOrder, I_BillingDocument, ...)
       ↓
Composite Views (I_SalesOrderItem, ...)
       ↓
Consumption Views (C_SalesOrderTP, C_BillingDocList, ...)
       ↓
OData Services → Fiori Apps

Why VDM Matters

Stability — Applications built on released Consumption Views are protected from table changes
Reuse — Basic and Composite Views are shared across many applications
Security — Authorization is enforced at the Consumption layer via access controls
Performance — SAP optimizes the entire VDM stack for SAP HANA pushdown