Parts Dimensions
Parts dimensions allow you to break the model up into any number of parts, or slices, by selecting which FO Instances to include in each element of the dimension.
Important Note: There is one element, titled "All", that includes all FO Instances in the model and cannot be deleted. This is necessary so that you always have a parts dimension selection that does not exclude any FO Instances. New parts are added by clicking and selecting .
Synchronized and Unsynchronized Parts Dimensions
An unsynchronized parts dimension is one built from scratch. Parts can be added, removed, retitled and redefined by creating custom FO Sets. A synchronized parts dimension is kept synchronized with a specific FO Attribute or Hub Type. As the FO Attribute or Hub Type changes, so does the synchronized parts dimension. Parts cannot be removed, added or changed. Synchronized parts dimensions can be changed to unsynchronized parts dimensions (and back again).
Automatic Creation of Synchronized Parts Dimensions
Parts Dimensions can be created automatically for any FO Attribute or Hub Types. To do so, go to Model Dimensions and Scenarios/Model Dimensions and
Common FO Set
Additionally, FO Sets can also be defined globally in Model Infrastructure and applied to all parts in a given Parts Dimension. This allows you to define a common set of FOs, avoiding the need to add them individually to each part.
The Default Part
Notice that as you add parts to the dimension that the parts appear in columns, each new part being added to the bottom. The part that is at the top is the Default Part In a Parts Dimension, the part at the top of the list. It is always the 'All' part., the "All" element. The Default Part for a dimension is important when the in Model Parametersis set to . If no default scenario is selected, the Default Part will be used in any report whose Framework does not explicitly specify the part to be used.
FO Sets
FO Sets allow you to specify which FOs are to be included in any given part in a Parts Dimension. FO Sets can be configured such that, as new FOs are added to the model, the FO Set is automatically extended without the need for a specific reference to each FO.
Kinds of Matching
FOs can be added to the list using a variety of matching criteria:
Group or Line Item
How to read the parameters - Add any FO that matches the selection. Negate?=Yes will add any FO that does not match the selection.
FOs are added to the list by selecting/drilling down to groups of FOs or individual FOs in the following categories:
- Income Statement - This selection will include all Income Statement FOs. Drill down further to select a specific group or instance.
- Balance Sheet - This selection will include all Balance Sheet FOs. Drill down further to select a specific group or instance.
- User Defined - This selection will include all User Defined FOs. Drill down further to select a specific group or instance.
Example:
Add any FO that matches the selection (Income Statement, Revenue).
Result: Adds all Revenue FOs
Negate?=Yes will add all non-Revenue FOs.
FO Parameter Type
If you want FOs to be added to the list based upon its FO Type . Drill down and select the Financial Object Type.
Example:
Add any FO that is of the type Basic Income.
Result: Adds all Basic Income revenue FOs
Negate?=Yes will add all FOs that are not of the type Basic Income.
Submodel/Library
FOs will be added to the list if they are included in a specific Library or Model import.
Data Store Import
Any FO that contains imported data from a specific Data Store Import will be included in the list.
FO Attribute value
Select the FO Attribute and then type in a string A sequence of characters. that is to be matched. If a match is found between a FO and a FO Attribute value, the FO is added to the set.
If a Hub is used as the matching criteria, all the hub's connections will be added to the list.
Line Item Sets
If a line item set is used as the matching criteria, then all line items in the set are added to the list (e.g. set union)
Negate?
This selection is useful when there is more than one Step and you want to add or remove items from the result of the previous step (In the first Step, "Add" and "Negate: do" or "Remove" and "Negate: do not" will return the same set of items).
Working with Combinations of Operations and Negate
Combinations of (Add - Remove) and (No - Yes or Do - Do Not) modify the list of FOs by adding or removing items that either match or do not match a specified criteria.
Let's say you currently have the set {a,b,c} from previous steps:
- Add means you are adding to the set, so that {a,b,c} will be in the resulting set no matter what. The set can only get bigger.
- Remove means you are removing items from the set, so that you won't have more than {a,b,c}. The set can only get smaller.
- Add Not x means to add everything that is Not x to the set.
- Remove Not x means to remove everything that is Not x from the set.
Examples (Assumes {a,b,c} is the starting set):
- Add {b,e} = {a,b,c,e}
- Add Not {b,e} = {a,b,c,d,f,g,h, ... }
- Remove {b,e} = {a,c}
- Remove Not {b,e} = {b}
For the first step only, if you use Add, the initial set is the empty set, but if you use Remove, then the initial set is everything.
Examples
- Step 1: Add {b,e} = {b,e}
- Step 1: Remove Not {b,e} = {b,e}
- Step 1: Remove {b,e} = {a,c,d,f,g,....}
- Step 1: Add Not {b,e} = {a,c,d,f,g, ....}