Field Audit Trail Lawson Learning education@lawson.com
Lawson M3 Java Audit Trail A user is maintaining customer master data xxxx xxxx xxxxxx xxxx xxxx xxxxxx xxxx xxxx xxxxxx ‘’ ‘’ ‘’ ‘’ ‘’ ‘’ ‘’ ‘’ ‘’ Customer Master File OCUSMA A user can review audit data on an individual field Database trigger program If an audited field is updated, a trigger program writes an extra record into a separate audit file Audit File in FAT Database Schema When a table is being audited, an additional process occurs at the point when the table is updated. A record containing the record image is written to an audit table created specifically for that audit by the FAT Manager. The FAT audit files are stored in a separate database schema (library) from the main M3 database tables.
Viewing field changes Example with Credit Limit 1 being audited Lawson M3 Java Audit Trail Viewing field changes Example with Credit Limit 1 being audited Press F9 with the cursor in the audited field Pop-up screen shows previous values
Lawson M3 Java Audit Trail Overview Used to display changes that are made in a field update, write, and delete operations can be trailed Primarily an interactive facility, not a reporting base F9 key shows recent changes Shows information on the changes made the user who made the changes the date/time the changes were made Audit trail is available on all fields in any file with a unique key a field xxCHID (“Changed By”) that contains the ID of the user who last changed the record Field audit data tracks changes made inside or outside the Lawson M3 application.
Lawson M3 Java Audit Trail Overview Field auditing begins in the FAT Manager with the creation of an Audit specify the file and fields to be audited specify the events to be audited - add, change, delete The FAT Manager creates the necessary system objects that control auditing audit files, stored in a separate database schema, containing the audited fields (the before image) unique identification of the updated record (key fields) a unique counter for the update the date- & time-stamp of the update the type of update operation (add, change, delete) the name of the user who updated the record
Lawson M3 Java Audit Trail Overview Audit trail data can be viewed in M3 by positioning the cursor in a field and pressing F9 a pop-up list of recent changes is displayed, in most recent first sequence before and after values of the field are shown only the before value is stored in the audit table Audit trail data can also be viewed in the FAT Viewer available only to system administrators iBrix implemented in Workplace used only for exceptional cases difficult to search/sequence the data
Life Cycle Manager or M3 Workplace Lawson M3 Java Audit Trail Java Audit Trail Components M3 BE FATCONF Audit Data FAT Server FATTEST FATLIVE MVXTEST 1 A C B 2 MVXCONF MVXLIVE Life Cycle Manager or M3 Workplace Port 8095 FAT Manager Port 18095 The FAT Manager provides a user interface The FAT Server controls the creation of audit files the creation of database triggers managing queries on audit data The FAT Manager is the user interface, available from the Workplace Administration menu, that communicates with the FAT Server. The FAT Server runs as a job in the M3JVA subsystem on the iSeries. One FAT server is required per environment. The FAT database schemas are created to contain audit files and other metadata objects required by FAT. Port 28095
Lawson M3 Java Audit Trail Process
Starting the FAT Server Lawson M3 Java Audit Trail Starting the FAT Server Ensure the FAT server is started for the environment whose fields are to be audited One FAT server job per M3 environment
Using FAT Manager to Create a New Audit Lawson M3 Java Audit Trail Using FAT Manager to Create a New Audit 1 Choose the System Configuration List of audits 2 Click New List of M3 files 3 Choose the file to be audited
Selecting Fields to be Audited Lawson M3 Java Audit Trail Selecting Fields to be Audited
Audit Status Audits can be activated or deactivated Lawson M3 Java Audit Trail Audit Status Audits can be activated or deactivated the status is shown in the list of current audits Green – active Red - inactive 12
Lawson M3 Java Audit Trail Managing Partitions
FAT audit files reside in the separate database schemas Lawson M3 Java Audit Trail Java Audit Trail Partitions M3 BE M3 Workplace MVXLIVE 1 A C B 2 FAT Server FAT Manager FATLIVE Audit Data MVXCONF 1 A C B 2 FAT Server FATCONF Audit Data MVXTEST 1 A C B 2 FAT Server FAT audit files reside in the separate database schemas FATTEST Audit Data 14
Java Audit Trail Partitions Lawson M3 Java Audit Trail Java Audit Trail Partitions A partition is a separate table containing audit data Each audit file can be separately partitioned manually - when audit information becomes too old automatically – if the audit information changes Old partitions can be deleted manually M3 Workplace FATCONF Customer Credit Limits (OCUSMA) Price List Details (OPRICL) Item Class Details (MITMAS)
Java Audit Trail Partitions Lawson M3 Java Audit Trail Java Audit Trail Partitions M3 Workplace Select the Partitions tab Select the audit file to be partitioned, then click Modify
Java Audit Trail Partitions Lawson M3 Java Audit Trail Java Audit Trail Partitions M3 Workplace Click Manual break New partition (table) is created Size column shows no. of rows in old partition Current partition always shows -1