Using Application Statistics
  • 3 Minutes to read
  • Dark
    Light
  • PDF

Using Application Statistics

  • Dark
    Light
  • PDF

Article summary

Overview

Power users can access the Application Statistics page by selecting the Manage task and the Application Administration, Application Statistics subtask. This page provides information on database size, number of models, license information, and much more.

Setting up the Target/Master Model using a Map

You need to be familiar with the high-level outline of the Source model or Structured Planning, Consolidation, or Reporting application and know what you want to use in your Target model before continuing this process. It will help to look at information about the metadata that was downloaded from Structured Planning, Consolidation, and Reporting applications.

Power user access is required for these steps.

Manage > Application Administration > Application Statistics

Navigate to Manage > Application Administration > Application Statistics. The Application Statistics page shows the number of models in your application, your software license user restrictions, user types, disk space consumption, and numbers of dimensions and members in each model.

Under Source Models, you will see HACPM_Financial, its disk usage and number of records.

Look further down the page to see more details about HACPM_Financial:

  • Dimensions: shows the categories of information that exist in Structured Planning, Consolidation, and Reporting applications and how they have been mapped to dimensions in Dynamic Planning.

  • Type: shows the dimension types in HACPM_Financial. Remember, they have no meaning here, so just ignore them.

  • Member Count: shows the maximum number of members that you have access to when defining your Target model.

  • Hierarchy Levels: shows the number of levels of parent/child relationships in the dimension.

image14962020por.png

Power or Contributor user access is required for the remaining steps.

Description of Fields

A description of each field on this page is provided below.

Application - The name of your application.

Database Size - The size of your database in megabytes.

No of Models - The number of models that reside in your application.

License Details / Purchased / Utilized - The user role, which can be Power, Contributor, or Reviewer. The number of licenses purchased for each user role and the number of licenses being used for each user role. Your license count is the number of allowed Business users. External users do not count toward the license count.

User Types - Lists the count of External vs. Business users. Business users are internal to your organization. External users are those such as Planful Support or Partners.

Source Models / Size / Records - A listing of your source models, the size in megabytes of each, and the number of records (transaction) in each source model. Source models, like HACPM_Financial, are the source data you drill into and copy data from.

Master / Analytic Models:

  • Type – Analytic or Master as defined on the Model Setup page
  • Size – The size in megabytes of the model
  • # Dimensions – The number of dimensions defined for the model. Dimensions are defined on the Model Setup and Model Dimension pages
  • # Attributes - The number of Attributes defined in the model. An Attribute, such as color, can have several attribute members
  • # Key Dimensions – The number of key dimensions (which is a dimension type) defined for the model. Dimensions are defined as Key or Value on the Model Setup page
  • # Value Dimensions – The number of value dimensions (which is a dimension type) defined for the model. Dimensions are defined as Key or Value on the Model Setup page
  • Key Member Count – The total number of key dimension combinations per model
  • Value Member Count – The total number of value dimension combinations per model. This number corresponds to the model's block size
  • Records – The number of database records (rows or documents) stored per model. In most cases, this number corresponds to the number of blocks in existence for the model. This count helps determine an optimal Key or Value scheme when defining model dimensions. For customers who have opted in to Data Storage Partitioning, the number of records corresponds to the number of sub-blocks in existence for the model. For information on Data Storage Partitioning, see Model Restructure.

Model:

  • Dimension – The dimensions that belong to the model listed
  • Type – The dimension type
  • Member Count – The number of members that belong to the dimension
  • Hierarchy Levels - The number of layers of parent-child relationships in each dimension in the model

Was this article helpful?