Functional and Technical Specification for Customization
Customer Requirement Document
Mod. Tracking #: 8
Design # – Update ACCT_CD_TBL
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-10
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-10
Amie Salamido
1.0
n/a
2008-08-18
Amie Salamido
1.1
Notes for object code only and
users to be determined in Nov.
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
Delivered encumbrance processing uses the field ACCT_CD_TBL.ENCUMB_ACCOUNT to
distribute encumbrance entries. A majority of the rows in this table have no values in the
encumbrance account field. At Peralta, encumbrance entries are distributed to the same account
(object code) as the expense, so the same value should appear in the encumbrance account (object
code) field as that found in the account (object code) field.
Business Justification
In order to use delivered encumbrance processing, the encumbrance account (object code) field must
be populated with the appropriate value. Using an automated update for initial implementation will
reduce time required and possible data entry errors. An automated update 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 values manually on line.
Disadvantages of the Alternative Work Around
Manual entry is time consuming, prone to user error and cannot be re-used.
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
Version #:1.0 (Jul 2008)
CIBER Confidential
Description
Responsibilities/Interests


Page 3
Last saved: 2016-06-28
Assumptions
No exceptions to the rule that encumbrance account equals expense account exist.
Who will be using this modification
Finance users
Process Flows/Frequencies
Encumbrance processing occurs once at the beginning of the year and periodically as necessary
when changes occur throughout the year
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
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
n/a
Dependencies
n/a
Acceptance Criteria
Encumbrance entries are applied to the correct account.
Glossary
Include any terms or acronyms unique to this project, the district, or the department.
Term
Version #:1.0 (Jul 2008)
CIBER Confidential
Definition
Page 4
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 #:1.0 (Jul 2008)
CIBER Confidential
Page 5
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 6
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 7
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 8
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 9
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 10
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 11
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 12
Last saved: 2016-06-28
Page (After Modification)
Page Print 2
Version #:1.0 (Jul 2008)
CIBER Confidential
Page 13
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 14
Last saved: 2016-06-28