The first level of compression is a basic type which is Dictionary compression. Further, on the second level, there are advanced compression methods that we apply to the data compressed by dictionary compression. The methods under advanced compression type are prefix encoding, run-length encoding, cluster encoding, indirect encoding, and sparse encoding.
The UNNEST function converts one or many arrays into a table. The result table includes a row for each element of the specified array. The result of the UNNEST function needs to be assigned to a table variable
ARRAY_AGG ( )– Function can be used to convert a column of an Internal Table to an Array. its opposite to UNNEST
ARRAY_AGG ( )– Function can be used to convert a column of an Internal Table to an Array. its opposite to UNNEST
CE function is Calculation Engine function with below role:
CE functions are specially optimized for HANA and can perform better than a normal SQL statement.
CE functions are executed in calculation engine.
CE functions can also help structure the code in a simpler way
CE functions are specially optimized for HANA and can perform better than a normal SQL statement.
CE functions are executed in calculation engine.
CE functions can also help structure the code in a simpler way
"Join Engine:This engine is for processing the JOINS (all type of joins)/attribute views
OLAP Engine: This engine is used to process analytical view
Calculation Engine: used by Calculation View
It is the SQL optimizer, which sees the models and queries and decides which engine to call"
OLAP Engine: This engine is used to process analytical view
Calculation Engine: used by Calculation View
It is the SQL optimizer, which sees the models and queries and decides which engine to call"
"Inner Join
Left Outer Join
Right Outer Join
Text Join
Referential Join
Temporal Join"
Left Outer Join
Right Outer Join
Text Join
Referential Join
Temporal Join"
"@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."
@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"
AMDP currently supports SQL-SCRIPT as language so ABAP code cannot be written in it.
No we cannot do so. We can set breakpoints by double clicking on the executable line
Open an AMDP class in the relevant ABAP project.
Position the cursor within the ruler (left bar) of the source editor at the line that contains the AMDP code (for example, SQLScript code) you are interested in.
Choose Activate AMDP Debugger from the context menu
Position the cursor within the ruler (left bar) of the source editor at the line that contains the AMDP code (for example, SQLScript code) you are interested in.
Choose Activate AMDP Debugger from the context menu