Creating a Reporting Application
A Reporting application is a basic application with one cube and the core components that you need to get up and running quickly. If you later decide that you need more complex business logic, you can convert a Reporting application into a Standard or Enterprise application.
A Reporting application:
-
Consists of one cube
-
Allows you to add more dimensions
-
Allows MDX member formulas only
-
Doesn't support business rules, map reporting, copy data, copy versions, exchange rates, or currency conversion
-
Can be converted into a Standard or Enterprise application
Note:
-
To convert a Reporting application into a Standard application, see Converting to a Standard Application.
-
To convert a Reporting application into an Enterprise application, see Converting a Standard or Reporting Application to an Enterprise Application.
-
Default dimensions and characteristics for a Reporting application:
-
Account: Only the root member is provided.
-
Entity: Only the root member is provided.
-
Period: Members are created based on the answers provided during setup. Users can add an alternate hierarchy later. The Beginning Balance and Year Total periods are provided.
-
Years: Number of years, history, and future years are broken up based on the values chosen during application creation. An All Year parent is provided. More years can be added later. The default number of years is 10.
-
Scenario: Five scenarios are provided: Plan, Actual, Forecast, Variance, and Variance Comments.
-
Version: Three versions are provided: Base, What If, and Final. Hierarchical versions are allowed, for example, Base (child member)+What If (child member)=Final (parent member).
Note:
Generic members aren't added to the dimensions.
To create a Reporting application:
After you create the application, populate it by performing these steps:
-
Import metadata using the import feature. See Importing Metadata.
-
Populate data by importing data from your source system. See Importing and Exporting Data.