16 | Audit Report Example
The Audit Report is used to view a list of activities that are performed and logged on the system such as edits, adds, deletes, reports, jobs, and errors. This article provides Audit Report examples including flag options, reported columns, and explanations.
The Audit Report is used to view a list of activities that are performed and logged on the system such as edits, adds, deletes, reports, jobs, and errors.
This article provides Audit Report examples including flag options, reported columns, and explanations.
Prerequisites- For an Operator to be able to access and run Audit Reports within BackOffice, the Allow Audit Reports flag within the Reporting tab of Operator Maintenance must first be enabled
- If this flag is not enabled, an Operator cannot access Audit Reports
Report Example
- The below Flag options allow you to pre-filter the Audit report by the Audit Level
- By default, all options are checked excluding the "Include Messages"
- You can filter the Audit Report with a combination of the below flags
Alert Level | Description |
Include Critical Alerts |
Will display Critical Level Alerts in the report |
Include Warning Alerts |
Will display Warning Level Alerts in the report |
Include Information Alerts |
Will display Information Level Alerts in the report |
Include Handheld Alerts |
Will display Handheld Level Alerts in the report |
Include Messages |
Will display Messages Level in the report |
Reported Columns
Column Name |
Description |
AuditID |
Primary Key Field |
VenueID |
|
Venue Name |
|
DateTime |
|
Audit Type |
Bepoz Audit Types |
Level |
|
Operator ID |
|
Operator Name |
|
Workstation ID |
|
Workstation Name |
|
IDA |
ID Value for the reported component |
IDB |
ID Value for the reported component |
IDC |
ID Value for the reported component |
IDD |
ID Value for the reported component |
LDA |
|
LDB |
|
DataA |
Name Value for the reported component |
DataB |
Name Value for the reported component |
DataC |
Name Value for the reported component |
DataD |
Name Value for the reported component |
Calling Method |
Internal code process of how the audit was triggered |
Other Info |
A brief overview of Changes/Events that took place for audit |
DateTime OKed |
Operator Messaging |
OperatorID OKed |
Operator Messaging |
Operator Name OKed |
Operator Messaging |
WorkstationID OKed |
Operator Messaging |
Workstation Name OKed |
Operator Messaging |
Example Detailed Audit View
Example 1:
- In this example, we have an audit for a negative stock on hand for Product Coca Cola Can which has and ProductID of “3493”
- The affected Store is MAC Restaurant$ which has a StoreID of “76”
Example 2:
In this example we can see that the audit contain Other Info, the Product was edited for Product Absolut Vodka Citron 700ML with a ProductID of “3589”
The following alterations were made: Name, LongName, ProductNumber, Comment, Recipe and DocLink