PerformancePoint Planning Business Modeler provides two categories of dimensions, predefined dimensions and user-defined dimensions. Predefined dimensions can be used as generated, but typically some modifications are necessary to accommodate your current data structure and naming conventions. The scope of customization for predefined dimensions is also more restricted than for user-defined dimensions.
Some examples of application planning considerations that pertain to predefined dimensions are listed below.
The Time dimension is also known as the Application Calendar and is the system dimension for maintaining a common time scale within an application. This dimension is populated and maintained by the Application Calendar wizard. See the topic, Application, model, and model site planning considerations for a list of the available calendar types.
Planning how to create your Time dimension is one of the most important planning considerations you will make for your application, as all aspects of your application refer to the time dimension in one way or another. Care must be taken to make sure that the application calendar is created to accurately match your business processes, as it cannot be modified later without creating a new application, purging data, and repopulating the data.
Another consideration when you plan your Time dimension is whether you will want to track different aspects of you business with different calendars. An application can have only one calendar, so multiple applications are required if you will need multiple calendars for your business.
The Scenario dimension is used to differentiate between data for different modeling scenarios, such as budgeted and actual values for any given period of time. One important consideration when you use the Scenario dimension is that you can only select one member of the scenario to be used for data entry per cycle. If you will want to select two members for data entry in a single cycle, such as budgeting for both best and worst case, you will have to build a user-defined dimension.
The Flow dimension is used with the Account and Time dimensions in a model to track cash flows between periods for financial models.
The Business process dimension is used for tracking business processes and performing custom calculations. It is used to store results from predefined financial calculations, such as consolidations, allocations, and currency translations.
The Exchange Rate dimension is used by the Exchange Rate Model for storing your exchange rate types and is also used by currency translation rules. Exchange rate planning considerations are discussed in more detail in the model type planning considerations topic.
The Entity dimension is used for maintaining a list of legal entities within your organization.
The Intercompany dimension is system-maintained and consists of entity dimension members involved in intercompany transactions used for reconciliations for financial consolidation.
The Consolidation Method dimension is used for performing consolidation calculations together withFinancial model with shares calculations. This dimension defines the basis for your financial consolidation processes, such as specifying equity, full, holding, and proportional consolidations.
The Account dimension is used to maintain your chart of accounts. It is important to make sure your data is accurate and consistent before uploading and assigning account types to the data in this dimension.
User-defined dimensions are dimensions that you can create, update, and delete. Common examples of user-defined dimensions include dimensions for profit centers, departments, or functional area. After determining which predefined dimensions you will use in your application, consider other ways you will want analyze your organization to identify types of user-defined dimensions you may want to create.
Member and Member Set Considerations
When planning your application, it is also important to consider the number of dimension members you will include in each dimension. For dimensions that will contain many dimension members, you can create additional dimension member sets to limit the number of accounts per model, therefore aiding application performance.