Beruflich Dokumente
Kultur Dokumente
User manual
1991-2016
http://www.cardware.rs
e-mail: podrska@cardware.rs
Tel: +381 21 443-516, +381 21 443-265
Josifa Marinkovića 44, Novi Sad
Summary
1 Introduction ........................................................................................................................... 1
Unlimited types of schedules (fixed single, fixed dual, flexi-time, part-time, shifts, overtime, etc. ...)
Unlimited number of presence types that can be measured and reported
Unlimited number of events can be recorded via the program
Evidenting absences and vacations
Separating clocked physical presence into various presence-types (the program differentiates day shifts
from night shifts, regular hours from overtime etc.)
Two-tier client-server architecture (the server is Microsoft SQL Server i.e. SQL Express)
KatzeReports works with all CardWare S-8x T&A and access controllers with iButtons or RF tags as ID badges.
The installation of KatzeReports7 is detailed in the section Installing KatzeReports in the Annex.
1
depending on the PC and domain name . The saved file i.e. the registration request should be sent to by email
to licenca@cardware.rs. You will shortly receive a key file (kr7key file). This file needs to be copied into the
application folder (by default, this is C:\Program Files\CardWare\KatzeReports7) Fig 2.1-2. The key file is valid
only for the PC where the request file was made.
2.2 Datebase
When first starting the program, a dialogue will appear stating that a database hasn't been selected (Fig. 2.2-1),
then a dialogue for database selection (Fig. 2.2-2).
The procedure for
creating and initialising
the database is explained
the Annex, in
KatzeReports installation.
Database selection
means: Fig. 2.1-3 Fig.
2.1-4 Fig. 2.2-1
Server: a list of found local SQL/MSDE servers is offered,
but manual entry of a server is also possible.
User name: User name for accessing the SQL Server.
Default: cardware. Fig. 2.2-1
Password: Password for accessing the SQL Server.
Default: cardware.
Database: select the database from a list in the combo-box.
Manual entry also allowed. Fig. 2.2-2
If connection to the database is successful, clicking on the Test button will show a connection message. If not,
an error message will be shown.. Fig. 2.2-2
2.3 Logging in
When the database has been selected, a window appears
for entering the user name and password to log into the
program. The default user name is administrator and there is
no password (Fig. 2.3-1). Clicking on Cancel will abort the
program.Clicking on OK, if the user name/password
combination is incorrect will show the warning in Fig. 2.3-2,
and if it's correct the KatzeReports7 program starts.
Fig. 2.3-1
2
Information on the program version, used database name and registration data can be seen in Help/About.
3.2 Users
Several users with varying authorisation levels can use the program. Each user is given a user name, password
and authorisation type. The menu option File/Users opens the window of Fig. 3.2-1.
Here you can see a
table of all user
names, passwords
and authorisation
types. New users
can be added and
deleted here, and
changes can be
made by typing
directly into the
fields.
A user can be
assigned seven
levels of
authorisation:
Administrator,
Operator,
Department–
operator, Guest,
Department–guest,
Zone-
Administrator-zone
and Zone-operator. Fig. 3.2-1
Administrator has two application authorities: viewing and saving of all data and reports and their editing.
Operators, as opposed to administrators, can't do a backup of clocking data, nor change employee data.
Department-operator has the same privileges as an operator but can only access data of the department
assigned to them in the Department column.
Users logged in as Guests can only create reports. Department-Guests can only create reports with data of the
department assigned to them in the Department column.
Zone-administrators can only see their own reports, as all other users. Apart from this, they can add, delete and
edit employee data and assign employees to zones.
Zone-operators can also see their own reports. Apart from this, they can change PIN codes assign employees
to zones. They can't change any other data.
Checking the check-box in the Calculation column, the user is granted the right to start calculations.
Clicking on the √ button will save the change and clicking on the X button will discard it. Clicking on Accept
saves all changes made, while clicking on Cancel discards them all even if they were saved with the √ button..
3
3.3.2 Groups
As opposed to
departments,
creating employee
groups based on a
chosen criterion is
not compulsory, nor
is it necessary to
choose a group
when entering a
new employee. This
option enables
grouping employees
based on arbitrary
criteria and
facilitates
organisation and
viewing report data.
The dialogue for
entering groups is
shown in Fig. 3.3.2-
1. The upper table is
for goups entered in
the usual way, with
the + button. Delete
a group with the - button. Fig. 3.3.1-1
The lower table is used to add employees to
the selected group in the top table. When
you click on the + button, a dialogue with the
list of all employees opens (Fig. 3.3.2-2).
This dialogue contains various options for
quick selection of employees.
The data in the employees table can be
grouped by the desired column. So, if you
need to assign a few departments to a
group, you can 'extract' the Department
column and the data will be grouped by
sector.
Multiple selection is also enabled by Ctrl or
Shift, as is right-clicking with the mouse. The
drop-down menu otpions are like Fig. 3.3.2-
2.
3.3.3 Towns
Places of residence are not compulsory
data. If you need to enter places of
residence for employees, a list of all
selectable places must be made. We get
this list by Employees/Towns in the dialogue
of Fig. 3.3.3-1. New towns can be added
(click on the + and fill in the fields) and
deleted (by the - button).
4
3.3.5 Adding employees
If employees are not available for import from another database, they must be entered manually. Selecting
Employees/New
employee shows the
dialogue for adding
employees of Fig.
3.3.5-1. ID, department,
surname and name are
compulsory, the rest
(place, address...) is
optional. A PIN is
entered if access
control with PIN
keyboards is used.
Employees can be
assigned photographs
(.jpg or .bmp format) by
clicking on Set (right
part of the screen). The
photo size will be
adapted automatically.
Clicking on OK saves
the entered data.
A review of general
employee data can be
seen by clicking on the
Data tab on the right
side of the main
program window. Fig. 3.3.2-2
5
3.3.7 Importing employees
If employee data already exists (name,
surname, department, mediaID) in any
type of database supported by ODBC and
OLE DB drijvers on the PC, choosing the
Fig. 3.3.7-2
File/Import/Import employees from
database option starts the import wizard.
Click on Next on the starting page like Fig.
3.3.7-1. Clicking on Select opens the
database selection window (Fig. 3.3.7-2).
To import data from another
KatzeReports7 database, select Microsoft
OLE DB Fig. 3.3.7-5
Provider for SQL Server and click on Next.
The dialogue of Fig.3.3.7-3 opens. Enter
or select the PC which hosts the
SQLServer/MSDE with the KatzeReports7
database in the Select or enter a server
name tield. In Enter information to log on
to the server, select Use Windows NT
integrated security. In Select the database Fig. 3.3.5-1
on the server you need to select or enter the name of the database
used by KatzeReports7. Then click on OK. The method is similar for
importing data from a user database, but the provider selection must
be appropriate for the database in question. When the source
database has been selected, click on Next. What follows are the
dialogues for selecting departments, employees, employee
department membership (optional) and mediaID codes issued to
employees (optional). The selection of tables and fields for importing
employees from another KatzeReports7 database is shown
sequentially in Figs. 3.3.7-4, 3.3.7-5, 3.3.7-6and 3.3.7-7. The
Dialogue for starting the import procedure is the last one and here
you just need to click on Import.
If the employee data was generated by the IDInput program, importing Fig. 3.3.6-1
is done with File/Import/Import employees from ID input file which will
start the necessary wizard. The wizard will ask for the usual file selection and the selection of the source .idi file
and, finally click on Import.
Fig. 3.3.7-1
Fig. 3.3.7-2
6
Fig. 3.3.7-4
Fig. 3.3.7-3
Fig. 3.3.7-5
Fig. 3.3.7-6
7
Data in the employee
table can be grouped
by dragging the
desired grouping
column onto the grey
area appearing
above the table when
Employees/Grouping
field is selected.
The employees view
is refreshed by
Employees/Refresh.
3.3.11 Exporting
to Excel
If it's necessary to
export data from the
employees table Fig. 3.3.10-1
(only displayed
columns) into an Excel Fig. 3.3.8-1
file (.xls), the menu item
Employees/Excel opens a dialogue which does this.
3.4.1 Controllers
Choosing Configuration/Controllers will show a window (Fig. 3.4.1-1) with a list of controllers. Each controller in
the system must have a different ID, which is set by a DIP switch on the board. ID codes can be 00 to 63. This
window enables the addition, deletion and editing of controllers.
When adding, the
following fields
must be filled:
ID - controller
ID can be seen
on the
controller itself
(DIP, LCD) or
from Fig.
3.4.1-1.
CommService
aplication (last
part of clocking
record or from
controller
Status. See
CommService
manual for
details;
Description –
description/name of controller; Fig. 3.4.1-1
8
Type – choose one of the offered types of controller in the combo-
box;
Address – name or IP address of the PC hosting CommService;
IP Port – IP port of the PC hosting CommService;
9
3.4.5 Event code association history
Configuration/Event
Codes Association
History opens the
window of Fig. 3.4.5-1.
When an employee
clocking occurs on a
controller, the program
knows which activity to
choose based on the
Event Code and the
Controller ID. This
window defines the
connection between
controllers, event codes
and activities. It's
possible do define time
spans when a certain
controller, event code
combination produces
one or the other activity.
This means that you
can e.g. use a single
reader to generate In
clockings in the
morning and Out clockings in the afternoon, Fig. 3.4.5-1
but it's best not to do this and keep the
reader function the same all day.
This event code/activity association has
to be done for all controllers used in the
company. Fig. 3.4.5-1
The window (Fig. 3.4.5-1) is divided into
three parts. The left part is used to
enter all the doors where clocking
occurs (ID and name). The upper right
part is (for a selected door) for entering
the associated controllers, event codes
and the starting date of validity.
There's also a PIN checkbox and a Bit
column whose function is linked to
access control, if used. The lower right
table is used to associate one or more
activities to a selected controller and Fig. 3.4.6-1
event code. Enter time span, activity name
and visibilty.Checking the Invisible
checkbox means that the activity will not
be included in the T&A calculations.
10
3.4.7 KatzeEvents SL-53
Configuration/KatzeEvents SL-53 is the same as the previous option, but for the SL-53 devices (Fig. 3.4.7-1).
11
1. Employee – this table shows access rules from an employee perspective. Selecting an employee in the
right-side table will show which zones he/she may enter. If the employee is red, no access is granted to
any zone.
2. Zone – this table shows access rules from a zone perspective. Selecting a zone in the right-side table
will show which employees have access rights to the selected zone.
3. Overview – tab enables creating a report of ZONES <-> EMPLOYEES relationship
4. Details – tab shows a table containing data on which employees will be written to which controller (this
tab is needed only for tech support and debugging in case the system doesn't allow access in desired
manner).
5. Changes – a list of records that should be added or removed. These are the changes that are
necessary due to operator-entered changes in the access rules, but have not yet been uploaded to the
controllers. If this window is empty, no uploading is necessary.
Fig. 3.5.2-1
3.6 Clockings
Employee clockings can be made in two ways: with their ID badges on readers and manually - in KatzeReports.
With the Employee/Clockings menu option, you can manually add, delete or edit clockings. These options are
also availabIe by right-clicking on the clockings pane (lower part of main window). The clocking options will now
be explained.
12
Fig. 3.5.3-1
Fig. 3.5.3-2
13
Fig. 3.5.3-3
14
columns for detailed
clocking information. If
the user wants more than
the standard clocking
columns, e.g. the day-
type when the clocking
was made, clicking on
Fig. 3.6.3-1
the Day column and
dragging it to the clocking
table's header will
achieve this.
Clockings/Grouping field
enables clocking data to
be grouped by a certain
criterium set by the user.
Setting the criterium is
done by dragging the
desired grouping column
to the grey area above
the clocking window.
Clockings/Refresh refreshes Fig. 3.6.3-1 Fig. 3.6.5-1
the clockings list with any newly arrived
ones.ig. 3.6.2-1
3.7.1 Employees
Reports/Employees opens a window
(Fig.3.7.1-1) for creating a report of
employees. Choose who the report
should encompass by clicking on the
appropriate radio button. The next
window appears for employees (Fig.
3.7.1-2) and departments (Fig. 3.7.1-
3). Click on Show to create the
report.
The Custom report checkbox
enables the loading (... button) of a
report other than the default one.
Fig. 3.7.1-1
15
Fig. 3.7.1-2
3.7.4 By readers
This option creates reports that show the clockings made by employees on a selection of readers for a selected
timespan. To make a report like this, the following must be done (Fig. 3.7.4-1):
16
Fig. 3.7.2-1 Fig. 3.7.3-1
3.7.5 By doors
This creates reports that show
clockings by selected doors. As with
the previous reports, apart from the
doors, you must select employees,
departments ot the whole company,
the interval and activities to be
shown in the report (Fig. 3.7.5-1).
17
the previous ones. You need to select
a time interval.
Grouping defines the hierarchy of the
displayed data:
- Departments – displays employees
grouped by departments and their
assigned day-types;
- Day types – dates, employees – day
types are at the top of the hierarchy,
sorted by date, then for each day-type
are listed all the employees who have
that day-type;
- Day types – employees, dates –
employees are at the top, and for
each date, the day-type of the
employee is shown.
Refresh day types – this check-box
must be checked when a change
occurs in the calendars, e.g. an
employee is on sick-leave (he has
been assigned an exception in his
calendar)..
Summary – if this box is checked, the
reports don't contain a time-sorted list
based on the selected grouping,
instead of this a sum of categories is
displayed. E.g. if By day types –
dates, employees is selected, then Fig. 3.7.5-1
instead of chronologically displaying
the dates on which the employee
works by that day type, only the total
number of days in the interval, on
which
he/she works by that day type is
displayed.
Clicking on Show opens the report in
a new window, Cancel closes the
window.
3.8 Calendar
configuration
The most important feature of
KatzeReports is its universal
configurability. This means that any
company can use the program and
the implementation of the company's Fig. 3.7.6-1
T&A rules can be adapted to by
configuring the program. The configuration is done on the basis of CardWare's questionnaire and is usually
ready by the time of installation, but later corrections and alterations are possible.
The Configuration option editing of the configuration as well as saving, reading and sending configurations. To
understand the configuration of KatzeReports, please see the Annex to get acquainted with the terms used in
these menu items.
18
state is defined by a starting activity, Calendar in and
an ending activity, Calendar out. A pair of real activities
define R-states. E.g. the R-state presence starts with
the R-activity In and ends with Out.
There is a special kind of K-state, so called markers,
which are used to define daily work obligations for an
employee (more on markers in the Annex). For
example, the marker EO8 is for defining a daily
obligation of 8 hours.
The window of Fig. 3.8.1-1 shows a list of all states
with their starting and ending activities.
States can be added and deleted as described in
previous sections.
19
Click on the + button in the upper part of the window and write the name of the new RxK state in the
Interpretation field. Click on √.
Now click on + in the lower pane and select the desired K-
state for Expected (K-state) and R-state for Clocked (R-
state) from the list of defined presence/absence types (see
previous section). Starting and ending activities are
optional, but sometimes necessary to distinguish between
similar RxK states as we saw in the example. Click on √,
then on OK.
Deleting RxK-states is possible in the following way: select
the RxK-state we want to delete and click on -. Editing is
done in a similar way; choose an RxK state and change
the data. After making the changes, click on √. If it's
necessary to cancel any changes and adding, click on X.
3.8.3 Attributes
Attributes (Fig. 3.8.3-1) to distinguish between certain
parts of the day or days of week (e.g. night, morning,
satruday). Adding, changing and deleting is done in the
usual way.
Attributes are used for more detailed calculations of work time. Fig. 3.8.3-1
3.8.4 Qualifiers
Qualifiers (Fig.
3.8.4-1) are used
for more detailed
calculations of work
time types such as
night work,
tardiness in the
morning, overtime
on Saturdays etc.
Qualifiers get
associated
attributes, which
describe certain
time periods. E.g.
the qualifier
day/night is divided
into three
attributes: 00:00-
06:00 is the
attribute night,
06:00-22:00 is the
attribute day and
22:00-00:00 is
again the attribute
night. The fields
From and To
denote the dates
between which the
qualifier will be
valid. Fig. 3.8.4-1
Using this qualifier, any type of working time can be calculated with day/night distinction e.g. night overtime, day
tardiness etc. Qualifier definitions have a global scope and don't depend on the employee calendars.
20
Fig. 3.8.5-1
3.8.6 Orders
The program calculates working hours using accounts and orders. E.g. if we want to calculate how late
employees were (in minutes), for a given interval (say one day), we need to create an order, which will be called
late arrival and which will transfer all data (minutes) from the RxK state late arrival into the Tardiness account
Fig. 3.8.6-1
21
(see next section for Accounts). Data from the RxK-states (work, tardiness, prolonged work etc.) is transferred
to (time) accounts with the relevant orders. E.g. if the employee was 20 minutes late for work, the late arrival will
transfer 20 minutes to the relevant account, Tardiness in this case.
Checking the Default box enables assigning a group of accounts (default) to all day types.
Ne orders are defined in a window such as Fig. 3.8.6-1 as well as edited and deleted as explained in the
previous sections.
There are two types of orders as can be chosen with the radio buttons to the right under the list of orders. One
type of order takes data from an RxK state, the other from an account:
1. RxK order – takes a value from an RxK-state. E.g. if the program discovers the RxK-state late arrival
then the order assigned to this RxK-state will transfer the number of minutes the employee was late. An
attribute can be set to the order. This option is useful if we want to see the amount of „late arrivals“ at
night, for example, and we can assint the night attribute to the order. One order can have many
attributes assigned to it (from different qualifiers). Attribute assignment is done in the bottom right part of
the window with the + button.
2. Account order – the order takes a value from a defined account.
Fields:
Name – name of the order.
Multiplication factor – factor used to multiply the amount taken by the order from the RxK state or the account.
Division factor – amount taken from the RxK state or account is divided by this factor.
Calculation period:
- At the end – denotes that the order transfers the total amount at the end of the period.
- Daily – denotes a daily transfer to the account, not once at the end of the period (e.g. if the period is a month,
then the order will transfer to the account every day in the month).
Min.to transfer and Max. To transfer denote conditions to be fulfilled by the amount in order to be transferred
(e.g. if we want tardiness to be transferred only if the employee is at least 15 minutes late, then we put 15 in
Min. to transfer).
Fixed to transfer – this field specifies a fixed amount to transfer if the min and max conditions are fulfilled (min.
to transfer and max. to transfer).
Rounding:
No – the amount transferred by the order to the account is not rounded.
Down – the amount is rounded down, depending on the value in the Rounding value field. E.g. if the
Rounding value field is 60 and the order has 70 to transfer from an RxK state or an account, the
transferred amount will be 60 minutes.
Up – the amount is rounded up, depending on the value in the Rounding value field. Taking the
previous example, the order will transfer 120 minutes, because that is the next highest multiple of 60
minutes.
Nearer – the amount is rounded to the nearer number, depending on the value of the Rounding value
field. In the previous example, the order would transfer 60 minutes because 70 is closer to 60 than 120.
If the amount is right in the middle, the order will round down or up according to the field If equal.
Rounding value: value used for rounding the amount being transferred to an account.
If equal: determines how to round if the amount is right on the boundary of the rounding rule
Down – the order will round down. E.g. the amount is 30 minutes, and the Rounding value is 60, the
amount is rounded down to 0.
Up – the order will round up. E.g. the amount is 30 minutes, and the Rounding value is 60, the amount
is rounded up to 60.
Transfer variable value with fixed amount: if the box is checked, the fixed amount in the table is added to the
amount taken from the RxK state or an account. So, if the fixed amount value is 20 minutes and the RxK state is
30 minutes, the destination account will get 50 minutes transferred. If the box isn't checked, only the fixed value
will be transferred, so using the previous example, 20 minutes would be transferred.
Decrease source account by transfer amount – This option is only visible for account orders.
22
3.8.7 Accounts
All data (minutes) that are collected by orders are stored in accounts. The reports show these accounts and this
data is the end result of KatzeReports.
This command shows the window (Fig 3.8.7-1) with the list of all created accounts (left side). The right side
shows all the orders assigned to a selected account. The account columns are:
Fig. 3.8.7-1
23
3.8.8 Day types
Day types are actually types of working days in an employee's calendar. The day types defined here are used to
make calendars by which employees are expected to work. Fig. 3.8.8-1 shows a list of existing day types (left
side) and, for the selected day type, a list of intervals for that day (top right) and their graphical representation
(bottom). Qualifiers and orders assigned to the selected Day type are listed in the bottom right part of the
window. A button on the order/qualifier pane lets us assign default qualifiers (to default orders valid for all day
types).
Fig. 3.8.8-1
24
To add a day type (click on the + on the left side) enter the name in the Name field and click on √. Next you
need to define intervals and their presence/absence types. Adding an interval is done with the + in the right half
pane. Now choose the presence type duration in the interval (presence type, from, to).
3.8.9 Calendars
Calendars are made up of day types and are assigned to employees. Any days that don't adhere to the
calendar can be manually entered as „exceptions“.
It's possible for several groups to work in shifts (e.g. the first group is in shift1 for a week and the other group is
in the opposing shift, then they switch shifts). In this case you define as many calendars as there are groups
and give them differing reference (starting) dates.
The left pane of the window in Fig. 3.8.9-1. shows the list of defined calendars, the right pane shows the
assigned day types for the selected calendar.
Fig. 3.8.9-1
25
A2 activity is changed to B2.
The change will happen if the
Duration is greater or equal to
the stated value (e.g. 720
minutes = 12 hours).
3.8.12 Debug
This option opens a new window giving
detailed calculation results (R-events, R-
states, RxK-states and account results)
for a selected employee (combo-box in
upper part of the window). This option is
used during the configuration of the
program.
26
3.9.1 Calendar assignment
By assigning calendars to employees, you define the rules by which
they work. Calendars can be assigned to an employee, a group of
employees, selected departments or the whole company. Calendar
assignments are done with Employees/Assign/New calendar in a
window such as Fig. 3.9.1-1. The top part of the window specifies to
whom we are assigning. The lower part (combo-box) specifies the
calendar and the starting date from which the assigment is valid.
You can get an overview of calendars assigned to an employee by
clicking on the Calendars tab on the right side of the main window.
An overview of manual accounts assigned to an employee can be seen with the Manuual accounts tab on the
right side of the main window.
27
3.9.4 Assigning qualifiers
The Employees/Assign/New qualifier menu item opens a dialogue
as in Fig. 3.9.4-1 for assigning qualifiers to employees. They need to
be added to employees if we need a more specific distribution of
work time, based on time of day or other factors. An overview of
qualifiers assigned to an employee can be seen with the Data tab on
the right side of the main application window.
28
Type of RxK state to be optimised – this option is used for automatic shift detection (ASD), i.e. when there are
several shifts in a day and the program must decide, based on a criterion, which shift the employee worked in.
E.g. if you choose the RxK state work and Optimisation method Max, then the shift is chosen in which he spent
the most minutes. There are other ways to choose a shift e.g. use the RxK state tardiness and Optimisation
method set to Min. This means the shift in which he was the least late will be chosen.
Presence type to substitute non-working hours in clockings – default presence type (R-state), which will be
assigned to the intervals before the first and after the last clockings in the time-span for which the calculation is
being made.
Optimisation method – this defines how to optimise the RxK state chosen in Type of RxK state to be optimised.
E.g. if the optimisation method selected is Max, and Type of RxK state to be optimised is work and there is a
day-type with automatich shift detection, the system will recognise which of the possible shifts will be valid for an
employee, based on clocking data.
Fig. 3.9.6-1
29
done from the 1st. of the month to the current date. For any other month, the calculation is done for the
whole month.
3.9.7 Calculation
To get the desired report, you must first do a
calculation. The result depends on correct
clockings, the configuration and calendar
assignment.
When all the parameters have been selected,
clicking on the Calculate button or selecting the
Calculation/Calculate menu item, Fig. 3.9.7-1 will
appear. Two types of calculation can be selected,
along with an added option that can be chosen.
Fig. 3.9.7-2
he second type of calculation (Join new calculation's results...) (Fig. 3.9.7-2) means that new results for the
selected employees will be merged with existing results for all the other (unselected) employees. The existing
data is taken from the
calculation given in
Select calculation. This
means that the interval
for which the
calculation is made will
be the same as in the
existing calculation,
but the results will be
new only for the
currently selected
employees (added or
overwritten).
Additionally, at the
bottom of the dialogue,
the option is given to
transfer values from a
selected calculation Fig. 3.9.7-3
30
into the currently starting calculation (Fig. 3.9.7-3). Value
transfer is only done for transferrable accounts (marked as
such during creation).
Calculation monitor
When the the calculation is started with OK, the
Calculation monitor window appears in the bottom part of
the Calculation window (Fig. 3.9.7-4). It shows information
about the calculation process.
Steps leading up to the calculation are reported in the left
pane and steps in the calculation itself in the right pane.
During the calculation, in the status line at the bottom of
the window, you can see how many employees are
waiting for calculation, how many have been processed
and in what time. The calculation can be interrupted with
Stop.
When the calcualtion is finished, the monitor will show the
message Done.
Fig. 3.9.7-5
31
Templates
The window for creating templates (Fig. 3.9.7-6) appears from the main menu Calculation/Templates or by right
clicking on part of the Calculation window with the list of calculations. Select Show/Templates.
The left part contains a list of templates and the right pane, for a selected template, lists the columns/accounts
to show in the report.
Templates are added with +. You must enter:
Name of template
Time Format – can be minutes (Minutes), hours and minutes (HH:MM) and decimal (Decimal)
By days – show calculation values for each day (when selected) or as a sum for the whole period (when
not selected),
Clockings – selection shows clockings in the report.
The right pane contains a list of columns (accounts), which will be displayed in the report selected on the left.
Adding is done with a click on +, then selecting an account from the list of all existing accounts. Clicking on Add
all adds all acounts to the report.
Displaying reports
A report can be displayed for the selected calculation from the list. As was shown in Calculation settings, a
right click on calaculation will open a list of options for working with existing calculations.
Choosing Show or CSV opens a list of existing templates for reports.
The difference between these two is that the first is a tabular display and CSV (comma separated values) is a
text file which is saved somewhere for importing into Excel or payroll software. Examples of reports are given in
report-table and report-csv
The separator in CSV reports can be changed in File/Application settings...) on the CSV tab, as shown in
settings csv.
Calculation control
Some columns (accounts marked as control) can be controlled.
First, select the employees and click on the Calculation control option. A window such as Kontrola proračuna
appears.
Values can be examined and, if necessary, clockings, assigned calendars and exceptions can be edited. The
editing options are reachable by right-clicking on a clocking or calendar/exception. The same options are
available in the window's tool bar.
If any data of an employee is changed, his/her name will be shown in red.
All changes are confirmed by clicking on OK or cancelled by clicking on Cancel. If the changes are confirmed,
they are immediately visible on the Employees tab.
Printing reports
Right-clicking on a report displayed in the program gives you two options:
CSV – saving the report as a CSV file and
View – view the printable report. The printer settings are standard.
Servers
Calculation/Servers is used during multiprocessing i.e. the use of multiple PCs simulataneously to speed up the
calculation. The window (Fig. 3.9.7-3) contains a list of selected PCs which will take part in multiprocessing.
To add a new PC, click on + . The window in Fig. 3.9.7-4 appears, in which you need to:
- select a PC from the combo-box.
- Enter the name of a temporary database which will be used on that PC.
- Select a data exchange folder on the selected PC. Make sure it is a shared folder with read, write and delete
privileges for all users.
- Select a folder on the selected PC to place the temporary database.
32
By clicking on OK,
the PC is added to
the list of PCs
allowed to perform
the calculation.
Clicking the box in
the Use column, you
can determine if the
PC will be used in
the next calculation.
Click on Edit to
change parameters
of the selected PC
and Delete to
remove the PC from
the list.
Settings – opens a
window for editing
calculation settings
(see section 3.9.5
Calculation settings)
Get data – get
calculation results
from PCs taking part
in the calculation.
This is done
atuomatically, so this
command is for
diagnostic purposes
only.
Calculation log
All calculation details
are saved in the (Fig.
3.9.7-5) kr7log file,
which is created
automatically for each Fig. 3.9.7-5
PC on which calculation was started. These kr7log files are
created on a daily basis. Selecting this option will display a
Windows dialogue for opening a specific kr7log file from the
KatzeReports installation folder.
3.9.8 Reports
Reports based on SQL queries
Reports/SQL enables the overview of data in the
KatzeReports database by issuing queries. Selecting this
option displays a new window (Fig. 3.9.8-1), which is in fact
an SQL editor. By entering the desired query in the upper
pane and selecting SQL/Execute or clicking on F9, the query
is performed and the result is placed in the bottom pane. The
program will report an error if there was an SQL syntax
problem.
33
account and undefined orders, markers and
manual accounts). You can show a company
logo in the reports by clicking Set. Clicking on
Delete will remove it.
3.10.4 Messages
File/Messages opens a window that enables
users to exchange messages. It's a usual
display of the sender, the recipient, the tiime the
message was sent and the message contents
(Fig. 3.10.4-1).
3.10.6 Log
Each starting of the program and manual clockings (adding, deleting, editing,
see Clockings) are logged in a file in the KatzeReports7 installation folder -
the log file. The File/Log menu item opens a log as in Fig. 3.10.6-1.
The file contains the date and time, account and PC from which the program
was opened, as well as the user name. It also contains adding, deleting and
editing clockings and the time and date of these activities. Log files are
monthly. Fig. 3.10.5-1
34
Fig. 3.10.6-1
Viewing a log file is done with Log/Read.
Refreshing a log file is done with Log/Refresh .
Clicking Log/Search shows a usual dialogue for serching in the log file.
35
BackUp
Faile/Database/BackUp will start the backup procedure straight away (Fig. 3.11-2).
Save
You can save the database to any location
on the PC. Click on File/Database/Save
database and a standard Windows save
dialogue appears to select the location to
save the database.
3.12.2 About
Help/About opens the dialogue of fig. 3.12.2-1. It contains 3 groups of
data:
At the top is data about the application version, period of
creation and copyright holder;
data about the SQL server, name of the PC which hosts the
database and database version;
data about the user's licence. Company name, maximum
number of employees and licence duration.
3.12.3 End
Fajl/End closes the program. Fig. 3.12.2-1
36