Custom Analytical Queries with Source Origin in ADT
In this blog post, I’ll show you how to handle with two different error messages that you can face using Custom Analytical Queries app.
The Custom Analytical Queries is used for reporting and analysis. It transforms and organizes raw data delivered from business documents into a meaningful grid. It abstracts the process of writing structured queries so that you don’t have to understand the query language or the technical details.
It also provides the fields required to design a query. You select the required fields and set filters for your query. You can add restricted measures, calculated measures, and preview the results.
Each custom analytical query has a source origin that can be, for example, Custom CDS Views. However, if a query has a source origin “ABAP Development Tools”, it becomes uneditable in the S/4HANA Cloud application.
If you try to use a query that has its source origin ADT, you’ll probably face one of the error messages below:
- Query cannot be created from the source query XXXXX.
- You do not have authorization to edit this query.
In this case, you have two options to proceed:
- Create your copy using ABAP Development Tools. Below you can find some useful documentation about ADT:
- You can use the data source cube that the original query bases as a base for a new custom query. You can find the data source for a query by simply clicking on it and checking the field “Data Source” in tab “Properties”.
To create a new query, please reproduce the following instructions:
- Open the Custom Analytical Queries app
- Click on “Create” button
- Insert the name and the data source that you want for your query (here you’ll insert the data source cube of the original query)
- Insert the field selection and display options (you can use the display options to add restricted measures, add calculated measures, create user input filters, and reorder fields)
- Apply the required filters
- Edit, Save Draft , Publish, and then Preview the query
*Custom Analytical Queries application initially creates a draft version of the queries, which allows you to update and test them. When the changes are finalized, click Publish . On publish, an OData service is created and activated, and the query is now available for consumption by reports and KPIs through the respective Report Design and KPI Design applications. On the Custom Analytical Queries page, status of the query is set as <Published>. A <Not Published> status indicates that the query has never been published.
Hope this information is useful for you!
I would greatly appreciate if you could share your feedbacks and thoughts in the comments.
Also, I encourage you to browse for other Community Topics that may be useful for you.