CDS OVERVIEW

 

Comprehensive Discussion of Core Data Services (CDS) Views

This document synthesizes information regarding Core Data Services (CDS) Views, drawing upon the provided sources and organized by the topics discussed.

I. Introduction and Definition: CDS Stands For

Core Data Services (CDS) fundamentally represent a new approach to data modeling, departing from older methods.

  • Definition: CDS stands for Core Data Services.
  • Paradigm Shift: CDS is completely based on a top down approach. This is synonymous with the code to data Paradigm, recognized as one of the important features of the Hana database.
  • Code Push Down: CDS views follow the crucial concept of code push down, similar to Application Managed Database Procedures (AMDP). This principle moves processing logic closer to the database layer.

II. Programming Approach

The programming approach associated with CDS Views is central to their definition and efficiency:

  • Core Paradigms: CDS utilizes the top down approach and code to data Paradigm.
  • Execution Location: CDS view execution takes place at the Hana database level. This contrasts with older Data Dictionary (DDIC) view consumption, which takes place at the application server level.
  • HANA Optimization: Execution at the Hana DB level enables developers to leverage the full potential of the Hana database. All calculations are performed directly at the Hana DB level. HANA is recommended because it is the most powerful effective database for real-time data processing.
  • Development Tools: CDS views can only be created on Eclipse or Hana Studio.
  • ABAP Skill Level: A developer does not need to be "Pro in ABAP programming" to create CDS views; a basic idea of ABAP is considered sufficient. The concept is noted as new to ABAPers also.

III. Technical Structure and Extensions

CDS is defined as an extension of open SQL in ABAP. This extension enhances standard SQL capabilities across several areas:

  • DDL (Data Definition Language): The DDL has been extended.
  • DQL (Data Query Language): The DQL has been extended.
  • DEL (Data Expression Language): The Data Expression Language has been extended.
  • DCL (Data Control Language): The Data Control Language has also been extended.

IV. Key Features and Characteristics

Semantically Rich Data Models

  • Definition: CDS views are characterized as semantically rich data models in SAP S/4HANA. This feature contributes to the overall power of the CDS view.
  • Annotations: This richness is achieved because developers can use annotations in the CDS view definition. These annotations, even smaller ones, in turn drive the functionality.

Execution and Database Requirements

  • Execution Level: Execution takes place at the Hana database level, allowing all calculations to be performed directly at the Hana DB label.
  • Database Requirement: While creation of CDS views is possible even if the company is not working on Hana DB, it is recommended to use the Hana database. Without HANA, one might not be able to utilize the high performance or complete efficiency or its full potential.

Functional Capabilities

CDS views possess enhanced functional capabilities compared to older structures:

  • Advanced Calculations: CDS views can easily perform calculations, aggregations, grouping, etc..
  • Join and Union Support: CDS views have support of vast number of joints and unions also.
  • Nested Views: CDS views support the concept of nested views (view on a view).
  • Result Output: CDS views always returns the single result set.

V. Comparison with AMDP

CDS Views are frequently compared to Application Managed Database Procedures (AMDP):

  • Shared Concept (Code Push Down): CDS views follow the concept of code push down, similar to AMDP. Both adhere to the top down approach and code to data Paradigm.
  • Result Set Difference: This is the big difference: CDS views always returns the single result set, whereas AMDP can return multiple result set also, corresponding to multiple internal tables.

VI. CDS Views vs. DDIC Views

The sources detail extensive reasons why CDS views are needed over traditional Data Dictionary (DDIC) views:

FeatureDDIC ViewsCDS Views
FunctionalityCannot perform calculations, aggregations, grouping, etc..Can easily perform calculations, aggregations, grouping, etc..
Join SupportSupports a limited number of joints (mainly inner joins).Has support of vast number of joints and unions also.
Nested ViewsDoes not support the concept of nested views (view on a view).Supports the concept of nested views (view on a view).
Consumption/ExecutionConsumption takes place at application server label.Execution takes place at Hana database level.
Creation ToolsCreated from transaction code SE11.Cannot be created from SE11; can only be created on Eclipse or Hana Studio.

CDS views are described as highly useful in nature due to these significant advantages over DDIC views.

Comments

Post a Comment

Popular posts from this blog

Types of Notifications/Orders/Order Category/Control Keyes

NOTIFICATION TYPES M1 - Maintenance request M2 - Malfunction report M3 - Activity report GO - General notification ORDER TYPES PM01 - Corrective Maintenance Order PM02 - Breakdown Maintenance Order PM03 - Preventive Maintenance Order PM04 - Refurbishment Order PM05 -  Calibration order PM06 -  Investment order PM07 -  Shutdown Order Note: The PM01,PM02,PM03 will be vary according to the business requirements. for Ex: Some Org's are maintain the PM02 Is preventive, Some are maintain as PM01 is Preventive ORDER CATOGERY 10 - Production Order 20 -  30 - Maintenance Order CONTROL KEYES PM01 - Internal Processing PM02 - External Processing PM03 - Refurbishment of Repairable Spares
Read more

Catalog & Catalog Profile in Plant Maintenance SAP

Image
Introduction Data on problems, malfunctions, damages, causes and problem solutions or malfunction corrections is recorded in the system or reported to the planner  responsible in the form of technical findings after a visual check, after the object has been inspected or checked, or the problem has been determined. This data forms part of the service or maintenance notification and is entered in the maintenance history. Catalog profile will group different characteristics of the notification which will cater the needs of management to analyses the company assets & to ascertain the decisions accordingly. Catalog profiles have sub class of code groups which will group the codes as per their feature. All the codes (Damage, Cause, Task & Activities) illustrate why an asset failed during production, what is the cause for that failure, tasks to be performed & activities done for that failure. The use of codes in a SAP system ensures a consistent way of documenting the key aspe...
Read more

TASK LIST TYPES USED IN SAP (PS), (PP-PI), (PM), (PP), (QM)

  ➡️ TASK LIST TYPES USED IN SAP (PS), (PP-PI), (PM), (PP), (QM) 1.Standard Network Task List in SAP A Standard Network Task List in SAP is a predefined template used in Project System (PS) for creating project networks and activities. It helps standardize project execution by defining common tasks, work centers, durations, and relationships that can be reused across multiple projects. 2.Master Recipe Task List Type in SAP The Master Recipe is a type of task list used in SAP PP-PI (Production Planning for Process Industries). It defines manufacturing steps, resources, and materials for process industries such as pharmaceuticals, chemicals, food, and beverages. 3.Rough-Cut Planning Profile in SAP A Rough-Cut Planning Profile (RCPP) in SAP is used for high-level capacity and resource planning in the early stages of production planning. It is primarily used in Sales & Operations Planning (SOP) and Long-Term Planning (LTP) to assess feasibility before detailed scheduling. 4.Genera...
Read more