From the Technical Information screen, you get an overview of important, technical, reference numbers for a query.
In order to access the Technical Information screen, choose a query from the Query Monitor screen and then Technical Info.
The technical information is created automatically.
The technical information is grouped by category for the selected query. Depending on the query definition, all or part of the categories are displayed. The first line of the HTML control contains links to the categories that are displayed in table form in the lower area of the page.
System entries are specified in the first column for some of the categories:
The symbol means that the value of the technical reference numbers corresponds exactly to the system recommendation.
The symbol means that the value of the technical reference numbers possibly does not correspond to the system recommendation.
The symbol means that the value of the technical reference numbers does not correspond to the system recommendation. In this case, changes may be useful. This does not necessary mean that an error exists.
· Target(s)
· Technical name of the query definition
· Last change to the query definition (date and time)
· Query name (technical name and internal name)
· Name of the generated programs (Using Display Gen. Report, you can display the program; see below).
· Query generation time (see under Cache-Relevant Data)
· Version (external/internal)
· Generation status (active/inactive)
· Read mode (for more information, see Read Mode)
· Released for OLE DB for OLAP (for more information, see Query Properties)
· Calculating before the aggregation (for more information, see Selection/Formula Properties)
· Virtual characteristics/key figures
· Attributes in calculated key figures
· Currency translation in the query definition
· Query can use aggregates
· Value field groups (groups of key figure IDs or selection elements and basic sizes for the form elements, combined by specific properties, for example, their aggregation behavior or by specific steps of the process that are required, for example, calculating as packed numbers)
· Key figure IDs for display (KIDs)
· Calculated key figure IDs
· Constant selection (for more information, see Constant Selection).
· Fiscal year variant
· Query key date
· Link to the Cache-Relevant Data table (see below)
· There is a non-cumulative value with AVI
· There are non-cumulative values with LAST or FIRST
· There are non-cumulative values with MAX or MIN
For more information about the types of exception aggregation for non-cumulative values, see Aggregation Behavior of Non-Cumulative Values
· More than a provider of non-cumulatives (see Evaluating Non-Cumulative Values in the InfoCube definition section)
· NCUMTIM is not unique (see Time Reference Characteristic)
· Query does not interrupt the critical interval (see Validity Period)
· The non-cumulative method L1 is required
· The non-cumulative method L2 is required
This section runs the statistics by specifying the current and maximum number:
· InfoCubes involved for the MultiProvider
· FEMS number (selection groups)
· Number of elements in structure 1 and 2 (for the structures in the columns and rows)
· Selection rows
· Columns in the SP storage table
· Free characteristics
· Basic key figures
· Formula components
· Hierarchies
· Hierarchy nodes
· Variables
If a query has invisible drilldown characteristics, they are displayed in this section with their technical name and description, for example:
0CURRENCY Units or currency field
· Query can use the cache (if necessary, with specifying the reason why the query cannot use the cache)
In addition, this section includes important time stamps:
· Query generation time (corresponds to the specification under OLAP-Relevant Data)
· Time of the last loading of data into the InfoProvider (last data change)
· Last change to data value set (pre-calculated value set)
· Last master data change for navigation attributes
This time stamp influences the invalidation of the cache. If the last time stamp for a cache entry for the selected query is older than one of the above-named time stamps, then the cache is rebuilt.
· Optimizes table sizes
After a query has been executed for the first time, the OLAP processor determines the optimal initial size of internal tables and generates the report automatically afterwards. The system shows the date and time of this last update. If the query definition is not changed, a new optimization does not take place automatically. You are able to force a new optimization however by choosing the link Optimize Again.
This section restricts ABAP programs. If these are not complied with, then the report is not generated, and the query is not executed.
· PXA buffer
· Static control blocks
· Variable control blocks
· Literals
· Structure descriptions
· Includes
The following functions are available in the screen toolbar:
Function |
What You Need to Know |
Display Gen. Report |
|
Query Def. Designer |
Goes to the ABAP debugger. You see the code for the interface between the BEx Query Designer and the OLAP processor |
Query Def. Processor |
Goes to the ABAP debugger. You see a few lines of the coding according to the above-named interface. For this break point, the complex data structure SX_REPORT and internal control tables are displayed for the query |