Skip to Content

You’re interested in the implementation patterns of CDS views in SAP’s digital core? Then the keyword here is VDM.

SAP S/4HANA’s virtual data model (VDM) uses ABAP CDS views to offer a simplified, easy-to-understand and harmonized data model on top of the suite tables (but avoiding their cryptical technical names). It is enriched with business semantics and enables an easy consumption of the business data.

ABAP CDS allows the definition of semantically rich data models providing all metadata that are necessary to build analytical or transactional apps or even remote APIs.

VDM represents the cornerstone of the programming model in SAP S/4HANA.

The main characteristics of VDM views are:

  • Business-oriented
  • Easily understandable & semantically rich
  • Reusable & stable
  • Executed on SAP HANA

Customers and partners can develop on top of the released VDM views.

In the session S4H220 – Implementation Patterns for CDS Views in SAP S/4HANA at SAP TechEd 2017, some insights were provided by SAP’s experts on how the virtual data model is structured and how to implement the different types of core data services views required for building analytical apps, transactional apps and remote APIs.

View the presentation (PDF)

 

Related Information in the SAP Community

To report this post you need to login first.

3 Comments

You must be Logged on to comment or reply to a post.

  1. DurgaPrasanth vemula

    i have a requirement where i need to disable the field in the standard CDS View ‘C_PurchaseReqnItem’ and as per the below it is displaying the Field PurReqCreationDate in the “Manage Purchase Requisition Professional” Fiori App.

    @UI: { fieldGroup: { qualifier: ‘QuantityDate02’, position: 20, importance: #HIGH } }

    Document.PurReqCreationDate,

    Now My Requirement i need to disable the field as i had to use annotation

    @ObjectModel.readOnly: true

    i had done the below code

    @AbapCatalog.sqlViewAppendName: ‘ZCPURREQNITM’

    @EndUserText.label: ‘${ddl_source_description}’

    extend view C_PurchaseReqnItem with zC_PurchaseReqnItem {

    @ObjectModel.readOnly: true

    Document.PurReqCreationDate }

    But I am getting error “View field PURREQCREATIONDATE-C_PURCHASEREQNITEM already exists in parent object (DDL source )” could you please help how to handle this situation.

    (0) 

Leave a Reply