- SAP Managed Tags:
Ensuring Performance in CDS Views with ATC: Tools & Test System Strategies
Introduction
In modern ABAP development, Core data services (CDS) views play an important role in defining data model and publishing those data to database through code pushdown approach. To ensure their quality and performance we have to check their critical step analysis that can be done through ATC checks in cds views.
In this blog post I am giving some ideas about tools and systems which can be used to check ATC for cds views. It is applicable for both the system whether you are working with public cloud, private cloud or on-premises system.
Tools Used for ATC Analysis of cds views
ABAP Development Tools (ADT) for Eclipse
ADT is a tool where we design/create the cds views.
Here ATC is integrated with them which is used to check performance, syntax and coding guidelines.
Here we can run ATC through right click on our cds views->run as -> ABAP test cockpit.
ABAP Test Cockpit (ATC)
- ABAP Test Cockpit (ATC) can be used to perform static check which includes:
- Query Performance, Consistency of Annotation and Coding guidelines.
Checkman tools (for cloud) System
Here we can check the ATC based on:
Application component, cds views Names or view type.
It also provides information related to priority of errors along with error message, package details and the person responsible for the views and also exemption state of cds views.
PFCDS Transaction
- PFCDS is a transaction where we can see details about error such as quality index, error types, amount of time to get query execution, system details, etc.
ATC System Setup for Cloud Environments
For public cloud, mostly we are making use of CCW/720 as a system to check ATC details because most of the table having enough no. of entries is present in this system, but it also supports some other systems such as 710.
For parameterized cds views we have to maintain proper parameter values and client system details if it is different from default system via sm30. There we need to pass table as a PFCDS_PARAMS and then we have to give our parameterized cds view name and after executing we need to give parameter and system details.
- If we have assigned wrong system details, it will be automatically taken care by system through background job in night.
ATC System Setup for On-Premises Environments
- For private cloud, mostly we are making use of CCQ/910 as a system to check ATC details because most of the tables have enough no. of entries is present in this system, but it also supports some other systems such as 911.
For parameterized cds views we have to maintain proper parameter values and client system details if it is different from default system via sm30. There we need to pass table as a PFCDS_PARAMS and then we have to give our parameterized cds view name and after executing we need to give parameter and system details.
- If we have assigned wrong system details, it will be automatically taken care by system through background job in night.
Ensuring Good Test Data Quality
Even with proper system assigned, for valid performance validation we must check whether the table having sufficient test data or not to ensure it, we are making use of some report program which is mentioned below:
PFCDS_R_NEEDED_TABLE_SIZE
This report program is used to check minimum entries and next categories entries of the table used in cds views.
- Private Cloud: Based on DDIC size category of Tables.
- Public Cloud: Based on estimated tables size in between 3-12 months.
PFCDS_DATA_QUALITY Report
- This report program is used to analyze cds views which needs more data, and it is used to display data quality index of cds views and the tables used in cds views and their deviation from expected data size.
PFCDS_SHOW_MISSING_TEST_DATA Report
It is used to track missing test data in public and private cloud such as CCW/720 and CCQ/910. We can search it by using:
- CDS view name, DDLS Source, Application Component, Package name and Tables name.
