Section 10
Other Functions
RASWIN has additional functions that allow
you to audit your transaction data. These are
mostly found on the AUDIT MENU, which will be available to you
if your security level is high enough to enable this function. The Audit
Menu contains the following options:
Audit Missing Tran Codes
This function checks the transaction codes actually used in your
database against the codes that exist in your
transaction codes
table.
If any are found to be missing, it will provide a list of the
missing codes.
View Filtered Log File
The view log file option displays the current day's log file (or one
for another date) on the screen. The data in the logfile can be helpful in tracing down program errors.
Maintenance Log File Report
This report permits you to request a display of all table
maintenance activity for any specified range of dates. It is not
normally used except when changes made have caused something 'that
used to work to stop working as before due to erroneous settings.
The maintenance log records 'before' and 'after' setting values for
your tables so you can see what the old values were.
Drawer Log View
RASWIN (optionally) logs all non-transaction related drawer opening
activity. When the cashier selects the open drawer option from the
main menu the program makes an entry in the drawer log recording
the date and time, the drawer number, and the register number. When you run
the Drawer Log View report, you specify the range of dates desired and the
program will prepare a list of all the drawer opening for that
period of time.
Note that if the drawer is manually opened (with the drawer key) the
program has no way to know the drawer was opened and does not make
any entry in the
log. Also, there is of course no way to know what the cashier did
when the drawer was opened (e.g., making change, adding funds,
removing funds,
etc.) so the drawer log is of limited value as an auditing
tool.
Audit Receipt Header/Detail/Payments
RASWIN records transaction data into three
separate tables... Receipt HEADERS, DETAILS and PAYMENTS. At a
minimum, a receipt must consist of at least one of each of these
record
types.
For a receipt with multiple line items, there will
be one DETAIL record for each line.
If there are multiple payments, there will be one
record in the PAYMENTS table for each payment.
This Audit function checks to make sure all the proper records are
present and provides a list of any missing records. This can occur
if a transaction is interupted due to a power failure or other program
crash.
Validate Header Totals
Similar to the previous report, this one checks the values
stored in the Receipt Headers to insure that the 'summary'
values stored are valid. For example, the total of each DETAIL
fee, is
summed and
compared to the TOTAL DUE on the receipt HEADER record. If
exceptions are found, they are
corrected. This process can take quite some time if your
database contains lots of records, which a normal production
database will.
Accounting Date Changes (Last 30 Days)
This option permits you to do a quick review of changes to
the accounting date made by your users for the last 30 day
period. You have the option to look at ALL registers, or just a
single
register.
It will not take long to create the report, which you can
view or print, as
required.

In most environments you would expect to have one change
of accounting date per calendar day. Forgetting to change the
accounting date is the
most common error users make, especially when first starting to
use
RASWIN.
Security Matrix
This option permits you to display which reports and
tables a user has access to based on their security
level. It can be run for only one user at a time. The report looks
like this:

For space reasons, the full report is not shown above.
The first portion shows which reports the user is
permitted to run, and the second
section shows which tables they are permitted to maintain (if they
are
allowed to maintain tables at
all).