Managing changes of the business in the ERP.

During an ERP implementation great effort is set to ensure that the ERP matches the business of the company. Over time the company’s businesses change. Business units are added/ terminated, products are replaced, and employees’s leave the company and new begin. These natural changes within all companies and they need to be reflected in the ERP-system. Since these are core parts of the ERP, changes within these master keys can cause severe damage to the ERP. Up until now these changes have been made manually. 

The Accure Way

To create a new Master key a job is designed that selects a Master key of the Live environment. The selected master key is used as a blueprint, on top of that changes are designed in regards to scope, names etc. For example when creating a new Division in the Environment, an existing division is selected as a blueprint. a3.ENV copy all information needed from the blueprint, but change the name of the Division and does not include any transactions. 

When deleting an existing Master key, the a3.ENV can simulate the deletion of the Master key. The simulation shows which Master data that can be archived or deleted without harm to the M3/ Movex system.

After simulation the deletion can be performed.