Audit Logger for Sage 300

Installation and User Guide

2018

© Copyright 2002-2017 Pacific Technology Solutions Limited. All Rights Reserved.

No part of this documentation may be copied, photocopied, reproduced, translated, microfilmed, or otherwise
duplicated on any medium without written consent of Pacific Technology Solutions Limited.

Use of the software programs described herein and this documentation is subject to the Pacific Technology Solutions
Limited Licence Agreement included in this documentation.

All product names referenced herein are trademarks of their respective companies.
End User Licence Agreement

Pacific Technology Solutions Limited

WARNING! PLEASE READ THIS AGREEMENT CAREFULLY BEFORE COMMENCING WITH INSTALLATION OF THE
SOFTWARE. YOUR USE AND/OR INSTALLATION OF THE SOFTWARE WILL INDICATE YOUR ACCEPTANCE OF THE
TERMS AND CONDITIONS OF THIS AGREEMENT. BY CLICKING “I ACCEPT” AT THE END OF THIS AGREEMENT
DURING THE INSTALLATION PROCESS YOU WILL BE DEEMED TO HAVE ACCEPTED THESE TERMS AND
CONDITIONS. IF YOU DO NOT ACCEPT THESE TERMS AND CONDITIONS YOU MUST NOT CLICK “I ACCEPT”
DURING THE INSTALLATION PROCESS AND YOU MUST NOT INSTALL OR USE THE SOFTWARE.

IF THE CUSTOMER IS A COMPANY OR OTHER ORGANISATION, THEN THE PERSON WHO CLICKS “I ACCEPT”
DURING THE INSTALLATION PROCESS CONFIRMS THAT THEY HAVE AUTHORITY TO BIND THE COMPANY OR
ORGANISATION UNDER THIS AGREEMENT AND THAT THE COMPANY OR ORGANISATION ACCEPTS THESE TERMS
AND CONDITIONS.

1 Definitions

In this Agreement:

“Agreement” means this agreement;

“Intellectual Property Rights” means all industrial and intellectual property rights whether conferred by statute,
at common law or in equity, including, but not limited to, all copyright and similar rights which may subsist or may
hereafter subsist in works or other subject matter, rights in relation to inventions (including all patents and patent
applications), trade secrets and know-how, rights in relation to designs (whether or not registrable), rights in relation
to registered and unregistered trade marks, business names and rights in relation to domain names;

“Licence Fees” means all licence fees agreed by the Customer to be paid for the use of the Software;

“Licensor” means Pacific Technology Solutions Limited;

“Customer” means the end user of the Software; and

“Software” means any software provided or made available by the Licensor to the Customer under this Agreement,
including programs, code and screens, on-line or printed documentation and any upgrades, enhancements or similar.

2 Licence

2.1 Subject to the terms and conditions of this Agreement and payment of all applicable Licence Fees, the
Licensor grants to the Customer a limited, non-exclusive, non-sublicensable (except subject to clause 3.3),
non-transferable (except subject to clause 10.1) right to install and use the Software on one network.
Where the Software is licensed on the basis of concurrent or named users, only the licensed number of
concurrent or named users can use the software. Where multiple databases/Companies are operating on
one server, the number of users is the total number across all databases/companies on that server.

2.2 The Customer is entitled to take a reasonable number of copies of the Software for backup or archival
purposes.

2.3 This Agreement extends to any accompanying documentation for the Software. Such documentation may
not be copied, modified, used or distributed in any way not contemplated or expressly authorised by this
Agreement.
3 Restrictions

3.1 The Customer is not entitled to use the Software until all applicable Licence Fees have been paid.

3.2 The Customer may not:

(a) copy or modify the Software, except as expressly permitted by this Agreement; or
(b) decompile, reverse engineer, translate, adapt, vary, modify, distribute or publish the Software.

3.3 The Customer may not permit any other person to benefit from the use or functionality of the Software
either directly or indirectly unless:

(a) the Customer is a company and the other person is a subsidiary of the Customer. For the purposes of this
clause 3.3(a), “subsidiary” shall have the meaning set out in Sections 5 and 6 of the Companies Act 1993
(New Zealand); or
(b) the Customer is not a company and the other person is a company in which the Customer owns more than
50% of the voting shares and is in a position to control the composition of the board.

4 Ownership, Title and Intellectual Property Rights

4.1 The Software is a proprietary product of the Licensor and is protected by copyright and other laws. All
Intellectual Property Rights in the Software belong exclusively to the Licensor or its licensors. Ownership of
all Intellectual Property Rights in any modifications or enhancements in the Software (whether undertaken
by the Licensor or the Customer and whether or not they are authorised by the Licensor) shall remain with
the Licensor or its licensors, and to the extent such ownership does not automatically vest in the Licensor or
its licensors on creation, the Customer shall perform all acts and sign all documents required by the Licensor
to vest such ownership in the Licensor or its licensors (as the case may be).

4.2 The Customer shall:

(a) at all times ensure the non-disclosure and confidentiality of the Software and all matters relating thereto;
(b) ensure that its officers, employees and agents are aware of the terms of this Agreement and do not except
as otherwise permitted in this Agreement, disclose, communicate or copy for any purpose whatsoever the
Software or any part thereof to any third party. The Customer accepts liability for any such disclosure,
communication or copying by its officers, employees and agents;
(c) maintain all copyright notices on all copies of the Software; and
(d) notify the Licensor immediately upon becoming aware that any person may have unauthorised knowledge,
possession or use of the Software or any part of it.

5 No Warranty

5.1 Except as set out in this Agreement, the Licensor provides the Software “as is” and does not warrant that it
is error free. All warranties, terms and conditions in respect of the Software (including without limitation,
warranties and conditions as to fitness for purpose and merchantability), whether express or implied by
statute, common law or otherwise are excluded from this Agreement to the fullest extent permitted by law.
5.2 The Licensor does not warrant that the Software will meet the Customer’s requirements. The Customer is
responsible for ensuring that the Software meets its requirements prior to using or installing the Software.

5.3 The Licensor shall not be bound by or liable to the Customer for any representations or warranties made by
any third party in relation to the Software.
6 Limitation of Remedies and Liability

6.1 THE LICENSOR ACCEPTS NO LIABILITY FOR ANY DAMAGE OR LOSS OF ANY KIND, DIRECT OR INDIRECT,
ARISING UNDER THIS AGREEMENT OR FROM THE USE OF THE SOFTWARE, INCLUDING CONSEQUENTIAL
DAMAGES, DAMAGES FOR LOST INFORMATION, BUSINESS INTERRUPTION, OR LOSS OF PROFITS.

6.2 In the event that the above exclusion of liability is held to be invalid in whole or in part, then the Licensor’s
maximum liability under this Agreement or arising from the Customer’s or any permitted sub-licensee’s use
of the Software shall be limited to the Licence Fees paid by the Customer for the Software.

7 Term

7.1 This Agreement shall remain in force until terminated by either party under clause 8.

8 Termination of Agreement

8.1 The Customer may terminate this Agreement at any time by giving written notice to the Licensor.

8.2 The Licensor may terminate this Agreement at any time by giving the Customer written notice if the
Customer fails to comply with any term of this Agreement. Termination by the Licensor shall be without
prejudice to any other rights or remedies available to the Licensor in existence as at the date of termination.

8.3 Upon termination of this Agreement by either party, the Customer shall immediately:

(a) cease to use the Software;

(b) destroy the Software and all copies of it in its possession;
(c) destroy all accompanying documentation for the Software and all copies of it in its possession; and
(d) provide the Licensor with a certificate in a form acceptable to the Licensor that the Customer has done so.

8.4 Clauses 4.1, 4.2(a) and (b), 5, 6 and 8.3 will survive termination of this Agreement.

9 Software Assurance

9.1 The Licensor shall provide as from the date of purchase of the Software a software assurance service for the
Software which entitles the Customer to receive all standard software upgrades made available by the
Licensor to its customers in relation to the Software (“Software Assurance Service”). The Software
Assurance Service will be provided on a 12-monthly basis, with the first 12 month period commencing on
the date of purchase of the Software. Either party may terminate the Software Assurance Service with effect
from and only from the end of any 12 month period by giving prior written notice to the other.

9.2 The Licensor shall charge a fee for the Software Assurance Service for each 12 month period of a sum equal
to 18% of the Licensor’s standard retail price for the Software (exclusive of GST) as at the date of purchase,
excluding any special discounts, bulk purchases or promotional pricing, plus GST (if any). The fee for the
Software Assurance Service will be paid by the Customer prior to the commencement of each 12 month
Software Assurance Service period, upon receipt of the invoice for such fee.

9.3 The Licensor does not warrant that any minimum number of software upgrades will be provided as part of
the Software Assurance Service. No other support, maintenance or error-correction services shall be
provided by the Licensor unless agreed by the parties in writing.

9.4 If the Customer wishes to reinstate the Software Assurance Service following its termination by the
Customer, then the Customer may do so subject to payment of a reinstatement fee to be determined by the
Licensor.
10 Assignment

10.1 The Customer may assign or transfer this Agreement to another person only if the following conditions are
met:

(a) the other person agrees in writing with the Licensor to accept the terms and conditions of this Agreement;
(b) the Licensor consents in writing to the assignment or transfer; and
(c) the Customer removes the Software executables and licence files from the Customer’s network and
computers immediately following the transfer or assignment.

11 General

11.1 This Agreement shall be governed by and construed in accordance with the laws of New Zealand and the
parties submit to the non-exclusive jurisdiction of the New Zealand courts.

11.2 This Agreement embodies the entire understanding of the parties relating to the matters referred to and
supersedes all other agreements and representations made by the parties whether oral or written.

11.3 If any provision of this Agreement is found to be invalid or unenforceable, the remaining provisions will
continue in full force and effect.

11.4 Failure or neglect of the Licensor to enforce any provision of this Agreement at any time shall not be
construed or deemed to be a waiver of its rights and shall not in any way affect the validity of this
Agreement or any of its provisions nor prejudice the Licensor’s right to take subsequent action.

11.5 All modifications to or variations of this Agreement must be in writing and signed by both parties.
Table of Contents

1. Introducing Audit Logger ................................................................................................... 2

2. Getting Started ................................................................................................................... 3
2.1 Before You Start ........................................................................................................ 3
2.2 Installation................................................................................................................ 3
2.3 Activation ................................................................................................................. 3
3. What You Need to Know Before Setting Up Audit Logger ................................................. 4
3.1 Data Storage ............................................................................................................. 4
3.2 Performance ............................................................................................................. 4
3.3 Ensuring That User/Security Data Is Set Up Correctly ................................................... 4
4. Maintaining Setup Information .......................................................................................... 5
4.1 Changing Setup Options ............................................................................................. 5
4.2 Testing ..................................................................................................................... 7
5. Processing ........................................................................................................................... 8
6. Reports 9
6.1 Audit Log Report ....................................................................................................... 9
6.2 Exporting to Excel ..................................................................................................... 9
7. Audit Log Inquiry .............................................................................................................. 10
8. Document History ............................................................................................................. 12
9. Purging Data ..................................................................................................................... 13
Appendix A - Audit Logger Demo product .............................................................................. 14
Appendix B - Contact Information .......................................................................................... 15

Audit Logger 2018 Page 1

User Guide
1. Introducing Audit Logger

Audit Logger is a module that tracks changes to Sage 300 data.

Because Audit Logger is developed completely in the Sage 300 Software Development Kit (SDK), it has
major benefits over a database-level approach, such as:

 functioning smoothly for operations such as Database Dumps and Database Loads
 ability to log deletion of records
 is aware of many Sage 300 internal functions – one example of where this is advantageous is that it
does not audit calculated fields unless explicitly requested
 is durable through database schematic changes
 is web-deployable

Audit Logger 2018 tracks changes on the following modules:

 System Manager
 Administration Services
 Bank Services
 Common Services
 Tax Services
 General Ledger
 Accounts Receivable
 Accounts Payable
 Inventory Control
 Order Entry
 Canadian Payroll
 US Payroll
 Audit Logger

Audit Logger 2018 Page 2

User Guide
2. Getting Started

The steps required to implement Audit Logger are as follows:

 installation
 testing

Each of these areas is covered in the following sections - failure to adhere to the instructions could cause
problems with the installation or operation of the software.

2.1 Before You Start

Audit Logger 2018 requires Version 2018 of the following modules: System Manager.

2.2 Installation

To start the installation process, run the installer downloaded from the web site. This process will install the
required files into the Sage 300 application directory called AU65A.

If the site has Accpac programs installed on each PC, then Audit Logger needs to be installed on each PC
also.

2.3 Activation

Follow the standard Sage 300 activation procedures for Audit Logger, this will initialise the Company desktop
with the icons available for running Audit Logger.

A group “Audit Logger” is created in the Administrative Services folder.

Activation also creates and seeds the required tables in the company database.

Audit Logger 2018 Page 3

User Guide
3. What You Need to Know Before Setting Up Audit Logger

3.1 Data Storage

As Audit logger can potentially store a large amount of data, it has been developed in a way that stores data
efficiently – data is stored in binary format.

3.2 Performance

As with all auditing functions, Audit Logger has an affect on performance. The more fields that are audited
the more affect there will be on the performance of Sage 300.

3.3 Ensuring That User/Security Data Is Set Up Correctly

Audit Logger uses the same security approach as standard Sage 300 modules, so the security rights for
Audit Logger need to be determined.

Audit Logger 2018 Page 4

User Guide
4. Maintaining Setup Information

After the software has been successfully installed, it needs to be configured to operate in the way that the
site requires it to operate, i.e. determining the correct settings for the setup parameters based on the site’s
requirements, and entering the settings in the Setup program. We recommend that the Sage 300 dealer
carries out this step.

4.1 Changing Setup Options

Audit Logger is created as a new folder in the Sage 300 Administrative Services folder.

Go into the Setup program.

For each of the modules that are activated and can be audited, the views available for auditing are listed
(refer screenshot below).

View Selection

Select the view that is to have fields audited.

Module Audit Level Audit Logger comes with pre-set options for Low and High audit levels. If you
use either of these options, we strongly recommend that you review the fields
that are being audited, both to ensure they cover the fields you want, and also
that the effect on performance is not overly adverse.

If any of the field audit settings are changed from the Low or High settings, then
the Module audit level is set to Custom.
Audit Logger 2018 Page 5
User Guide
Field Selection

When a view is selected, all the fields in the view are presented, as shown in the screenshot below.

For each field that is to be audited, double-click in the Field Use column to turn on or turn off the auditing
function.

Field Use

Key Key fields are always logged if a trigger field triggers an audit record

Trigger Audit Most fields can be set to Trigger Audit – this means that if that field is changed
then an audit record is created

Calculated Fields Calculated fields are fields that are maintained by Accpac processes as opposed
to by users – and they cannot be set as trigger fields. However these fields can

Audit Logger 2018 Page 6

User Guide
 be set to Record, which means when an audit record is created, the values of
these fields will be stored as part of the audit record.

Optional Fields

For views that have Optional Fields that are covered by Audit Logger, there are options to handle the
various levels of auditing of changes to the optional fields. This audit information is stored with the “parent”
record that it relates to, even though the Optional Field data is held in a different Accpac view.

4.2 Testing

After Audit Logger has been installed, it should be tested to ensure that the software is functioning
correctly. We suggest that this is done by processing some test transactions through a Test database.

Audit Logger 2018 Page 7

User Guide
5. Processing

Audit Logger operates as a background function, so that whenever the nominated views and fields are
changed the changes are logged.

Audit Logger does not have any processing functions of its own.

Audit Logger stamps each audit record with a sequential number, providing a check that the audit record
sequence is intact.

Audit Logger 2018 Page 8

User Guide
6. Reports

6.1 Audit Log Report

Report File Select the report file that you wish your results to be printed to

From/To Date Enter the data range for the audit records

Filter Users Leave unchecked to report audit records for all users. You can filter the users
that you want results for by clicking on the zoom button. Note that you will
only see users for whom an audit record has been created

Filter Views Leave unchecked to report audit records for all views. You can filter the views that you
want results for by clicking on the zoom button

Operations Tick the audit operations that you want to print

Show Changed Fields Only This option allows you to just report on the fields that have been changed –
otherwise the before and after values for all audited fields are reported

6.2 Exporting to Excel

It is often useful to be able to export audit data, to search for specific data. This function is provided from
the Report screen by clicking on the ‘Export’ button.

Audit Logger 2018 Page 9

User Guide
7. Audit Log Inquiry

The Audit Log Inquiry screen allows you to inquire on views and users for which audit log records
have been created.

From/To Date To specify a date range

Filter Users Leave unchecked to display audit records for all users. You can filter the users that you
want results for by clicking on the zoom button. Note that you will only see users for
whom an audit record has been created

Filter Views Leave unchecked to display audit records for all views. You can filter the views that
you want results for by clicking on the zoom button.

Operations Tick the audit operations that you want to print

Audit Logger 2018 Page 10

User Guide
Clicking on the ‘Details’ button will show you the individual field details.

Audit Logger 2018 Page 11

User Guide
8. Document History

The Document History screen allows you view the entire change log history for a specific view
and record within that view.

View Select the view that you wish to inquire on

Key Field Depending on the view selected, the next field's caption will change to the name of
the primary key field. Use the finder to select the record of interest

From/To Date To specify a date range

Operations Tick the audit operations to be included in the report

The ‘Details’ button will show the field details of the selected record.

Audit Logger 2018 Page 12

User Guide
9. Purging Data

This function allows old audit data to be removed from the system.

The Purge process does not purge audit log events related to the Audit Logger module.

Note that while the purge process is proceeding the tables being purged will be locked. This means that
you will not be able to log new transactions at the same time as data is being purged. This process should
therefore be carried out when all other users are logged out of Sage 300.

Audit Logger 2018 Page 13

User Guide
Appendix A - Audit Logger Demo product

Audit Logger has full functionality for the SAMINC and SAMLTD databases. If you have purchased the
Product for use, the activation codes must be entered before the product will run on production company
databases.

Audit Logger 2018 Page 14

User Guide
Appendix B - Contact Information

For any questions about the Audit Logger for Sage 300 product, please contact:

Pacific Technology Solutions Limited

PO Box 175
Hamilton
New Zealand

E-mail: info@pacifictechsol.com
Ph: +64-7-839-2290
Fax: +64-7-839-2230

www.pacifictechsol.com

To find out about other great Sage 300 add-on products that are available from Pacific Technology
Solutions, please visit our web site.

If you believe that there are areas where we can improve Audit Logger product can be improved or suit
your business better, please advise us by e-mail: accpacsupport@pacifictechsol.com .

Audit Logger 2018 Page 15

User Guide