Adding some thoughts to Wcho ‘s response, data in Netsuite are usually at a detail level not required for planning or consolidations. In this situation I might encourage design to summarize into OS the data coming out of NS using many to one mappings in the xformation rules.
The thinking is it’s not necessary to maintain the same level of detail in two systems capable of producing reports, nor is it always necessary to have ERP level of detail in a system used for planning or consolidation.
Huge thank you for your response, I appreciate it.
I agree with all your points.
The business would like to make changes to the external ID and the description of many accounts, further they would like to, in some cases, shrink the number of NetSuite accounts from many to one. They feel that if they have mapped using the internal IDs this will reduce their maintenance, because the internal IDs will always be the same ....
My feeling is that the internal ID will mean nothing to the end user when they drill down and see the detail from the data upload?
I also feel that the changes made to the accounts when in the sandbox environment, unless made in exactly the same order and not allowing for any errors, during the development/maintenance process, will end up meaning the internal IDs can be different in the two environment, only on the affected accounts, but if we test mapping from the sandbox and then migrate to production ...
I would prefer to use many to one mappings in the xformation rules, but would prefer to use the external ID because it is not just randomly assigned and using the external IDs allows for mapping of ranges etc, whereas internal IDs required explicit mappings for every single GL account?
