All,
Without revealing any trade secrets, looking for any common threads on what on-premise CRM system s do more from a policy or procedure in creating BP & customer hierarchies.
Starting with BP's, where CRM can support multiple addresses for a single BP, we still tend to create a new BP for each location where we do business or where the contact resides. Most of this is related to the integration with ECC and it's limitation of a single address for an account.
So if we deal with XYZ Inc, and we have customer contacts 3 offices we will have 3 BP's for XYZ Inc. Not a right or wrong but a guideline we follow.
On the customer hierarchy side, there are options to create a hierarchy in ECC which can replicate to CRM (generally used for pricing ) or CRM can have their own hierarchies which do not replicate to ECC.
For reasons where not all of our accounts replicate to ECC we elected to use CRM customer hierarchies & primarily for reporting purposes.
This is where the set up gets complicated from a best practice perspective. The CRM customer hierarchy is very flexible, can be very flat or many levels depending on your scenario. Trying to manage in an enterprise mode is challenging as there do not seem to be right or wrong answers.
Would like to see if anyone wants to share their best practice. We may look for 3rd part resource like D&B (or other vendor) to provide a mapping of our accounts and we write a Z program to upload and maintain the relationships (BP's to the nodes)
