1.05-02 Always use a code

rob_marshall

Using codes is more efficient for loading and using lists so strive to always have a code for lists.  This is especially important for numbered lists

 

Exception:

1.05-02a Static non hierarchy lists: For simple static lists (such as Yes/No) it is OK not to have a code, but even then, Y and N can be used as codes

Related to Rule:
1.05-04 Numbered Lists should always have a code

 

Best Practices article:
Hierarchy Management

 

Misbah

Rule 1.05-02 Always use a code. Using codes is more efficient for loading and using lists so strive to always have a code for lists. This is especially important for numbered lists.

Here is how it was done in Pre Planual Era Creating a List is easy especially when you know your list items are all unique. In the past, lists were loaded without codes. Here's an example of Counties/Territories in one state in the United States.

What is wrong with this method? It is considered to be inefficient when dealing with large lists.

Here is how it should be done in Planual Way:

It has been shown that lists, especially large ones, are more practical and efficient to load if codes are used. Most importantly, however, codes can save you a lot of trouble if any of these conditions arise:

 

1. The user wants to change the list item name (Typical usage of Codes in Numbered List)
2. The IT department only provides the surrogate key or the short code for the list item
3. You need to create a 60 character or less code that requires you to concatenate more than one dimension

For List Items that require more than one code, e.g. a product SKU may have an UPC-12, UPC-14, GIN, Internal Code, Manufacturer's Code, etc.., select the most common to use as your code. The other codes can become properties in your system module - do not add list properties (Discussed in 1.05-03 Planual). 

Use-Case: A very common situation with Anaplan implementations that utilize a data hub is when a user wants to change the name of the list item. This may be because of legal reasons, for business reasons, or for strategic reasons.

Without codes, you would have to identify the original name and manually find it in the data hub, change it there then go to all the spoke applications and manually change it there too. This is not practical if 100 list items change. With codes, you can automate the process because the name may change but the code does not.

Let's say in our example above, I want to remove the word "County" from all my list items. Now that I have codes, this is an easy process.

 

Run the import script and map to codes:

 

Outcome: