Functional and Technical Specification for Customization
Customer Requirement Document
Mod. Tracking #: 1
Design # – Conversion 1
Initial Specification Approval
Customer Requirement Document
Prepared:
Amie Salamido
Prepared By:
Peralta Technical Lead Approval:
Initial:
Date Prepared:
Initial:
Date Reviewed:
Initial:
Date Reviewed:
Initial:
Date Reviewed:
Initial:
Date Approved:
Initial:
Date Approved:
Minh Lam
Reviewed By:
Peralta Functional Lead
2008-07-02
David Betts
Approval:
Michelle Lenh
Reviewed By:
Peralta User Approval:
Wyman Fong
Reviewed By:
Peralta Sponsor Approval:
Thomas Smith
Approved By:
CIBER Project Manager Approval:
Kim Groshek
Approved By:
Completed Modification Acceptance
Customer Requirement Document
Prepared:
Amie Salamido
Prepared By:
Peralta Technical Lead Approval:
Approval:
Date Prepared:
Initial:
Date Reviewed:
Initial:
Date Reviewed:
Initial:
Date Reviewed:
Initial:
Date Approved:
Initial:
Date Approved:
Minh Lam
Reviewed By:
Peralta Functional Lead
Initial:
David Betts
Michelle Lenh
Reviewed By:
Peralta User Approval:
Wyman Fong
Reviewed By:
Peralta Sponsor Approval:
Thomas Smith
Approved By:
CIBER Project Manager Approval:
Kim Groshek
Approved By:
Document Control
Change Record
Date
Author
Version
Change Reference
2008-07-02
Amie Salamido
1.0
n/a
2008-07-09
Amie Salamido
2.0
Added reference to installation
table
Added fields action &
action\reason for job data insert
2008-07-16
Amie Salamido
3.0
Use dept manager to create reports
to information
Reviewers
Sign-Off
Date
Reviewer Name
Copy No.
Name
Position
Sign-Off
Distribution
Version #:3.0 (Ju1 2008)
CIBER Confidential
Page 2
Last saved: 2016-06-28
Functional Specifications
Detailed Business Requirements
Peralta has over 800 regular employees. In order to allow better budget control with limited
maintenance, positions will be created and budgets established by position. Because of the large
volume, a solution should be developed that will allow the load of position data into the system
rather than entering the data manually. This will be a one-time load. On going maintenance will
occur on-line.
Process flow for conversion program:
1. data from job and JobCode for current, active, budgeted employees will be used to
populate the table POSITION_DATA (see table below for source mapping / constants).
Active, budgeted is defined by empl_status in (‘A’, ‘L’, ‘P’) and paygroup in
('RCL','ADM','P10','P11','P12','BTS','PST')
2. position numbers created with the load of position data will be used to insert rows on
JOB, putting the employee into the position. The new row on Job data will contain all
data found on the current row on Job as of the date that the program is run, with the
exception of the fields associated with positions as noted in the table below.
Employees who have future dated rows will not be processed and will be listed in the
exception report to be analyzed and corrected manually
3. HR department table will be updated. The value in the manager ID field will be used to
determine the value that should be in the Manager Position field. After the manager
position field is updated, the manager ID field will be set to blank. After the manager
position has been updated, this info will be used to update reports to fields on Job
Data and Position Data.
4. Update INSTALLATION table with last Position Number that was assigned.
Any exceptions to general rules (eg. empl to be split between two locations, vacant positons,
inactive/non-reg managers) will be entered manually following the conversion.
New effective-dated rows will be inserted in effective-dated child tables of JOB. All data will be
brought forward from current row.
Child tables: JOB_JR (last update date and oprid will be updated on inserted row) and
COMPENSATION
Rows in the Child table JOB_EARNS_DIST will be deleted as of the new effective date. Note that
the data from the deleted JOB_EARNS_DIST table will be stored in a temp table to be used in a
subsequent conversion program that will create position level department budgets.
All rows in the table JOB_IND will be deleted. These rows were created in error and cannot be
accessed on-line.
When processing, the conversion program will produce an exception report (EmplID, Name,
exception message(s) ) for the following conditions:
1. Full/part –time flag of ‘F’ when FTE < 1 or flag of ‘P’ when FTE >= 1.
2. Blank or non-reg Manager ID on department table.
3. Future dated job data exists
Version #:3.0 (Ju1 2008)
CIBER Confidential
Page 3
Last saved: 2016-06-28
Position_data table
FIELDNAME
POSITION_NBR
EFFDT
EFF_STATUS
DESCR
DESCRSHORT
ACTION
ACTION_REASON
ACTION_DT
BUSINESS_UNIT
DEPTID
JOBCODE
POSN_STATUS
STATUS_DT
BUDGETED_POSN
CONFIDENTIAL_POSN
KEY_POSITION
JOB_SHARE
MAX_HEAD_COUNT
UPDATE_INCUMBENTS
REPORTS_TO
REPORT_DOTTED_LINE
ORGCODE
Version #:3.0 (Ju1 2008)
CIBER Confidential
Description
Position
Number
Effective Date
Status as of
Effective Date
Description
Short
Description
Action
Reason Code
Action Date
Business Unit
Department
Job Code
Position Status
Status Date
Budgeted
Position
Confidential
Position
Key Position
Job Sharing
Permitted
Max Head
Count
Update
Incumbents
Reports To
Position
Number
Dotted-Line
Report
Organization
Hierarchy
Code
Data Source / Constant Value
Generate sequential position
number
'2008-07-01'
Comments
Start at 00000100
'A'
JOBCODE_TBL.DESCR
JOBCODE_TBL.DESCRSHORT
'POS'
'CNV'
Run date
'PCCD1'
JOB.DEPTID
JOB.JOBCODE
'A'
'2008-07-01'
'Y'
'N'
'N'
'N'
1
'Y'
JOB.REPORTS_TO
After all position
numbers have
been created and
assigned to
employees, find the
position number
that was assigned
to the emplid that is
found in the
manager ID field for
the employee’s
department.
Update reports to
fields in JOB and
POSITION_DATA
with this value
''
''
Page 4
Last saved: 2016-06-28
FIELDNAME
ORGCODE_FLAG
LOCATION
MAIL_DROP
COUNTRY_CODE
PHONE
COMPANY
STD_HOURS
STD_HRS_FREQUENCY
UNION_CD
SHIFT
REG_TEMP
FULL_PART_TIME
MON_HRS
TUES_HRS
WED_HRS
THURS_HRS
FRI_HRS
SAT_HRS
SUN_HRS
BARG_UNIT
GVT_PAY_PLAN
SEASONAL
TRN_PROGRAM
LANGUAGE_SKILL
MANAGER_LEVEL
FLSA_STATUS
GVT_WIP_STATUS
GVT_STATUS_TYPE
GVT_WORK_SCHED
GVT_SUB_AGENCY
GVT_DT_POSN_ESTAB
GVT_COMP_AREA
Version #:3.0 (Ju1 2008)
CIBER Confidential
Description
Organization
Hierarchy Flag
Location Code
Mail Drop ID
Country Code
Telephone
Company
Standard
Hours
Standard Work
Period
Union Code
Regular Shift
Regular/Temp
orary
Full/Part Time
Monday
Tuesday
Wednesday
Thursday
Friday
Saturday
Sunday
Bargaining Unit
Pay Plan
Seasonal
Training
Program
Language
Required
Manager Level
FLSA Status
Work-inProgress
Status
Status Type
Work Schedule
Sub-Agency
Date Position
Established
Competitive
Area
Data Source / Constant Value
Comments
''
JOB.LOCATION
''
''
''
'PCC'
JOB.STD_HOURS
JOB.STD_HRS_FREQUENCY
JOB.UNION_CD
'N'
‘R'
message should
appear on
exception report if
Full/part –time flag
is ‘F’ when FTE < 1
or flag is ‘P’ when
FTE >= 1.
JOB.FULL_PART_TIME
JOB.STD_HOURS/5
JOB.STD_HOURS/5
JOB.STD_HOURS/5
JOB.STD_HOURS/5
JOB.STD_HOURS/5
0
0
''
''
'N'
''
''
JOBCODE_TBL.
MANAGER_LEVEL
JOB.FLSA_STATUS
''
''
'F'
''
'2008-07-01'
''
Page 5
Last saved: 2016-06-28
FIELDNAME
GVT_COMP_LEVEL
GVT_ORG_TTL_CD
GVT_ORG_TTL_DESCR
GVT_DRUG_TEST_REQ
GVT_FUND_SOURCE
GVT_INTEL_POSN
GVT_LEO_POSITION
GVT_MOB_POSN_IND
GVT_PROC_INTEG_PSN
GVT_PRESIDENT_APPT
GVT_NTE_DATE
GVT_OCC_SERIES
GVT_PAR_NBR
GVT_PAREN_TITLE
GVT_PERF_PLAN
GVT_POI
GVT_POSN_LOC
GVT_POSN_OCCUPIED
GVT_POSN_SENS_CD
SECURITY_CLEARANCE
GVT_STAFF_LINE
GVT_LAST_AUDIT_DT
GVT_AUDITED_BY_ID
GVT_OBLIGATED_TO
GVT_OBLIG_EXPIR_DT
GVT_TARGET_GRADE
Version #:3.0 (Ju1 2008)
CIBER Confidential
Description
Competitive
Level
Organization
Posn Title Cd
Organization
Position Title
Drug Test
(Applicable)
Fund Source
Intelligence
Position
LEO/Fire
Position
Mobility
Position
Procurement
Integ Posn
Presidential
Appt Posn
Not To Exceed
Date
Occupational
Series
Personnel
Action Request
Nbr
Parenthetical
Title
Performance
Plan
Personnel
Office ID
Position
Location
Position
Occupied
Sensitivity
Code
Security
Clearance
Staff/Line
Position
Position Audit
Date
Position
Audited By
Obligated To
ID
Obligation
Expiration
Target Grade
Data Source / Constant Value
Comments
''
''
''
'N'
'A'
'N'
'N'
'N'
'N'
'N'
''
''
''
''
''
''
'H'
''
''
'0'
''
''
''
''
''
''
Page 6
Last saved: 2016-06-28
FIELDNAME
GVT_PI_UPD_IND
GVT_EXEC_FIN_DISCL
REG_REGION
CLASS_INDC
ENCUMBER_INDC
FTE
POSITION_POOL_ID
EG_ACADEMIC_RANK
EG_GROUP
ENCUMB_SAL_OPTN
ENCUMB_SAL_AMT
HEALTH_CERTIFICATE
SIGN_AUTHORITY
ADDS_TO_FTE_ACTUAL
SAL_ADMIN_PLAN
GRADE
GRADE_FROM
STEP_FROM
GRADE_TO
STEP_TO
STEP
JOB_PROFILE_ID
PKG_TEMPLATE_ID
PKG_RULE_ID
Version #:3.0 (Ju1 2008)
CIBER Confidential
Description
pi upd ind
Executive
Financial
Disclosure
Regulatory
Region
Classified/Uncl
assified Indc
Encumbrance
Indicator
FTE
Position Pool
ID
Academic
Rank
Service
Calculation
Group
Encumber
Salary Option
Encumber
Salary Amount
Health
Certificate
Signature
Authority
Adds to FTE
Actual Count
Salary
Administration
Plan
Salary Grade
From Grade
Step
To Grade
Step
Step
Job Profile ID
Package
Template ID
Package Rule
ID
Data Source / Constant Value
''
Comments
'N'
'USA'
'C'
Depends on preencumbrance
processing
determined by
finance dept
TO BE DETERMNED
JOB.FTE
''
''
''
'STP'
0
Depends on preencumbrance
processing
determined by
finance dept
Depends on preencumbrance
processing
determined by
finance dept
''
''
Y
JOBCODE_TBL.SAL_ADMIN_PL
AN
JOBCODE_TBL.GRADE
''
0
''
0
JOBCODE_TBL.STEP
''
''
''
Page 7
Last saved: 2016-06-28
FIELDNAME
SUPV_LVL_ID
INCLUDE_SALPLN_FLG
DESCRLONG
Description
Supervisor
Level ID
Include Salary
Plan/Grade
Description
Data Source / Constant Value
Description
Effective Date
Effective
Sequence
Action
Action Reason
Action Date
Position
Number
Position Entry
Date
Data Source / Constant Value
Run date
Comments
''
'N'
JOBCODE_TBL.DESCR
JOB table
FIELDNAME
EFFDT
EFFSEQ
ACTION
ACTION_REASON
ACTION_DT
POSITION_NBR
POSITION_ENTRY_DT
0
‘POS’
‘CNV’
Run date
As generated for position_data
table
Supervisor ID
‘‘
SHIFT
Shift
‘N’
REG_TEMP
Regular/Temp
orary
FULL_PART_TIME
Full/Part Time
EARNS_DIST_TYPE
ADDS_TO_FTE_ACTUAL
CLASS_INDC
REPORTS_TO
LASTUPDDTTM
LASTUPDOPRID
Version #:3.0 (Ju1 2008)
CIBER Confidential
Adds to FTE
Classified/Uncl
assified
Indicator
Reports to
Position
Number
Last Update
Datetime
Last Update
OPRID
Start at 00000100
Run date
SUPERVISOR_ID
Earnings
Distribution
Type
Comments
‘R’
If FTE = 1, ‘F’;
If FTE < 1 , ‘P’
‘N’
‘Y’
‘C’
After the data in
this field is used to
populate the
reports_to field, it
will be set to blank
Will be set to ‘N’ for
all employees in
positions
Will be set to ‘R’ for
all employees in
positions
Will be set to None
for all employees –
budget strings will
be tracked on dept
budget table
Will be set to ‘Y’ for
all employees in
positions
Will be set to ‘C’ for
all employees in
positions
Determined from manager ID field
on the employee’s department
Run date
Program Name
Page 8
Last saved: 2016-06-28
INSTALLATION table
FIELDNAME
POSN_NBR_LAST
Description
Last Position
Number
Data Source / Constant Value
Value from counter after last
number is assigned in program
Comments
Business Justification
Using position management will reduce on-line maintenance as employees move into and out of
positions. Using an automated load for initial implementation will reduce time required and possible
data entry errors. An automated load can be re-used consistently in multiple environments.
Risks
Testing required to ensure that data loaded by automated means behaves like data entered on-line.
Alternative Work Around (Not requiring customization)
Enter Position data manually on-line
Disadvantages of the Alternative Work Around
Manual entry is time consuming, prone to user error and cannot be re-used in multiple environments.
Stakeholders
Stakeholders are individuals or groups with an interest in the project that are not users of the project
deliverables. List and describe the stakeholders along with their responsibilities as they relate to this
project.
Name
Description
Responsibilities



Users
Briefly describe the users, including their responsibilities to the project, their affiliation, and how they will
use the software. When possible, refer to roles rather than individual names. If necessary, use real names.
Name
Description
Responsibilities/Interests


Assumptions
Data in source tables (JOB, JOBCODE_TBL, DEPT_TBL) will be clean and correct.
Version #:3.0 (Ju1 2008)
CIBER Confidential
Page 9
Last saved: 2016-06-28
Who will be using this modification
HR functional users
Process Flows/Frequencies
One-time data load at go-live
What are the inputs and outputs of the modification in terms of
business processing
Clean source data is required
Capabilities
Capabilities statements describe functionality of the software including reports and interfaces with
other systems. They are extracted from users stories. If a capability describes a report or interface,
place an X in the appropriate box. The modification will be tested against these capabilities during
acceptance testing.
No.
Capability
Report Interface
Security
Set up security access to the position management pages for HR analyst.
Dependencies
Position must exist before it can be assigned to an employee and before a budget can be created for
it.
Acceptance Criteria
Queries on target tables show that data has been successfully loaded in the correct fields and
formats. On-line transactions using the loaded data complete successfully.
Glossary
Include any terms or acronyms unique to this project, the district, or the department.
Term
Version #:3.0 (Ju1 2008)
CIBER Confidential
Definition
Page 10
Last saved: 2016-06-28
Technical Estimates
Approach
Describe the approach
Estimates
Estimate the technical effort required implementing this approach. Include the following where
appropriate:
 Number of PeopleSoft objects involved and the nature in which it is used (modified,
cloned, new)
 Number of lines of code modified or created
 Number and type of resources are required
 Any other useful estimates
Hours Estimate
8 hours
24 hours
40 hours
80 hours
est’d hours = ###
Risks
List any risks particular to this approach
Risk Mitigation
Discuss means to limit or eliminate the impact of risks identified above.
Assumptions
List any assumptions particular to this approach.
Constraints
Include anything outside of the control of the technical team that will affect technical decisions
(schedule, resources, etc)
Version #:3.0 (Ju1 2008)
CIBER Confidential
Page 11
Last saved: 2016-06-28
Impacted Objects
Impact Type (New,
Modify, or Delete)
Add a new field to
the existing record
Object Type
(Record, View, Page,
PeopleCode, etc)
Record
Obect Name
Comment
PS_PERSONAL_DATA
DATE
SUBMITTED:
Date Required
By:
Version #:3.0 (Ju1 2008)
CIBER Confidential
Page 12
Last saved: 2016-06-28
Technical Specifications
Modified Online Objects:
Project Name
Project Information
Comment:
Name:
Portal Registry Structure
Name:
Portal Registry Structure Definition
Type (Folder or Content):
Label:
Sequence:
Parent Folder:
Object Owner ID:
Product:
Long Description:
*Menu:
*Component:
Permission Lists:
* For Content Reference portal registry structures only
Menu
Menu Group
Modify
New
Menu
Bar
Component
Component
Component
New Modify
Search Record
Add Search Record
Actions Allowed (Add,
Update/Display, etc.)
Pages
Page:
Record
New
Modify
Field Name
Component:
Type
Display
Only
Invisi
ble
Disp
Cntrl
Rel
Disp
Lvl
Component/Page Security
Component
New Modify
Version #:3.0 (Ju1 2008)
CIBER Confidential
Page
Permission List
Display
Only (Y/N)
Actions (Add, Upd,
Upd/Disp, Corr)
Page 13
Last saved: 2016-06-28
Records
Record:
New
Field Name
Modify
Key
Dir
Req
Src
Key
Alt
Src
List
Box
Default Value
Table Edits
Indexes
Record:
Field Name
Index:
Column Position
Unique (Y or N):
A/D
Fields
Field Name
New Modify
Type
Len
Value
Active
Long Name
Short Name
Translate Values
Translate Values
Field Name
New Modify
Version #:3.0 (Ju1 2008)
CIBER Confidential
Eff Date
Long Name
Short Name
Page 14
Last saved: 2016-06-28
Queries
Query Name:
Query Type:
Records
Record Name
New
Description:
Owner:
Modify
Alias
Fields
Col Record.Fieldname
Criteria
Logical
Format
Expression 1
Order
By Num
Condition
Type
Agg
Heading Text
Expression 2
SQL
*Paste Screenshot of Query Preview below
HTML
HTML:
Record
New
Modify
Field Name
Message Catalog
Message Set
Number
New
Modify
Message
Number
Severity
Message Text
*Paste Screenshot of new or modified message below.
Version #:3.0 (Ju1 2008)
CIBER Confidential
Page 15
Last saved: 2016-06-28
PeopleCode
Type (Record, Page,
etc)
New Modify
Object Name
(Record.Field, Page,
etc)
Event
Processing Description
Application Engine
Program
New
Modify
Section
Step
Action (Do When, Do While, Do
Select, Do Until, PeopleCode,
SQL, Call Section, or Log
Message)
Definition
Qualifier
Definition Delimiter
File Layout Definition
File Layout
File Layout
Format
Default File Name:
File Record/Segment ID
Name
Seq No
Max
Rec
Length
File
Record
ID
ID
Length
Field
Lengt
h
Start
Positio
n
Field
Qualifier
Field
Inheritance
(REC.FIEL
D)
File Record/Segment ID
Name
Seq No
Max
Rec
Length
File
Record
ID
ID
Length
Field Name
Version #:3.0 (Ju1 2008)
CIBER Confidential
Default
Qualifie
r
Field
Delimiter
Default Value
Default
Qualifie
r
Field
Delimiter
Page 16
Last saved: 2016-06-28
Field Name
Field
Len
Start
Positio
n
Field
Qualifier
Field
Inheritance
(REC.FIEL
D)
Default Value
Process Definition
Process Name:
New
Modify
Process Definition
Process Type:
Description:
Priority:
API Aware:
Long Description:
Process Definition Options
Recurrence Name:
Server Name:
Component
Process Groups
Job Definition
Job Name:
New
Modify
Job Definition
Run Mode:
Description:
Seq
Priority:
Process Type
Server Name:
Component
Version #:3.0 (Ju1 2008)
CIBER Confidential
Process List
Process Name
Run Always
Job Definition Options
Recurrence Name:
Process Groups
Page 17
Last saved: 2016-06-28
Images (Paste New or Modified Images Below)
Page (Before Modification)
Page Print 1
Version #:3.0 (Ju1 2008)
CIBER Confidential
Page 18
Last saved: 2016-06-28
Page (After Modification)
Page Print 2
Version #:3.0 (Ju1 2008)
CIBER Confidential
Page 19
Last saved: 2016-06-28
Batch Objects
Programs
Program Name:
New
Modified
Subprograms:
New
Modified
Records include:
Usage Type: (Read/Write/Delete)
Suggested Unit Testing Approach
Testing Scenarios (should cover ensuring that the process works correctly and that
the process handles any unknown errors correctly)
Version #:3.0 (Ju1 2008)
CIBER Confidential
Page 20
Last saved: 2016-06-28