|
|
 |
|
 |
|
|
|
|
| |
The Auditing module
allows for specific events to be audited by recording information
relating to these events whenever they occur. Generally, these events
are database updates, additions, or deletions from a particular table.
Users can configure which parts of the database
should be audited, including specific row and column information or
just the event itself.
An example might be price overrides in sales order entry where it's
important not just to track the event but also record the order number,
product, overridden price, user who made the change and the
date/time. Event
notes and free-format text can be entered for the events when they
occur. Audited events are captured and written to a separate Auditing
Database that can be interrogated by table and event-driven enquiry
and reporting options.
User-based security within Enterprise allows individual organisations
to define the level of security they require over their database.
Security can be defined by individual users, or groups of users, and
can be controlled to allow for database maintenance, viewing or reporting.
Users can specify from a range of tables (account codes, costs centres,
revenue and expense codes) for particular Enterprise options that
require security access checking, and ranges of either valid or invalid
values for particular columns on these tables.
|
|
|
User-defined auditing
- Event tracking
- Audit analysis |
|
|
|
|
|
User-defined security control
- GL account and posting codes
- GL cost centres
- GL hierarchy codes
- Expense and revenue codes
- Special report codes |
Return to Modules
page
|
|
|
|
|
|
|
|
