Many audit solutions require application code in order to detect the change to the data and perform the subsequent write to the audit log. These solutions are expensive in development and future maintenance. Coverage of the audit is rarely 100% as only those transactions that contain the specific code are written to the log.
With the GLOVIA G2 extended ERP system, the audit capability has been moved down to the Oracle database via the use of triggers, thus allowing the changes to the database to be controlled by Oracle instead of the application. Only the net change is written to the database. Writing only changed data ensures that database storage issues are minimized and clarity of the audit inquiry is optimized.
Audit Manager allows a user to define the individual columns from a database table that are to be under audit control. The columns available for selection are those columns that appear both on the SuperLayer file definition and on the Oracle table definition. The user also defines when to track audits, i.e. when a field is inserted, changed, or deleted.
The audit inquiry provides a flexible and powerful inquiry of the audit log. A single generic inquiry has been created that allows the history of changes of any table under audit to be viewed. The data on the inquiry screen, including the associated column names, is pertinent to the table that is under inquiry.
The audit log can be purged by table name and date. Any audit records for the selected table with a change date equal to or older than the selected date will be permanently deleted.
The data elements that are displayed for the audited table are:
You can search the audit log via the following criteria:
Contact FUJITSU GLOVIA to learn more about the audit control capabilities of the GLOVIA G2 extended ERP system.
Copyright 1995 - 2015 FUJITSU