Merit Solutions has spent a lot of time over the past couple of months demoing our Microsoft Dynamics GP Risk Management Suite and its capabilities to new prospects while providing training to existing clients looking to upgrade. In both situations, two questions always seem to pop up:
- How do we make sure that we get (got) the roles and users right?
- How do we make sure we don't create a burden with tracking too many changes?
Interestingly enough, the answer to both is very simple. The implementation - not so simple.
- The first thing that each client has to ensure is that their business processes are efficient and that their ERP system is setup in a way to support those processes. The Risk Management Suite will comply to any set of rules you require - helping you increase your efficiency while making sure you comply with regulations. To receive the maximum value, efficient business processes have to be in place - and, often, that is not an easy task to complete.
- As for the second question, we recommend that tracking changes should be limited to business critical fields, tables, and processes, as that will make the system easier to implement, changes easier to track and will help a company meet compliance regulations.
On occasion, companies tend to track everything, including tables with high volume of transactions. While this is possible to do with Audit Trails, as with any other Microsoft Dynamics GP table, this is not recommended, as it will affect performance of your SQL Server, which will in turn affect all users and systems that use it.
In order to generate the highest value from the Risk Management Suite, we suggest that companies craft a smart tracking plan prior to implementation with procedures and policies in place that limit adding new tables to Audit Trails tracking without a strong business reason why.