Get documents about "XX09000 FIS90 DS ModName 2009MMDD
Document Sample
Modification Approval and Design Request
California State University
CMS Baseline
General Information
Item Enter Information Requested
Service Request Number Click here to enter service request number.
Modification Number Click here to enter modification number.
Modification Name Click here to enter modification name.
Modification Request Status Select One – In Review, Approved, Not Approved, Deferred, or Cancelled.
Request Initiated By (campus, team, or CMS ) Click here to enter name of campus or group that initiatied request.
Primary Contact (name) Click here to enter name of primary contact.
Primary Contact (email) Click here to enter email address of primary contact.
Filename XX09000_FIS90-DS_ModName_2009MMDD.docx
Modification Request Applies To: (Check all that apply)
Finance 8.4 Finance 9.0
Human Resources 8.9 Human Resources 9.0
Student Administration 8.9 Student Administration 9.0
About this Document
The Modification Approval and Design Request document is a point-in-time document that provides the approval
history, business requirements, design solution, and object list for modifications made to the CMS Baseline
product.
Once the modification is released and posted to the CMS website, this document becomes a historical record of
the modification as initially released. Minor updates (i.e. editing errors or minor corrections) are updated and
republished in this document, but all functional or object changes are documented and posted as Modification
Update Requests.
Section One: Revision History provides a table listing all Modification Update Requests associated with this
document (if applicable), as well as a second table listing all minor document edits. Modification Update
Requests will be posted with the original modification on the CMS website. Please refer to the documentation
web page for each application.
Related Documents
The documents listed below are supporting materials such as test plans, test scripts, business process guides,
etc. associated with this modification. Depending on the complexity of the modification, support materials will
vary. Support materials are also posted on the CMS website, on the documentation web page for each
application.
>>add document list <<
Last Revised: 00/00/00 Page 1 of 16
Name of Modification Modification Approval and Design Request
Modification #.-vXX Module
Table of Contents
Section One: Revision History ................................................................................................................................... 3
Section Two: CMS Central Modification Governance Review (CMS Use Only) ..................................................... 4
Section Three: Business Justification for Modification Request ............................................................................... 5
1.0 Overview ........................................................................................................................................................... 5
2.0 Department/Process Impact ............................................................................................................................. 5
3.0 Cross Product Analysis ..................................................................................................................................... 5
4.0 Alternatives and Recommendation ................................................................................................................... 6
Section Four: Design Specification ............................................................................................................................ 7
1.0 Conceptual Model (Process Flow) .................................................................................................................... 7
2.0 Requirements and Design Details .................................................................................................................... 7
Section Five: Business Test Conditions .................................................................................................................... 9
Section Six: Object Changes ................................................................................................................................... 10
Appendix A: Title...................................................................................................................................................... 16
Last Revised: 00/00/00 Page 2 of 16
Name of Modification Modification Approval and Design Request
Modification #.-vXX Module
Section One: Revision History
Modification Update Requests
Please list Service Request Number (SR#), Date, and Filename of any Update Requests associated with this
modification.
SR# Date Filename of Update Request
Click here Click here Click here to enter Filename of Update Request.
to enter to enter
SR# Date.
Click here Click here Click here to enter Filename of Update Request.
to enter to enter
SR# Date.
Document Edits
Please provide a high-level description of edits made to this document to alert users to changes made since its
initial release. Please note: Minor updates (i.e., editing errors or minor corrections) are updated and republished
in this document, but all functional or object changes are documented and posted as Modification Update
Requests.
Date By Description of Document Edits Section Edited
Click Click here to Click here to enter Description of Document Edits. Click here to
here to enter who is enter Section
enter making Edited.
today’s edits.
date.
Click Click here to Click here to enter Description of Document Edits. Click here to
here to enter who is enter Section
enter making Edited.
today’s edits.
date.
Last Revised: 00/00/00 Page 3 of 16
Name of Modification Modification Approval and Design Request
Modification #.-vXX Module
Section Two: CMS Central Modification Governance Review (CMS Use Only)
CMS Analyst / Author: Click here to enter text.
Oracle Analysis: Select One – Will Not Add Modification to this Product, Possible Addition to Future Release, N/A-
CSU Requirement, or Other-(Please Comment).
Category of Analysis Estimates/ Impacts
Preliminary Time Estimate for Original Modification Click here to enter Time Estimate for Original Modification
Final Time for Original Modification Click here to enter Final Time for Original Modification
Estimated Maintenance Over 5 Years Click here to enter Estimated Maintenance.
Impact on Upgrades Select One – None, Minimal, or Significant
Impact on Data Warehouse Select One – None, Minimal, or Significant
Review and Approval
Area / Title Name Date Action Comments
User Group Click here to Click here Choose an action. Click here to add comments. Samples
enter name of to enter include: Recommended for CMS Central
user group. date. review, Recommended to defer until (date),
recommended for cancellation, etc. .
CMS Application Click here to Click here Choose an action. Click here to add comments. Samples
Director enter name of to enter include: Submitted to SOSS Director for
CMS date. review, deferred until (date), not
Application recommended, cancelled because, etc.
Director.
CMS SOSS Director Click here to Click here Choose an action. Click here to add comments. Samples
enter name of to enter include: Submitted to Senior Director for
SOSS Date review, deferred until (date), cancelled
Director. Reviewed. because, etc.
Chief Information Jessie Lum Click here Choose an action. Choose an item.
Systems Officer to enter
Date
Reviewed.
Last Revised: 00/00/00 Page 4 of 16
Name of Modification Modification Approval and Design Request
Modification #.-vXX Module
Section Three: Business Justification for Modification Request
Please select the appropriate categories to indicate the business justification for this modification request.
Modification Governance Category: Select One – State/Legal, CSU Business Requirement, Productivity
Enhancement, Software Improvement
Modification Decision Criteria [Select ALL that apply]
Impacts the ability to go live or is a result of collective bargaining, Trustee requirements, Executive direction, or
State / Federal regulations
Modification would result in a significant reduction in manual effort
Modification would maintain a significant service level or add significant improvement in administrative
productivity and / or service
Without the modification, additional staff would be necessary to perform the business process
1.0 Overview
Please provide a narrative that clearly states the reason why this modification is needed. What is the background
/ purpose of the request? What details support the mod decision criteria checked above?
< start here
2.0 Department/Process Impact
Describe features such as process frequency and the impact on campus community if the modification is not
approved.
< start here
3.0 Cross Product Analysis
Provide a detailed description of the impact either between modules within your application, or to other
applications (e.g., Campus Solutions, Financials, Data Warehouse, or 3rd Party Tools / Interfaces).
< start here
Last Revised: 00/00/00 Page 5 of 16
Name of Modification Modification Approval and Design Request
Modification #.-vXX Module
4.0 Alternatives and Recommendation
Summarize the alternatives considered. For example, can business requirements be adjusted to meet delivered
functionality? Can a manual process or combination of manual and automated process satisfy the business
requirements? If CSU, state or federal policies are forcing this requirement, can alternatives be discussed with
those bodies to identify alternative means of fulfilling their requirements?
Please list each alternative in a numbered list, with the recommended solution presented last.
1. Alternative One: <start here - enter more in list, as needed>
2. Alternative Two: <start here - enter more in list, as needed>
3. Recommendation: <list last>
Last Revised: 00/00/00 Page 6 of 16
Name of Modification Modification Approval and Design Request
Modification #.-vXX Module
Section Four: Design Specification
1.0 Conceptual Model (Process Flow)
Title of Flow Chart
<Insert Flow Chart>
Delete this Field to Remove Instructions for Flow Chart
Please provide a high-level diagram showing how this modification request fits into the overall business process.
This initial diagram does not represent the final solution, rather it should provide the conceptual "roadmap" so
developers will understand the various touch-points / interfaces / process flows that need to be considered when
developing the solution.
2.0 Requirements and Design Details
Please include business requirements, security requirements, operational, performance, and/or reporting
requirements, as applicable.
<Start here>
Instructions to Complete Requirements - Delete Before Publishing
Functional and Technical analysts need to work together to complete this section. Please remember that this
document captures both the functional and technical components of our modifications. Business users should be
able to understand why the modification was adopted, and any future technical developer should be able to take
this document and recreate the modification with exactly the same outcomes. Please provide enough details and
specifics to make that happen!
Functional Analysts should provide information such as:
What are the business cases that need to be met by this modification?
How would you imagine the process could be completed?
Please include needs and requirements such as:
Business Requirements: Need the ability to enter R32 status for applicants. (sample)
Security Requirements: Page must have the ability to have operator security applied to the new
fields.
Operational Requirements: Must be able to run locally on NT Platform.
Performance Requirements: Must complete the run within one hour.
Reporting Requirements: Must generate running total of FTE for inclusion in the R09 reports.
Last Revised: 00/00/00 Page 7 of 16
Name of Modification Modification Approval and Design Request
Modification #.-vXX Module
Technical Analysts will work with the functional analysts to provide
Documentation of the design considerations leading to each solution
Documentation of the final solution(s)
When detailing the solutions, please be as specific as possible:
Include screen shots if new pages are added
Provide field definitions and required values (if applicable)
Provide diagrams detailing the final solution(s). Here is where data flow diagrams, entity relationship
diagrams, etc. may be appropriate to detail how the solution actually works.
Track Object Changes and enter them in Section Six.
Include appendices, as necessary, if (for example) you are documenting changed PeopleCode or
SQRs.
Last Revised: 00/00/00 Page 8 of 16
Name of Modification Modification Approval and Design Request
Modification #.-vXX Module
Section Five: Business Test Conditions
Provide initial test conditions based on the business requirements. These will act as input to develop regression
and integration test scripts. The conditions should be focused on the business scenarios that will enable the
newly-modified/created modification to be executed. Please also include high level test requirements for
processes that will integrate with other applications or products - e.g. cross-application (HCM/Campus Solutions,
HCM/FIN, Campus Solutions/FIN), other 3rd party integration points (SCO, Data Warehouse), etc.
Business Process Sequence Scenario Description Intent
Row 1 Click here to enter Row 1 Click here to enter Row 1 Click here to enter Row 1 Click here to enter Intent
Business Process Sequence. Scenario Description
Row 2 Click here to enter Row 2 Click here to enter Row 2 Click here to enter Row 2 Click here to enter Intent.
Business Process. Sequence Scenario.
Row 3 Click here to enter Row 3 Click here to enter Row 3 Click here to enter Row 3 Click here to enter Intent.
Business Process. Sequence. Scenario.
Last Revised: 00/00/00 Page 9 of 16
Name of Modification Modification Approval and Design Request
Modification #.-vXX Module
Section Six: Object Changes
Objects listed in this section reflect the point-in-time when the modification is first released. New projects and
objects will be listed on their respective Modification Update Request forms. Please see Section One: Revision
History for a full list of associated update requests.
Important Note:
This section lists objects delivered with a project, but does not provide all details for each object. For complete
specifications on the PeopleSoft objects listed in this section, please use Application Designer to open and view
the project/object details.
Key: When completing the Action column, actions are
New
Altered
Dropped
N/A
Project Name Description Action
Click here to enter Project Name. Click here to enter Project Description. Select
one
Action for
the
Project –
New,
Altered,
Dropped, or
N/A.
Fields
# Field Name Long Name Short Name Description Type Length Action
1. 1Click here to enter Click here to enter Field 1 Click here to Click here to Click Click Select
Field 1 Name. Long Name. enter Field 1 enter Field 1 here here to one
Short Name. Description. to enter Action
enter Field 1 for
Field Length. Field 1
1 - New,
Type. Altered,
Droppe
d, or
N/A.
2. 2Click here to enter Click here to Field 2 Long Click here to Click here to Click Click Select
Field 2 Name. Name. enter Field 2 enter Field 2 here here to one
Short Name. Description. to enter Action
Field Field 2 for
2 Length. Field 2
type. - New,
Altered,
Droppe
d, or
N/A.
Last Revised: 00/00/00 Page 10 of 16
Name of Modification Modification Approval and Design Request
Modification #.-vXX Module
# Field Name Long Name Short Name Description Type Length Action
3.
Records and Views
Record / View Name Type Add to Data Warehouse?
Click here to enter Record/View name. Click here to enter Record/View Choose action for Data
Type. Warehouse – Yes or No.
Parent Record Query Sec Record Set Control Field SQL View
Click here to enter Parent Click here to enter Click here to enter Set Click here to enter SQL View.
Record. Query Secondary Control Field.
Record.
Use View Edit View
# Field List Prmpt
Key Order # Search Audit Default Req’d Tbl Edit
Box Tbl
Row 1 Click here to
1. c Row Row 1 Row 1 Row 1 Row Row 1 Row 1 Row 1 Row 1
enter Field Name 1 Click Click Click 1 Click Click Click Click
Click here to here to here to Click here to here to here to here to
here enter enter enter here enter enter enter enter
to order search. list to default Req’d Tbl Edit. Prompt
enter number box. enter status Table.
Key audit
Row 2 Click here to
2. c Row Row 2 Row Row 2 Row Row 2 Row 2 Row 2 Row 2
enter Field Name 2 Click 2Click Click 2 Click Click Click Click
Click here to here to here to Click here to here to here to here to
here enter enter enter here enter enter enter enter
to order search. list to default Req’d Tbl Edit. Prompt
enter number box. enter status Table.
Key audit
3.
Application Engine Programs
App Engine Program Name Description Action
Click here to enter App Engine Click here to enter App Engine Program Description. Select one
Program Name. Action for
App Engine
Program -
New, Altered,
Dropped, or
N/A
Last Revised: 00/00/00 Page 11 of 16
Name of Modification Modification Approval and Design Request
Modification #.-vXX Module
Application Engine Sections
App Engine Section Name Description Action
Click here to enter App Engine Section Click here to enter App Engine Section Description. Select one
Name. Action for
App Engine
Section -
New, Altered,
Dropped, or
N/A.
Components
Component Name Description Action
Click here to enter Component Name Click here to enter Component Description. Select one
Action for
Component -
New, Altered,
Dropped, or
N/A.
Menus
Menu Name Bar Name Item Name Description Action
Click here to enter Click here to Click here to Click here to enter Menu Description. Select one
Menu Name. enter Bar Name. enter Item Action for
Name. Menu - New,
Altered,
Dropped, or
N/A.
Pages
Page Name Description Action
Click here to enter Page Name. Click here to enter Page Description Select one
Action for
Page - New,
Altered,
Dropped, or
N/A.
Process Definitions
Process Definition Name Description Action
Click here to enter Process Definition Click here to enter Process Definition Description. Select one
Name. Action for
Process
Definition -
New, Altered,
Dropped, or
N/A.
Last Revised: 00/00/00 Page 12 of 16
Name of Modification Modification Approval and Design Request
Modification #.-vXX Module
Process Definition Name Description Action
SQL
SQL Name Description Action
Click here to enter SQL Name. Click here to enter SQL Description. Select one
Action for
SQL - New,
Altered,
Dropped, or
N/A.
Translate Values
Field Value EFFDT Status A/I Long Name Short Name Action
Click here to Click Click here Click here Click here to enter Click here to enter Select one
enter Translate here to to enter to enter Translate Value Long Translate Value Action for
Value field enter Effective status. Name. Short Name Translate
name. transla Date. Value - New,
te Altered,
value. Dropped, or
N/A.
PeopleCode Tables
Please note: There are multiple types of PeopleCode. Tables are provided for the most common types - if other
types are delivered, please insert a new table and title it with the type of PeopleCode delivered. Enter N/A if no
PeopleCode is included in the tables listed below.
Record PeopleCode
Record PeopleCode Name Description Action
Click here to enter Record PeopleCode Click here to enter Description for Record PeopleCode. Select one
Name. text. Action for
Record
PeopleCode
- New,
Altered,
Dropped, or
N/A.
Application Engine PeopleCode
App Engine PeopleCode Name Description Action
Click here to enter App Engine Click here to enter App Engine PeopleCode Description. Select one
PeopleCode Name. Action for
App Engine
PeopleCode
- New,
Altered,
Dropped, or
N/A.
Last Revised: 00/00/00 Page 13 of 16
Name of Modification Modification Approval and Design Request
Modification #.-vXX Module
App Engine PeopleCode Name Description Action
Component PeopleCode
Component PeopleCode Name Description Action
Click here to enter Component Click here to enter Component PeopleCode Description. Select one
PeopleCode Name. Action for
Component
PeopleCode
- New,
Altered,
Dropped, or
N/A
Component Record PeopleCode
Component Record PeopleCode Name Description Action
Click here to enter Component Record Click here to enter Component Record PeopleCode Select one
PeopleCode Name. Description. Action for
Component
Record
PeopleCode
- New,
Altered,
Dropped, or
N/A.
Component Record Field PeopleCode
Component Record Field PeopleCode Description Action
Click here to enter Component Record Click here to enter Component Record Field PeopleCode Select one
Field PeopleCode Name. Description. Action for
Component
Record Field
PeopleCode
- New,
Altered,
Dropped, or
N/A
Page PeopleCode
Name Description Action
Click here to enter Page PeopleCode Click here to enter Page PeopleCode Description. Select one
Name. Action for
Page
PeopleCode
- New,
Altered,
Dropped, or
N/A.
Last Revised: 00/00/00 Page 14 of 16
Name of Modification Modification Approval and Design Request
Modification #.-vXX Module
Name Description Action
Batch Module
Object Type Name Description Action
Click here to Click here to enter Batch Module Click here to enter Batch Module Description. Select one
enter Batch Name. Action for
Module Batch
Object Type. Module
Description -
New, Altered,
Dropped, or
N/A.
Other
Object Type Name Description Action
Click here to Click here to enter Name for Click here to enter Description – for Type -Other. Select one
enter Batch Type- Other. Action for
Object Type Type – Other
- Other. - New,
Altered,
Dropped, or
N/A.
Last Revised: 00/00/00 Page 15 of 16
Name of Modification Modification Approval and Design Request
Modification #.-vXX Module
Appendix A: Title
This section is intended as a placeholder to attach appendices, as applicable -(e.g. delivered code). Please delete
if no appendices are included.
Last Revised: 00/00/00 Page 16 of 16
