Business Requirements Specification

System: HRIS
Name: ODS Legacy Data Extract
1.1 Business Overview
Currently HR information is provided to other on-line mainframe legacy applications through
mainframe-based data primarily obtained from the legacy Payroll Master and Personnel Data
Block files. To keep these other applications opertional once HRIS is implemented, the
information needed for these legacy applications has been mapped to data on the HRIS ODS, and
new files will be recreated nightly from the ODS data. These files are: Employee, Position,
Compensation Plans, Leave Activity, and Pay Cycle.

1.2 Business Requirements Matrix

Business
Requirement

Functional
Requirement

A persons demographic
information is needed by the
legacy systems

1a

Extract person table data from

HRIS ODS PERSON table.

Information concerning the

positions a person holds is
required by the legacy system

2a

Extract position table data from

the HRIS ODS POSITION
table.

Information concerning the

various compensation plans a
person has is required by the
legacy systems.

3a

Extract compensation plan table

data from the HRIS ODS
Compensation Participation
Activity Star.

Pay cycle information is

needed in order to perform
processig in the legacy
systems,

4a

Extract pay cycle table data

from HRIS ODS Employee Pay
Activity Star.

Extracted data transferred and

formatted for use on the
mainframe.

5a

FTP data, format numeric data,

and load cluster.

/var/www/apps/conversion/tmp/scratch_3/262151327.doc

Detail
For each person (row) in the
HRIS ODS PERSON table,
extract the person table data to
populate the Employee file.
For each current of future
position (row) in the POSITION
tables as determined by a C or
F in Position Trans Status
Code, extract the ODS data from
the tables to populate the Position
file.
For each person (row) in the
PERSON table, extract the
PERSON and current or
future COMPENSATION
PLANS (tables) tadat to populate
the Compensation Plan file. A
C or F in Compensation
Participation Status code
determines current and
future.
For each current or future
Pay Calendar (row) in the Pay
Calendar tbale, as determined by
a C or F in Pay Calendar
Status Code, extract the ODS
data from the tables to populate
the Pay Cycle file.
FTP data to awaiting mainframe
file. Use File Aid to reformat
numeric data into COBOL signed
numeric format, define and load
cluster.

Business Requirements Specification

/var/www/apps/conversion/tmp/scratch_3/262151327.doc