-
5.04-01 From source system, create a code defining all attributes
Ideally, this would be a separate file that is unique vs. using the same file for the transactional load Exception: 5.04-01a Code is >60 characters: If the code is >60 characters, you will have to use combination of properties Related to Rule: 5.04-02 Create separate files for attributes and data Best Practice article:…
-
5.04-02 Create separate files for attributes and data
The data file should have the key and values based on the dimensions. Non dimensional data should be in a different file Related to Rule: 5.04-01 From source system, create a code defining all attributes Best Practice article: Data Hubs: Purpose and Peak Performance Questions on this topic? See 5.04-02 Create separate…
-
5.04-03 Data or Time period should not be part of the unique row
Consider what actually makes the row unique; include only attributes in the key, not data fields or dates Related to Rule: 1.05-11 Do not embed Numeric values or Dates within the Code of a list Best Practice article: Data Hubs: Purpose and Peak Performance Questions on this topic? See 5.04-03 Data or Time period should not…
-
5.04-04 Only include the fields that are needed
Use the Ignore field if there are any unwanted fields in the source data Questions on this topic? See 5.04-04 Only include the fields that are needed in our Planual forum.
-
5.04-05 Pre aggregate in the source
Wherever possible, aggregations should be done in the source system. This is likely to reduce the size of the import file meaning faster imports Questions on this topic? See 5.04-05 Pre aggregate in the source in our Planual forum.
-
5.04-06 Import the correct granularity
Only imported data at the granularity needed. There is no need to bring in transactional data at a weekly level when Planning happens at the month level Questions on this topic? See 5.04-06 Import the correct granularity in our Planual forum.
-
5.04-07 Import using the correct formats
Line items holding the Imported line items should reflect the data. List formatted, numbers, and dates. Don’t use text (unless it is a true text field) Questions on this topic? See 5.04-07 Import using the correct formats in our Planual forum.
-
5.04-08 Never use a list as an import source
Import sources should always be done from a module view. This allows for filtering and only including the elements required for each import Questions on this topic? See 5.04-08 Never use a list as an import source in our Planual forum.
-
5.04-09 Always use saved views as import sources
Modules and saved views should be used as the source for other imports Best Practice article: Filter Best Practice Questions on this topic? See 5.04-09 Always use saved views as import sources in our Planual forum.
-
5.04-10 Unify the date format
Use a generic date format (e.g. YYYYMMDD) whenever possible to simplify the imports and remove the need for date mismatches and manipulations Best Practices article: Untangling Anaplan Time Mapping in Imports Questions on this topic? See 5.04-10 Unify the date format in our Planual forum.