Avaya Call Management System Custom Reports page 146

Advanced report design
In the previous report figure, Row Search ID 1 is assigned to the Forecast Method
field. Notice also that the database item for this field is FMETHOD. FMETHOD is stored in
the f_cday table, but is not stored in the f_cdayrep table. This is an example of how
current day forecast data is divided between the two tables.
However, in the following figure, notice that Row Search ID 1 has row search conditions
that are almost identical those in the previous figure:
Row search conditions for Forecast data
The only differences between Row Search ID 0 and Row Search ID 1 are the table
selections and the field types. In this way, the data in the tables will match.
Note:
Note:
146 Avaya CMS Custom Reports
Row search ID: 1
From tables: f_cday
Select rows where: ROW_DATE = $i_date and SPLIT = $i_split
Field/bar type (Select one):
<x> Discrete
< > Repeated vertically, spacing 1___
In the standard Current Day Forecast, FMETHOD normally displays a
character string, either Seasonal trending, Current trending, or
No trending. However, the CMS database actually stores a number to
represent each method. So, if you include the FMETHOD database item in a
report, CMS displays a number, not a character string, in the report (see
Avaya CMS R3V11 Database Items and Calculations, 585-780-702, for a
description of these numbers).
You can retrieve data from the Current Day Configuration Forecast
(f_cday) table only if the appropriate call handling profile has been
specified for the particular dates. For retrieval of data from the Current Day
Forecast Report (f_cdayrep) table, Forecast Manager must have run for
the particular date for which the report is run.
Row Search Window
and ACD = $acd