-
5.07-01 No Hierarchies
There should be no need for composite list hierarchies in the Hub. They can be built to "test" the actions, but after testing they should be deleted Exceptions: 5.07-01a Validation purposes: If data is needed to be consolidated to check against source systems, although the flat modules with attributes can be used to sum…
-
5.07-02 No Analytical modules
Try and keep Analytical modules out of the Hub Questions on this topic? See 5.07-02 No Analytical modules in our Planual forum.
-
5.07-03 Flat lists for data export
Use the flat list structures to create modules and views for downstream exports Questions on this topic? See 5.07-03 Flat lists for data export in our Planual forum.
-
5.07-04 Get the correct format
Get the data from IT in the correct format as well as the correct granularity Related to Rule: 5.04-06 Import the correct granularity Questions on this topic? See 5.07-04 Get the correct format in our Planual forum.
-
5.07-05 Use System modules
Use System modules for filtering data (current period, current FY year, etc.) Related to Rule: 2.01-15 Filters in separate modules Best Practice article: Filter Best Practice Data Hubs: Purpose and Peak Performance Questions on this topic? See 5.07-05 Use System modules in our Planual forum.
-
5.07-06 Master data should be built by the source system
Try and avoid creating Master Data in the hub. This should really come from the source system(s) Questions on this topic? See 5.07-06 Master data should be built by the source system in our Planual forum.
-
5.07-07 Keep Transactional Analysis out of the planning models
Use the Data hub (or another reporting model) to keep detailed transactional data out of the main planning models. Large amounts of historic transactional data can inflate the size of the planning model and lead to reduced performance. Questions on this topic? See 5.07-07 Keep Transactional Analysis out of the planning…
-
5.07-08 Pre aggregate for downstream exports
It is more efficient to aggregate the data in the hub and then export it, rather than accumulate it through the import to the downstream models Questions on this topic? See 5.07-08 Pre aggregate for downstream exports in our Planual forum.
-
5.07-09 Avoid using a Top Level for large lists of transaction data
Don't create a transaction list with a top level. The calculations will need to sum for all items in the list even if only a single item is added Exception: 5.07-09a Check totals: If a check total of all transactions is needed, but again using the flat attributes modules is preferable Related to Rule: 5.07-10 Add…
-
5.07-10 Add intermediate sub totals to transaction lists
If you need the totals for validation purposes, create intermediate subtotals within the transaction list. This will significantly reduce the calculation load Related to Rule: 5.07-09 Avoid using a Top Level for large lists of transaction data Questions on this topic? See 5.07-10 Add intermediate sub totals to transaction…