1
CDS View activation generates 2 objects:
CDS View Entity(consumed everywhere) & SQL view at DDIC level.
Cardinality is used to define the relationship among tables. It can be such as ZERO TO ONE, ONE to ONE,ONE To MANY, MANY to ZERO represented as [0..1],[1..1], [1..*], [*..0]
Path expression is like a where condition which is used inside the CDS select to filter the data.
0
"@ObjectModel.foreignKey.association:’_AssicationName’: This Annotation is used for Value Help from association based on the Key Field.
@ObjectModel.text.element: [‘Fieldname’]: This annotation is used for Value Help for Key field to display the Text also. E.g field name is Customer Name for Customer Number.
@Consumption.valueHelp: This Annotation is used for Value Help from Associations.
@Consumption.valueHelpDefinition: This Annotation Used for Value Help from another CDS view or Value Help CDS."
1
"Use of Order BY cluase while selecting data from tables.
Use of Inline declaration.
Use of Inner join on tables compared to For all entries. Use of data calculation related functions while selecting the data to reduce further roundtrip from DB.
All cluster and some pooled tables are converted to transparent tables in HANA. Hence queries on Cluster/pooled tables returns results sorted by primary keys is no more true here. Any custom coding which accesses physical table cluster/pool has to be changed so that the program reads from tables directly"