Here is an overview of the most significant changes in the context of CDS view building tools that relate to the:
Example:
@ClientDependent: true define table function GET_SCARR_SPFLI with parameters @Environment.systemField: #CLIENT clnt:abap.clnt, carrid:s_carr_id returns { client:s_mandt; carrname:s_carrname; connid:s_conn_id; cityfrom:s_from_cit; cityto:s_to_city; } implemented by method CL_DEMO_AMDP_FUNCTIONS=>GET_SCARR_SPFLI_FOR_CDS;
Tool Support
The DDL editor provides support for:
Starting with SAP NetWeaver 7.50, you have the option to extend views in ABAP CDS.
Example:
@AbapCatalog.sqlViewAppendName: 'DEMO_CDS_EXTENS' extend view demo_cds_original_view with demo_cds_view_extension { spfli.distance, spfli.distid as unit };
Tool Support
The DDL editor provides support for:
For each CDS entity that is defined in the DDL editor, you now have the option to view the SQL CREATE statement generated at database level.
For more information, look here:
You can now apply a wizard for defining ON conditions in JOIN clauses and ASSOCIATION definitions of your CDS view definition.
For more information, look here:
When implementing the view on view pattern, the relations between the resulting data sources can become very complex. The Dependency Analyzer aims to give the CDS developer a better overview of the complexity of the SQL behavior so that this complexity might be reduced and/or superfluous JOINs might be found.
For more information, look here: