Often times enterprise users want to be able to keep track of audit trail. They want to be able to find out the time and date of a record has been modified, and the name of the user who modified it. This feature can be implemented as a separate module. This function should be implemented in a document and master record (Accpac objects) oriented approach. e.g. track changes by Invoices, Orders, Customer records...
by: Guillermo T. | over a year ago | Setup / Environment
Comments
There are 3rd party apps that do this, I believe. Might be something to look at bringing in house.
I agree, during db dumps and loads, audit tracking details of user date and time get replaced. Keep original data. I don't know why we need a 3rd party app. to do this.
Should be built in automatically across all tables.
Use Audit Logger from Pacific Technology solutions.It works really well. (maybe Accpac should OEM it)
Given that there is a third party app that does this already, I vote to fix or add other features before this.
Isn't the "A" in the original Accpac acronym for "Audit"?
Also Acctech Systems in South Africa have Audit Trails program at www.acctech.biz
Use Audit Logger. It works.
Besides the problem do Dump and Load replacing the data there is another problem: printing a document (Sales Order, Purchase Order, etc.) replaces the audit data with the date of the printing. If this information is valuable, then the printing date and time should have their own columnas
In the Accpac audit trails is very poor and is's very dificult to tracks also. Sometime cannot tracks also. I hope Accpac will include complete auit trail in the future version ( Accpac 6.0)
In the Accpac audit trails is very poor and is's very dificult to tracks also. Sometime cannot tracks also. I hope Accpac will include complete auit trail in the future version ( Accpac 6.0)
An absolute essential
Third party does it well but it is becoming a core requirement where it impacts on cost consideration.
Yes, Essential
My company is considering throwing out Sage Accpac for the specific reason that there is no Audit trials. In terms of compliance and governance
any ERP system should have Audit trials.
I know there is 3rd Party software but it is mostly developed using trigger functionality within in SQL and that impacts the performance of the system to such a degree that the option is not viable.
The audit trail should form an integral/core part of the the Sage 300 ERP software, not a 3rd party application.
Third-party products are great but they aren't allowed in Sage's hosted environment. Audit trails really need to be part of the product as they are requested more frequently by auditors. There is a start with Entered By fields in some areas but these are lacking at GL level and there is no Posted by. Last Audit User could be someone who printed the batch or posting.
Hi Mike F, just saw your old comment 'Isn't the "A" in the original Accpac acronym for "Audit"?'
Nope. Its :
A Complete and Comprehensive Program for Accounting Control.
Kid you not.
Audit function should be in build, all the other ERP's have it in built. Yet another area where Accpac is letting it's customers down. Why should we spend extra on lessor quality 3rd party apps when we pay enough money for accpac licences/maintenance!!!!!
I imagine Sage will be letting AccPac die off instead of a re-write as it definitely lacking in modern accounting functionality, but if for some reason the developers are working on Sage 300, Auditing is a core requirement of any ERP worth its salt.
In addition to having an audit trail it would also be helpful if the feature included selecting which transactions/master data changes require an audit trail and for what time frame.