Data Quality and Code Recycling
Recently I’ve heard for one not so rare practice performed by IT or technicians. Re-usage of old codes. Meaning, old and inactive codes for some time from Information System are filled with new content/product and being used in systems. Old code appear once again in the systems with new amounts and contents. Like a Phoenix.
From the perspective of savvy engineers this sounds like a reasonable idea. Why not, if empty column in table, dimension or switch is reused… why should not be the same with codes?
Financial colleagues do not allow such policy. It’s strictly forbidden and with reasons. Historical financial data are important and need to be compared with current and future amounts. It would be not possible to compare anything especially not company performance if financial indicators were messy.
Since company Information Systems consist of financial systems too it is very reasonable to spread the rule to non-financial systems. It will allow more transparent work of processes and ease reporting. It will for sure reduce portion of generated errors.
Do not recycle codes and notify all IT experts about this important rule. There is no Master Data Solution, data integrity processes and cleansing tools that can repair damage made with code re-usage. It is simple data quality rule that needs only certain extra promotion.