"@Consumption.valueHelpDefinition: its based on some other CDS view and its field
@ObjectModel.foreignKey.Association: its based on the Association defined in the same view."
"Odata can be created in 4 ways:
1.ABAP code-based implementation: done using DPC_EXT class
Based on SADL framework(Data model driven approach)
2.Mapping Editor:
3.Reference Data source
4.Using annotation: odata.publish: true in CDS"
1.ABAP code-based implementation: done using DPC_EXT class
Based on SADL framework(Data model driven approach)
2.Mapping Editor:
3.Reference Data source
4.Using annotation: odata.publish: true in CDS"
By using the annotation @OData.publish : true
Metadata Extension is useful in segregating the UI/Consumption related annotations from the Actual CDS.
It is very handy for enhancing the UI without impacting the CDS. It establishes a loose coupling between Data Model and UI annotations.
@Metadata.allowExtension: true
It is very handy for enhancing the UI without impacting the CDS. It establishes a loose coupling between Data Model and UI annotations.
@Metadata.allowExtension: true
CDS access control is used to perform authorization checks.
Annotation used is @AccessControl.authorizationCheck
Annotation used is @AccessControl.authorizationCheck
If logic is more complex then CDS cannot help in achieving code pushdown. We will have to use Table function with CDS.
ABAP CDS is reusable.
CDS helps in achieving code pushdown.
Act as a single model for Fiori apps.
Can help us to write SQL script inside ABAP using Table function.
CDS helps in achieving code pushdown.
Act as a single model for Fiori apps.
Can help us to write SQL script inside ABAP using Table function.
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.
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.
ABAP CDS & HANA CDS.
Further ABAP CDS has categories:
Interface Views,
Composite Views &
Consumption Views.
Now we have further types under these:
CDS with Parameter
CDS with join
CDS with association
Extend view etc.
Further ABAP CDS has categories:
Interface Views,
Composite Views &
Consumption Views.
Now we have further types under these:
CDS with Parameter
CDS with join
CDS with association
Extend view etc.
We have inbuilt functions for this unit_conversion & currency_conversion