Aggregate functions such as MIN, MAX, AVERAGE etc donot apply to the measure at the time of query generation

• Related Articles

• Why the Aggregate functions such as MIN, MAX, AVERAGE etc is not applying to the measure at the time of query generation?

  The aggregate functions do not apply for the measures that are created by referring the Dimensional tables (E.g. DIM_STORE). The aggregate functions apply only when the measures refer Aggregate tables (E.g. AGG_MLY_STORE). This is the functionality ...

• The aggregate functions (For example, MIN, MAX, AVERAGE, etc.) do not apply to the measure, while generating query. Why?

  The aggregate functions are applicable for the measures only when the measures refer Aggregate tables (Example, AGG_MLY_STORE), and not when the measures refer dimensional tables (example, DIM_STORE). This is the functionality of ARC.

• When I add a base measure with average aggregation, the Total field should show the average value. But why is it showing the sum of that average?

  The sum of the average is displayed in the 'Total' field becauase the functionality is to display the total value and not the average value. When you add a base measure with average aggregation, it considers only the line items and not the 'Total' ...

• While adding a base measure with average aggregation then, the total field should show the average value, but it shows the sum of that average. Why?

  Whenever the aggregate functions are applied, it will consider only the line items but not the TOTAL column. Total field always displays the summed-up values from the line items.

• Why does the FINBI KPI AR - Billers Transaction Count report generation taking a long time?

  The KPI you are analyzing refers to viewsql to fetch data. To reduce the time taken for report generation, alternatively create this view in the database so that retrieval of data will be faster from the database. Once this view is created in the db, ...