VDM Annotations

Allow classifying views of the virtual data model in terms of their admissible reuse options and provisioned content

Scope and Definition

@Scope:[#VIEW, #TABLE_FUNCTION]
Annotation VDM
 {
   viewType : String enum { BASIC; COMPOSITE; CONSUMPTION; };
   private : Boolean default true;
 };

Usage

VDM is intended to be interpreted by view browsers and other functionality which is based on the virtual data model.

This classification is used only for SAP internal structuring and interpretation of the CDS views. Releasing CDS views for customers and partners is controlled by additional internal classification of the views.

Annotation	Meaning
`VDM.viewType`	Defines the type of a VDM view Scope: #TABLE FUNCTION, #VIEW Evaluation Runtime (Engine): None - Used for SAP internal structuring and interpretation of the CDS views Values:
	Value	Description
	`BASIC`	views that form the core data basis without data redundancies.
	`COMPOSITE`	views that provide data derived and/or composed from the `BASIC` views.
	`CONSUMPTION`	views that serve for specific application purposes and may be defined based upon public interface (for example, `BASIC` and `COMPOSITE`) views.
`VDM.private`	Private interface (for example, BASIC and COMPOSITE) views represent technical helper views which may only be used by their defining responsibles. Scope: #TABLE FUNCTION, #VIEW Evaluation Runtime (Engine): Interpreted by ABAP Runtime Environment

Examples

Example 1

Defining a public basic VDM interface view:

Sample Code

@VDM.viewType: #BASIC
define view I_SalesOrder ... { 
	key SalesOrder, 
	...
}

Example 2

Defining a private composite VDM interface view:

Sample Code

@VDM.private: true
@VDM.viewType: #COMPOSITE
define view P_SalesOrderItemCube ... { 
	key SalesOrder,
	...
}