Suggested Files to be Monitored by Audit Master

Audit Master is an invaluable tool for the PSQL database. It helps to answer the question "what happened to my data?"  For example, during day-to-day operation, if someone delete a sales order, you want to know who did it so you can find out why.  Fortunately, Elliott as a Sales Order Line Item to help you.  You can assume the person who deleted the line item is the same person who deleted the order.

However, Elliott does not provide an audit trail for everything. Therefore, when a record, like Notes, is deleted, we have no way of knowing who deleted it and when.  This is where Audit Master will come in handy. Audit Master will also help Netcellent debug many hard-to-find and how-to-diagnose scenarios.  It is an invaluable tool that helps Netcellent support you.

One of the challenges with Audit Master is that it will generate large amount of data.  Each Audit Mater archive file is limited to 1GB. In a larger Elliott installation, this can take less than 1 day to fill up. To reduce the amount of data created by Audit Master, you should not monitor every single Elliott table. Most of the history data has little value for auditing.  For example, there's not much value in auditing invoice-history-related tables since when the records are added to invoice history, there's no user interface to change the record in the invoice history database.  The following are examples of tables that we don't need to monitor:
  • ARDISFIL, APDISFIL, PRDISFIL, IMDISFIL, BMDISFIL - These are module-level G/L distribution tables.  The records in these tables, once created, cannot be changed by the user other than to purge them.
  • GLTRXFIL - G/L Trx File.  Once created, the user can't change it other than to purge it at year end.
  • IMINVTRX - I/M Inventory Trx Audit Trail. Once created, the user can't change it other than to purge it.
  • CPINVHDR, CPINVLIN, ...etc - These are invoice history databases.  Once created, there's no user interface to change them other than to purge them.
  • CPHODHDR, CPHODLIN...etc. - These are order history databases.  Once created, there's no user interface to change them other than to purge them.
  • POORDHDR, POORDLIN - These are purchase order databases. Since we provide full revision history for purchase orders, there's not much value in auditing these two tables.
There are more tables that should not be monitored, than there are tables that should be monitored. Therefore, the purpose of this documentation is to give you a recommended list of tables to monitor with Audit Master. You may add additional tables to monitor to suit your own needs.

General Recommendation

The following is a list of tables we recommend that you monitor in most situations:
  • APTRXFIL - A/P Trx File
  • APTRXDST - A/P Trx Distribution File
  • APVENFIL - A/P Vendor File
  • ARCUSFIL - A/R Customer File
  • CPCUSWLF - COP Customer Wish List File (if you use this feature)
  • CPORDHDR - COP Order Header File
  • CPORDLIN - COP Order Line Item File (add this for "full" auditing)
  • CPORDLS - COP Order Line Item Lot/Serial File
  • CPORDPMT - COP Order Payment File
  • CPSHPFIL - COP Ship To File
  • IMINVLOC - I/M Inventory Location File
  • IMITMFIL - I/M Item Master File
  • IMLSTRXS - I/M Lot Serial Trx File
  • IMTRXFIL - I/M Trx File
  • IMTRXSER - I/M Trx Serial File
  • NOTES - Notes File
  • POWHRECI - PO Warehouse Receiving Item File
  • POWHRECS - PO Warehouse Receiving Serial File
  • SYATTRIB - System Attribute File
  • SYCONTCT - System Contact File
  • SYCONREL - System Contact Relationship File

General Recommendation (Optional)

The following is a list of table that's optional depending on your situation:
  • AROPNFIL - A/R Open Item File: You may want to monitor this file if you need to monitor the users who have access to A/R -> Maintenance -> A/R Open Item File.  It may also be desirable to monitor this file if you use payment window on the COP side and you apply AR payment or credit memo to the order as payment.

WMS (Warehouse Management System) Users

If you use Elliott WMS and Multi-Bin systems, we recommend that you monitor the following additional tables:
  • CPBOXFIL - COP Box FIle (Shipping Verification)
  • CPBOXSER - COP Box Serial File (Shipping Verification)
  • CPBOXSHP - COP Box Ship Item File (Shipping Verification)
  • CPSTGBAT - COP Staging Batch File
  • CPSTGDTL - COP Staging Detail File
  • CPSTGORD - COP Staging Order File
  • CPSTGSER - COP Staging Serial File
  • CPSTGSUM - COP Staging Summary File
  • CPWMSDTL - COP WMS Detail File
  • CPWMSORD - COP WMS Order File
  • IMBINFIL - I/M Bin Master File
  • IMBININV - I/M Bin Inventory File
  • IMBINREF - I/M Bin Reference File
  • IMCNTITM - I/M WMS Physical Count Item File
  • IMCNTSER - I/M WMS Physical Count Serial File
  • IMEQPFIL - I/M Equipment File
  • IMEQPTRX - I/M Equipment Trx File
  • IMTSFTRX - I/M Transfer Transaction File
  • IMTSFSER - I/M Transfer Transaction Serial File
  • IMTSFBAT - I/M Transfer Batch File

ACH (Automatic Clearing House) Users

If you use the Elliott ACH feature, we recommend that you monitor the following additional tables:
  • SYACHACT - System ACH Account File
  • SYACHQUE - System ACH Queue File

Pickup Pending Users

If you are using Elliott Pickup Pending feature, we recommend that you monitor the following additional table:
  • CPPUDELV - COP Pickup Delivery File

EMK

Pervasive PSQL

  1. Btrieve Error Codes 001 - 199
  2. Btrieve Error Codes 3000 - 3099
  3. Btrieve Error Codes 3100 - 3199
  4. PSQL Version Required by Each Elliott Version
  5. Do I Need to Change PSQL Server Engine Default Parameters After Installing It?
  6. New Elliott PSQL Server Processor and RAM Suggestions
  7. Can I Dynamically Adjust Elliott / PSQL 11 Server Memory?
  8. Received "Your Computer Does Not Have PSQL 10 or 11 Client " Even though PSQL Client Is Just Installed
  9. Btrieve Error 161 on Password File When Starting Up Elliott
  10. Problems with Using Pervasive Rebuild Utility on APOPNFIL and AROPNFIL Tables
  11. Security Issue with Installing PSQL Client Remotely on User's Workstation
  12. PSQL and Distributed File System (DFS)
  13. How Do I Turn on PSQL Relational Engine Security?
  14. An Example of Debugging NOTE_ORD_VIEW PSQL Expression Evaluation Error
  15. Btrieve Error 025 on COP Open Order by Salesman Report
  16. What Is the *.^01 File for My PSQL Btrieve Table?
  17. Suggested Files to be Monitored by Audit Master
  18. Pervasive Backup Agent Is Not Compatible with Creating Work Files
  19. Hardware Recommendations for Your PSQL Database Server
  20. How to Optimize SQL SELECT Statement When Retrieving Data from Invoice History
  21. New User-Defined Functions in Elliott DDF
  22. How to Improve Query Performance When Retrieving Data from Notes & Invoice History
  23. How to Retrieve Tracking Number for an Order from Notes
  24. Actian PSQL Not Started Automatically After Server Reboot
  25. Create a New Database in the PCC for Relational Engine Access
  26. Slow PSQL Relational Engine Performance
  27. IPV6 May Cause Problem for PSQL 11 Relational Query

Feedback and Knowledge Base