LinkIndexPrint
Contents
 Welcome
    Ask MaxiPlan
 Using Cascade Planning
    Data Entry Shortcuts
 Working with Planning Projects
    Designing A Cascade Project
    Project Management
       Creating and Maintaining Projects
       Period Sets
       Currencies
       Creating A Splash Screen
       Allowing Other Users Access
       Backup and Restore
       Virtual Period Definition
       Deployment Alias
       Publish Documents
       Project Status
    Building an Application
       Building Application Models
          Building A Cube Model
             Basic Setup
             Selecting a Period Set
             Measure Settings
                Defining the Measures List
                Setting Measure Attributes
                Measure Formatting
                Defining Calculations for Measures
                Other Functions for Measures Editor
                Cross Referencing Measures
                   Dimension Order in Planning Models
                   Cross Referencing Within The Same Model
                   Cross Referencing to Another Model Cube
                   Cross Referencing to the Parent of the node
                Measure Logic Functions
                   PREVIOUS function
                   SUM function
                   MAX function
                   MIN function
                   DEPRECIATION function
                   INT function
                   ROUND function
                   ROUNDUP function
                   ROUNDDOWN function
                   IF Function
                   SWITCH Function
             Dimension Settings
                Defining Dimension Lists
                Defining Dimension Properties
             Miscellaneous
             Finishing The Model
             Advanced Features
                Specifying Consolidation Logic
          Building A Transaction Model
             Basic Set Up
             Defining Dimension Lists 
             Defining Transaction Model Fields
             Additional Definition for a List Field
             Additional Definition for an Expression field
             Additional Definition for a Lookup Field
             Optional Validation for Text, Date, Integer & Value Field
             Defining Field Format & Access
             Miscellaneous
       Model Flow and Linking Models
          Using Links (the 'Push' Method)
          Cross Referencing (the 'Pull' Method)
       Deployment and Workflow
          Deploying Models for Input and Review
          Allowing Users to Extend Models
          Setting up and Managing Workflow
          Workflow for Users
       Advanced Project Functions
          Measure Filters
          Jobsets
             Defining A Jobset
             Run Jobsets
          Data Integration
             Create Dynamic Model
             Import to Cube
             Import to Transaction
             Export Cube Data
          Maintenance
             Model Maintenance
             Link Maintenance
             List Maintenance
             Calculate all cubes
             Versions
          Pre/Post Rules
 Reports and Scripting
    Define Scripts
    Define Reports
    Publish Documents
    Manage Scripts


Home > Working with Planning Projects > Building an Application > Building Application Models

Building Application Models
Last Updated 2/21/2012 9:58 PM

 

 

Building a Cascade Planning model is a straightforward process involving the definition of the various elements of the model you wish to build. Before building the model using the Model Building Wizard, you should take the time to map out the basic elements of the model.

As a guideline, these are the basic requirements you need to know before commencing the building process:

Model Type - is the type of model chosen (either Cube model or Transaction Model)

Period Set - for a Cube model, you need to know which Period Set you will use for the model. Remember that Period Sets are common across all Cascade Planning projects. If you require a new Period Set and you do not have the necessary rights, you will need to ask your Cascade Planning administrator to create the Period Set for you. Transaction models do not require a Period Set.

Versions - Cascade automatically provides a Version dimension to keep track of different versions of the data. For example, we might wish to define Versions Actual, Budget, Forecast and Last Year. We must create at least one Version before we can build a model within a project. Versions are common across all models in a project.

Dimensions - the model dimensions that are required for this model. You will need to know the dimension members and any consolidation definition, although these can be added or amended later if required. Also, if currency conversion is required, you will need to define which dimension defines currency for the model.

Measures - the measures that will make up your model and the calculations for any completed measures.

Fields - for a Transaction model, you need to know what data that you need to collect for the model. There are various data type can be used for Transaction model, for example : Text, Date, Value, Integer, Lookup, Expression, etc.


 


See also


Model Flow and Linking Models
Deployment and Workflow
Advanced Project Functions