Functional and Technical Specification for Customization
Customer Requirement Document
Mod. Tracking #: 3
Design # –Department Budget Conversion
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:
Yvonne Dorrough
Reviewed By:
Peralta Sponsor Approval:
Thomas Smith
Approved By:
CIBER Project Manager Approval:
TBD
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:
Yvonne Dorrough
Reviewed By:
Peralta Sponsor Approval:
Thomas Smith
Approved By:
CIBER Project Manager Approval:
TBD
Approved By:
Document Control
Change Record
Date
Author
Version
Change Reference
2008-07-09
Amie Salamido
1.0
n/a
2008-08-18
Amie Salamido
1.1
Changed dates from Jul 1 to Jan 1
Added description to
DEDUCTIONS_EMPLOYER
acct_cd field
Reviewers
Sign-Off
Date
Reviewer Name
Copy No.
Name
Position
Sign-Off
Distribution
Version #:1.0 (Jul 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 department budget data into the
system rather than entering the data manually. This will be a one-time load. On going maintenance
will occur on-line. Note: Accounting distribution for earnings should be the same as that on the
ee’s current Job Earnings Distribution. Accounting distribution for deductions and taxes: all
amounts go to combo code: “DEDUCTIONS_EMPLOYER”.
Logic for conversion program:
1. Position Data table must have been populated before this conversion can be run.
2. For each position that exists in the position data table, a row will be created in each of the
tables listed below.
3. Employee level conversion must be run before the department budget conversion can be
run – the position level budget data will be created from a temporary table that is created
by the employee level conversion process.
4. Department level budgets must already exist for the fiscal year 2009.
DEPT_BUDGET table
FIELDNAME
SETID
Description
SetID
Data Source / Constant Value
‘PCCD1’
DeptID
DEPTID
FISCAL_YEAR
POSITION_POOL_ID
SETID_JOBCODE
JOBCODE
Year
Pool ID
Jobcode SetID
Job Code
POSITION_DATA.DEPTID
2009
‘‘
‘‘
‘‘
Position
POSITION_NBR
EMPLID
EMPL_RCD
EFFDT
EFFSEQ
EFF_STATUS
BUDGET_LEVEL_INDC
CURRENCY_CD
OVERALL_BDGT_CAP
Version #:1.0 (Jul 2008)
CIBER Confidential
ID
Empl Rcd#
Eff Date
Sequence
Status
Bdgt Level
Currency
Overall
POSITION_DATA.POSITION_NB
R
‘‘
0
2009-01-01
0
‘A’
P
‘USD’
0
Comments
Data selected from
temporary table
created by
employee level
conversion
Data selected from
temporary table
created by
employee level
conversion
Page 3
Last saved: 2016-06-28
FIELDNAME
ERN_BDGT_CAP
DED_BDGT_CAP
TAX_BDGT_CAP
ACTION_DT
Description
Earn Cap
Ded Cap
Tax Cap
Action Date
Data Source / Constant Value
0
0
0
Current date
Comments
Description
SetID
Data Source / Constant Value
‘PCCD1’
Comments
DEPT_BUDGET_ERN table
FIELDNAME
SETID
Data selected from
temporary table
created by
employee level
conversion
DeptID
DEPTID
FISCAL_YEAR
POSITION_POOL_ID
SETID_JOBCODE
JOBCODE
Year
Pool ID
Jobcode SetID
Job Code
POSITION_DATA.DEPTID
2009
‘‘
‘‘
‘‘
Position
POSITION_NBR
EMPLID
EMPL_RCD
EFFDT
EFFSEQ
ERNCD
BUDGET_SEQ
ID
Empl Rcd#
Eff Date
Sequence
Earn Code
SEQ#
POSITION_DATA.POSITION_NB
R
‘‘
0
2009-01-01
0
‘‘
1
Data selected from
temporary table
created by
employee level
conversion
Combo Code
ACCT_CD
GL_PAY_TYPE
BUDGET_AMT
HP_EXCESS
GL Pay Type
Budget
Allow
Overspend
Temp table.ACCT_CD
from employee in this position
‘‘
0
‘Y’
Note: for a split
employee, 2 or
more lines will exist
in this table.
Data selected from
temporary table
created by
employee level
conversion
Distrb %
DIST_PCT
PERCENT_EFFORT
Version #:1.0 (Jul 2008)
CIBER Confidential
DIST_PCT from temp table for
employee in this position
% Effort
Data selected from
temporary table
created by
employee level
conversion
0
Page 4
Last saved: 2016-06-28
FIELDNAME
FUNDING_END_DT
HP_USED_DISTRIBUTN
HP_FRINGE_GROUP
HP_REDIRECT_ACCT
Description
Funding End
Dt
Distributed
Fringe Group
Redirect
Data Source / Constant Value
Description
SetID
Data Source / Constant Value
‘PCCD1’
Comments
null
‘N’
‘‘
‘‘
DEPT_BUDGET_DED table
FIELDNAME
SETID
Comments
Data selected from
temporary table
created by
employee level
conversion
DeptID
DEPTID
FISCAL_YEAR
POSITION_POOL_ID
SETID_JOBCODE
JOBCODE
Year
Pool ID
Jobcode SetID
Job Code
POSITION_DATA.DEPTID
2009
‘‘
‘‘
‘‘
Position
POSITION_NBR
EMPLID
EMPL_RCD
EFFDT
EFFSEQ
DEPT_BDGT_DED_KEY
BUDGET_SEQ
ID
Empl Rcd#
Eff Date
Sequence
Budget Ded
Key
SEQ#
Combo Code
ACCT_CD
PLAN_TYPE
BENEFIT_PLAN
DEDCD
DED_CLASS
GL_PAY_TYPE
BUDGET_AMT
HP_EXCESS
DIST_PCT
FUNDING_END_DT
HP_USED_DISTRIBUTN
OVERRIDE_IND
Version #:1.0 (Jul 2008)
CIBER Confidential
Plan Typ
Plan
Deductn Cd
Ded Class
GL Pay Type
Budget
Allow
Overspend
Distrb %
Funding End
Dt
Distributed
Override
POSITION_DATA.POSITION_NB
R
‘‘
0
2009-01-01
0
Data selected from
temporary table
created by
employee level
conversion
‘‘
0
DEDUCTIONS_EMPLOYER
(DUMMY FOR DEDUCTIONS – 101-470-9918-1-672800-0000)
‘‘
‘‘
‘‘
‘‘
‘‘
0
‘Y’
100
Null
‘N’
‘N’
Page 5
Last saved: 2016-06-28
DEPT_BUDGET_TAX table
FIELDNAME
SETID
Description
SetID
Data Source / Constant Value
‘PCCD1’
DeptID
DEPTID
FISCAL_YEAR
POSITION_POOL_ID
SETID_JOBCODE
JOBCODE
Year
Pool ID
Jobcode SetID
Job Code
POSITION_DATA.DEPTID
2009
‘‘
‘‘
‘‘
Position
POSITION_NBR
EMPLID
EMPL_RCD
EFFDT
EFFSEQ
STATE
LOCALITY
TAX_CLASS
BUDGET_SEQ
ID
Empl Rcd#
Eff Date
Sequence
State
Locality
Tax Class
SEQ#
Combo Code
ACCT_CD
GL_PAY_TYPE
BUDGET_AMT
HP_EXCESS
DIST_PCT
FUNDING_END_DT
HP_USED_DISTRIBUTN
OVERRIDE_IND
GL Pay Type
Budget
Allow
Overspend
Distrb %
Funding End
Dt
Distributed
Override
POSITION_DATA.POSITION_NB
R
‘‘
0
2009-01-01
0
‘‘
‘‘
‘‘
1
DEDUCTIONS_EMPLOYER
(DUMMY FOR DEDUCTIONS – 101-470-9918-1-672800-0000)
‘’
0
Comments
Data selected from
temporary table
created by
employee level
conversion
Data selected from
temporary table
created by
employee level
conversion
‘Y’
100
Null
‘N’
‘N’
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.
Version #:1.0 (Jul 2008)
CIBER Confidential
Page 6
Last saved: 2016-06-28
Alternative Work Around (Not requiring customization)
Enter department budget 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 Note (2008-08-18): user list will be determined later in the project
(November)
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
Positions exist in the system and are assigned to ee’s
Employee/Position conversion program has already been run.
Department level budget accounting strings must already exist for the fiscal year 2009.
Who will be using this modification
Budget control 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
N\A
Capabilities
Capabilities statements describe functionality of the software including reports and interfaces with
Version #:1.0 (Jul 2008)
CIBER Confidential
Page 7
Last saved: 2016-06-28
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
Ensure access to department budget page is set up for appropriate users
Dependencies
Positions must exist in position data table
Department level budget accounting strings must exist.
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
DeptID
Definition
Cost Center
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
Version #:1.0 (Jul 2008)
CIBER Confidential
40 hours
80 hours
est’d hours = ###
Page 8
Last saved: 2016-06-28
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 #:1.0 (Jul 2008)
CIBER Confidential
Page 9
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 #:1.0 (Jul 2008)
CIBER Confidential
Page 10
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 #:1.0 (Jul 2008)
CIBER Confidential
Page
Permission List
Display
Only (Y/N)
Actions (Add, Upd,
Upd/Disp, Corr)
Page 11
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 #:1.0 (Jul 2008)
CIBER Confidential
Eff Date
Long Name
Short Name
Page 12
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 #:1.0 (Jul 2008)
CIBER Confidential
Page 13
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 #:1.0 (Jul 2008)
CIBER Confidential
Default
Qualifie
r
Field
Delimiter
Default Value
Default
Qualifie
r
Field
Delimiter
Page 14
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 #:1.0 (Jul 2008)
CIBER Confidential
Process List
Process Name
Run Always
Job Definition Options
Recurrence Name:
Process Groups
Page 15
Last saved: 2016-06-28
Images (Paste New or Modified Images Below)
Page (Before Modification)
Page Print 1
Version #:1.0 (Jul 2008)
CIBER Confidential
Page 16
Last saved: 2016-06-28
Page (After Modification)
Page Print 2
Version #:1.0 (Jul 2008)
CIBER Confidential
Page 17
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 #:1.0 (Jul 2008)
CIBER Confidential
Page 18
Last saved: 2016-06-28