First Steps in SAP S/4HANA Embedded Analytics

2.1 Query browser

Let us start with a query browser. This is a primary discovery tool for all customers and the only one for those using a public cloud edition of SAP S/4HANA. It may be utilized by on-premise customers with the potential downside that it will only contain queries built using a CDS technology (see Chapter 4 on choice of technology for queries).

Query browser allows us to cover three main tasks:

• Search for queries
• See a definition of a selected query
• Preview the query data in multidimensional reporting client

It can be accessed under group Query Browser and tile Query Browser (as shown in Figure 2.2).

Figure 2.2: Query Browser tile

The direct link to it is: /sap/bc/ui5_ui5/ui2/ushell/shells/abap/FioriLaunchpad.html#AnalyticQuery-browse

Our starting point is, intuitively, a search. When we enter a keyword in the search box, the system will be queried and results will be displayed. Search is executed over the names of the queries as well as fields contained in the query. As shown in Figure 2.3, we see results sorted by relevance. Both standard and custom queries are displayed. Further, we may choose to mark one or a few queries and add them to our favorites or tag them with any keywords (see respective buttons in bottom-right corner in Figure 2.3).

Figure 2.3: Query Browser search

Once a particular query is selected, we get into a definition of it, i.e., all the fields available are listed so we can learn the maximum level of detail for a selected query.

Figure 2.4: Details of a selected query—journal entry analyzer

Last but not least, we may want to preview the data delivered by this query. To do so, we click the Open for Analysis button in the bottom-right corner.

Figure 2.5: Query output—journal entry analyzer

So, query browser is an ultimate starting point to begin discovering the analytics content in an SAP S/4HANA system.

Some examples where Query Browser comes handy:

• as a query catalogue
• as a search tool for queries and fields
• to shortlist the potentially relevant queries for more detailed review
• to share with developers the queries that need to be potentially altered or copied