2.01-13 Separate Transaction data from Attribute/Property data

Keep the non-time-based data in a separate module from static attributes


Best Practice article:
Data Hubs Purpose and Peak Performance



  • Rule 2.01-13 Separate Transaction Data from Attribute/Property Data. Keep the non-time based data in a separate module from static attributes. It goes against NECESSARY element of PLANS if you wish to go against the rule

    Here is how it was done in Pre Planual Era: Even after best practices on Data Hub we still used to accept the unique key and load as is from the source system without analyzing the components of the key.  Remember there are 4 Corner Stones and Data is one among the largest piece of the puzzle. Hence spend good amount of time in analyzing the data. Here is the unique key which gets loaded into the system.


    What is wrong with this method? It looks like a prefect key to be loaded into Anaplan as there are no time periods in the key, there are proper delimiters, no duplicates etc. But if you look at the key closely it might not be the ideal key to be loaded as is into Anaplan as there can be attributes as well which do not change with time. In the below key Segment is an attribute of Customer


    Here is how it should be done in Planual Way: Understand the source data and the unique key carefully and see if the key contains any attribute which doesn’t change with time and follow the steps

    Step 1: Create an attribute module within Anaplan and store the mappings between the two as one time activity


    Step 2: Load the key without Segment Part of it. Here is the ideal key to load into Anaplan


    Step 3: Create a SYS module to extract all components of the Key and reference Segment (Step 1)


    Step 4: In the Data module just reference Segment & Other Attributes from Attribute Module and create a view to be sent to spoke model