Corrections
This option is only visible when Corrections is unlocked, and when you have access to the option in your Profile. By default, access is disabled.
Audit Trail
The Audit Trail can be used to track any changes made to certain fields in the Access Accounts database.
Automatic Triggers
To setup an Audit Trigger, select from the left hand side of the window the table on which you want to create the trigger and click Insert.
First, enter a Trigger Name.
The name cannot contain any spaces. If a name with spaces is entered you will be prompted to remove them when you try to save.
Next, select what action it should Trigger On. You can choose to have the trigger execute when data is Inserted, Updated, Deleted or any combination of the three.
Now tick the Field Description within the chosen table which should cause the trigger to execute. To set the fields for the trigger to execute on, tick the appropriate check-box under the Trigger column. If you wish information in other fields to also be written to the Audit Trail table when the trigger executes, tick the check-box in the Show column for appropriate fields.
The Field Description box contains Descriptions of each field, which field is the Primary key, which fields the Trigger is executed on, which fields Show in the table when the trigger is executed, and the Column Name.
For example, when a price or description field has been edited and written to the Audit Trail, it would not necessarily be straightforward to tell which specific record has been changed; however, if the record code was also written to the Audit Trail table it would be easily identifiable.
When you have selected all the required fields, click on OK to save the trigger.
The Show All Tables checkbox shows all the SQL tables that Dimensions uses but it should be noted that if a trigger were to be setup on a transaction table, it could lead to performance degradation and other unforeseen problems.
Reporting
When a change is made, the information is written to a separate SQL table (ARM_CM_CHANGE_LOG) which can then be used for reporting. A Crystal Report is included with the Corrections Module to view this information. It is called 'Changes Log.rpt' and is located in the Reports folder within the Correction Module Core Components installation directory. The Corrections Module also automatically produces an audit trail of any changes it makes which can be viewed with 'Corrections Audit Report.rpt' which is also located in the Reports folder.
If you wish to view either of these reports from within Dimensions copy the file to the module folder you wish to run the report from, within the Access directory.
For example: To show the report in the list of Nominal Ledger reports copy the report file to:
<Access directory>\Access Reports\SQL\Nominal
where <Access directory> is the path to your Access directory e.g. C:\Program Files\Access.
System Settings
This popup controls the various options within Corrections, thus allowing you to customise the feature to work according to your requirements.
Update SME values - To update a linked Service Manager database, check the Update SME Values checkbox and enter the Service Manager database name into the 'SME Database name' field. Corrections will then update the relational Service Manager data when changing such things as customers, projects, cost centres etc.
Prompt for reason when making corrections - this checkbox, when selected, also has an optional 'Reason Mandatory' checkbox. These options can be used to add audit information to any Corrections.