Request Tracking System Documentation
Technical/Tables
Tables
Several tables are used by the request tracking system. These are
described below, in alphabetical order. For further information about a table,
see the extended table documentation available through the AIMS
TBL option.
Archive Codes Table (RQA)
This table contains valid archive codes. The first
character of the request tracking file key is an archive code. Requests
marked as complete are kept as current requests for up
to 30 days following their completion. They are then
moved to archive status. This helps make such
applications as RTR (Request Tracking Review) more
viable as it looks only at current requests.
Documentation Codes Table (RQD)
This table contains all valid documentation values supported by the
request tracking system.
Employee Codes Table (RQI)
When indicating a project leader or project team in the request tracking
system, initials are used. This table provides a translation into the person's
name. Since the request tracking system can support multiple organization
codes (see the RQO table), the key for this table is a 3
character field composed of the 1 character organization code followed
by the 2 character initials.
Miscellaneous Table (RQM)
Several miscellaneous values are needed by the request tracking system.
This table provides for a generic key and a generic data area to permit entry
of miscellaneous values to prevent unneeded hardcoding in programs.
Organization Codes Table (RQO)
The request tracking system can support tracking of requests for up to 9
different organizations. The organization code is a 1 character field ranging
from 1 through 9. This table contains organization codes considered valid.
Status Codes Table (RQS)
Each request may have a status assigned to it to indicate where it stands.
This table contains those status codes which may be used.
Request Type Table (RQT)
Requests may be of different types (e.g., ad hoc report, project, etc.).
This table contains those codes that are considered valid request types.
User Priority Table (RQU)
The Business Office likes to classify requests according to a priority
scheme. This table documents valid user priority codes. Each category is
listed twice. The descriptive codes are difficult to interpret, and are
redefined as numeric codes. The numeric codes are in decreasing level of
importance (1 = top priority). The request tracking system stores the user
priority using the numeric equivalent.
Request Prefix Table (RQO)
Different organizations may prefer to have requests start with a one
character alpha prefix rather than the request number being entirely numeric.
The PRJ table permits this prefix to be specified by
organization code. If a table entry does not exist for a given
organization code, a prefix of 0 is assumed.
IT Applications Support
Last Modified: