Lucent Technologies CentreVu Report Designer, User Manual

Page: 231 / 266

SQL Query and CMS Database Table Basics CentreVu Report Designer Version 8 User Guide
CMS Database Table Basics
18-9
●
Event counts (for example,
ACDCALLS
,
INTERFLOWCALLS
,
ABNCALLS
, and so on)
●
For real-time and agent trace reports, current state data (for
example,
WORKMODE
,
DURATION
,
NUMINUSE
, and so on).
See the CentreVu CMS R3V8 Database Items and Calculations (585-
210-939) document for a description of database tables and items
including the exceptions, forecast, and login/logout tables.
Standard database items are often shared by more than one table. For
example,
ABNCALLS
can identify a column in the Current Interval Split,
Daily Split, or Intrahour Agent tables (or many other tables).
CentreVu CMS can determine the exact database item only when it is
identified with a table. The same data item may exist in several CMS
database tables, with the same data item name used. If a data item exists
in a real-time CMS table as well as an integrated CMS table, its value will
usually be different depending on which table is queried. If data items in
reports created with Report Designer are returning unexpected values,
particularly in integrated reports, check that the correct table is being
queried.
Custom Database
Items
18
You must enter a custom database item, with the custom table name as a
prefix, exactly as you defined it in the Dictionary subsystem. The data
identified by a custom database item depends entirely on the data you
entered for the item in the custom table.
When you create a custom database table, as described in this chapter,
keep in mind that all custom database table names need to begin with the
“c_” prefix. If you do not name the tables with the c_, they will not
automatically be backed up and they will not show up in the Query
Assistant.
Constants
18
A constant is the name of a fixed numerical value (whole number or
decimal) that you define in the Dictionary subsystem. Constant names
can be up to 20 characters long. A constant could represent a per-minute
usage rate for trunks, a daily or hourly wage rate, or a service objective
(like number of abandons, number of ACD calls, or percent within service
level). A constant could also represent an average for the estimated
dollar loss of an abandoned call, which could then be used to calculate
daily loss of revenue due to abandoned calls. No standard constants
exist in
CentreVu CMS when it is first installed. Therefore, you must
define every constant you want to use.