38
Budget Planner Phase 2 Enhancements Technical Change Request.doc Technical Change Request & Design Specifications Budget Planner Phase II Enhancements Plan Version: 1.0 Last Updated: 3/16/2009 2:22:00 PM Date Submitted: 8/26/2008 Submitted by: Jeffrey O’Keefe Technical Lead: Jeffrey O’Keefe Expected Start Date: 7/23/2008 Expected End Date: 12/23/2008

Technical Change Request & Design Specificationsit.unm.edu/dashboard/BudgetPlannerPhase2.pdf · batch mode via AppWorx, thereby avoiding the timeout issue. 1.1.1.4 Modifications to

  • Upload
    others

  • View
    7

  • Download
    0

Embed Size (px)

Citation preview

Page 1: Technical Change Request & Design Specificationsit.unm.edu/dashboard/BudgetPlannerPhase2.pdf · batch mode via AppWorx, thereby avoiding the timeout issue. 1.1.1.4 Modifications to

Budget Planner Phase 2 Enhancements Technical Change Request.doc

Technical Change Request

& Design Specifications

Budget Planner Phase II Enhancements

Plan Version: 1.0 Last Updated: 3/16/2009 2:22:00 PM Date Submitted: 8/26/2008 Submitted by: Jeffrey O’Keefe Technical Lead: Jeffrey O’Keefe Expected Start Date: 7/23/2008 Expected End Date: 12/23/2008

Page 2: Technical Change Request & Design Specificationsit.unm.edu/dashboard/BudgetPlannerPhase2.pdf · batch mode via AppWorx, thereby avoiding the timeout issue. 1.1.1.4 Modifications to

Budget Planner Phase 2 Enhancements Technical Change Request.doc Page 2 of 31

Part 1: Technical Change Request 1. Current State and Deficiencies (What is currently available and what problem(s) does this cause?)

Budget Planner was implemented in March 2008 with the minimum changes required to function in the UNM environment. Immediately after the go-live, the Budget Office and other stakeholders reviewed the application and identified other modifications needed to improve the usability of the application in the UNM business environment. These changes are summarized in Phase II of the Budget Planner implementation.

2. Scope

(What changes are to be made and what are not?)

Scope Elements In Scope / Out of Scope

1. HED Document Out of Scope 2. Correct Index Out Of Balance report In Scope 3. Remove lock requirement from Index Out Of Balance report In Scope 4. On Operating Budget Summary, show 1901 and whether it nets to zero In Scope 5. Improve Budget Development Working Report performance In Scope 6. Change Fund, Organization and Program parameters for reports In Scope 7. Use Fund and Program hierarchies and non-data enterable FOPA’s In Scope 8. Remove display of line items with zero amounts In Scope 9. Default Budget ID, Phase and Chart for Budget Development reports In Scope 10. Display Budgeted Account Code Report comment In Scope 11. Add link to worksheet for navigation to Create Budget Worksheet Page In Scope 12. Include salaries in summary totals (Budget Worksheet) In Scope 13. Correct account code lookup of codes with “B” data-entry indicator In Scope 14. Change default number of records returned from all lookups to 100 In Scope 15. Add “Next 100” button for account code lookup Out of Scope 16. Round budget change amount to whole dollars In Scope 17. Correct budget refresh process In Scope 18. Run SPWR by Index and Fund In Scope 19. Add Include or Exclude Vacant Positions option and future-dated distribution flag to SPWR In Scope 20. Add Exclude FTE Outside Hiring Organization option to SPWR In Scope 21. Update Exception Report for FY10 guidelines In Scope 22. Make labor distribution page index-centric In Scope 23. Remove account code blanking when Default From Index button is pressed In Scope 24. Allow modification of labor distributions by amount Out of Scope 25. Disallow entry of zero for labor distribution amount/percentage In Scope 26. Correct organization security and lock functionality In Scope 27. Round position budget and distribution amounts In Scope 28. Disable updates on Job Detail screen (except proposed appointment percent) In Scope 29. Disable changes to base amounts on position detail screen In Scope 30. Disable changes to extracted jobs On Employee Detail screen In Scope

Page 3: Technical Change Request & Design Specificationsit.unm.edu/dashboard/BudgetPlannerPhase2.pdf · batch mode via AppWorx, thereby avoiding the timeout issue. 1.1.1.4 Modifications to

Budget Planner Phase 2 Enhancements Technical Change Request.doc Page 3 of 31

31. Ensure Salary Planner refresh process updates proposed information In Scope 32. Force distributions to 100% In Scope 33. Display message if position has future-dated distributions Out of Scope 34. Apply Sungard patch pcms_dfct90919_bwf70300 In Scope 35. Re-apply UNM modifications to Budget Worksheet In Scope 36. Apply other Finance Self-Service Patches Out of Scope 37. Projected actuals functionality In Scope

3. Additional Hardware and/or Software (What additional installations are required to complete this effort?)

None required. 4. Rationale and Expected Benefit(s) (How will these changes eliminate the deficiencies?)

These changes will greatly improve the usability and efficiency of the application as well as correct several minor errors. 5. Alternatives Considered

(What are the other solution(s) investigated?) Alternatives

1. Do nothing: This would present a challenge to users of Salary Planner, which has not had many of the index-centric changes implemented in Budget Development. Users would also not benefit from many of the proposed fixes and enhancements to reporting. This alternative would not allow UNM to utilize the application to its fullest.

2.

6. Dependencies

(What work is dependent upon this effort and what work is this effort dependent upon?)

Dependencies Dependent On / Depends Upon

1. None

2.

7. Type of Change (What kinds of technical modifications are required?)

Change in software or hardware Change in Banner Source Code Work-around /add-on/change interfaces to Banner

8. Banner System(s) Impacted (If a change to Banner, which systems are affected?)

A/R Finance Financial Aid General HR/Payroll Student Workflow (attach related Workflow Process Model) Other:

9. Effort Size (Based upon number of planning, design, development, testing, and implementation hours required)

Small (<100 hours) Medium (100 – 200 hours) Project (>200 hours)

10. Project Complexity (Based upon system integration, new technology, and intricacy of solution)

Low Medium High

11. Deliverables

Page 4: Technical Change Request & Design Specificationsit.unm.edu/dashboard/BudgetPlannerPhase2.pdf · batch mode via AppWorx, thereby avoiding the timeout issue. 1.1.1.4 Modifications to

Budget Planner Phase 2 Enhancements Technical Change Request.doc Page 4 of 31

(What outcomes or products – IT components, training materials, SOPs - are to be produced by this effort?)

Milestone Owner Resources Needed 1. Completion and approval of change request document Robert Kerwin 2. Phase II modifications available in INTG Robert Kerwin 3. Successful completion of integration testing Lorie Chance 4. Go-live of Phase II in production Jeffrey O’Keefe 5. Communication to user community Lorie Chance

12. Roles & Responsibilities

(Who are functionally and technically responsible for and interested in this effort?)

Project Role Project Responsibility Name Title, Department Estimated Time Commitment

Customer Management Sponsor

Provides authority in the functional area to work on this effort and maintains priority of functional expertise needed by ITS

Andrew Cullen Associate VP,Budget, Planning & Analysis: Budget Office

Minimal

ITS Management Sponsor

Provides technical authority and guidance and maintains ITS effort priorities

Moira Gerety

Director, ITS Computing Services

Minimal

Functional Lead Defines, plans, controls, and leads the work of the functional participants. Defines and maintains effort requirements

Lorie Chance Information Systems Project Director: HSC Budget Office

Ongoing

Technical Lead Defines, plans, controls, and leads the work of the technical participants. Coordinates integration with existing systems.

Jeffrey O’Keefe Manager, Applications Programming: ITS Computing Services

Ongoing

BPOs / Steering Committee

Key Business Process Owners participating in and/or affected by this effort

Doloritas Romero Duane Arruti Edwin Baker Julian Sandoval Kate Moore Kristin Gates Norma Allen Raquel Martinez Robert Fondino Vahid Staples Venessa Hawker

Univ Budgets Administrator: Budget Office Associate VP: HR Staff Compensation Manager: HR Associate Controller: FSM Financial Officer: Provost General Admin Graduate Programs Director, School of Medicine Finance Assoc Dir: Budget Office Fclty Affrs & Svcs Director: Provost Office Chief Budget & Fin Officer: HSC Financial Analyst: Budget Office Assoc Dir,Univ Budget Opns: HSC Budget Office

Minimal

Work Team Provide the knowledge and skills to complete the effort requirements.

Randy Eldredge Robert Kerwin Robert Barraza

Analyst/Programmer III; ITS Computing Services Consultant

Ongoing

IT Security Security approvals Jeff Gassaway

Administrator, University Information Security

Minimal

Page 5: Technical Change Request & Design Specificationsit.unm.edu/dashboard/BudgetPlannerPhase2.pdf · batch mode via AppWorx, thereby avoiding the timeout issue. 1.1.1.4 Modifications to

Budget Planner Phase 2 Enhancements Technical Change Request.doc Page 5 of 31

Michael Carr Director,,Information Assurance

Other Stakeholders Other stakeholders who should be consulted

Page 6: Technical Change Request & Design Specificationsit.unm.edu/dashboard/BudgetPlannerPhase2.pdf · batch mode via AppWorx, thereby avoiding the timeout issue. 1.1.1.4 Modifications to

Budget Planner Phase 2 Enhancements Technical Change Request.doc Page 6 of 31

13. Technical Change Request Approvals (Those providing approval for Part 1, the Technical Change Request)

Name Title, Department Signature Customer Management Sponsor

Andrew Cullen Associate VP,Budget, Planning & Analysis: Budget Office

IT Management Sponsor

Moira Gerety Director, ITS Computing Services

BPOs / Steering Committee

Doloritas Romero

Univ Budgets Administrator: Budget Office

Duane Arruti Associate VP: Human Resources

Edwin Baker Staff Compensation Manager: Human Resources

Julian Sandoval Associate Controller: FSM

Kate Moore Financial Officer: Provost General Administrative Graduate Programs

Kristin Gates Director, School of Medicine Finance

Norma Allen Assoc Dir: Budget Office

Raquel Martinez Fclty Affrs & Svcs Director: Provost Office

Robert Fondino

Chief Budget & Fin Officer: HSC

Vahid Staples

Financial Analyst: Budget Office

Vanessa Hawker Assoc Dir,Univ Budget Opns: HSC Budget Office

Functional Lead

Lorie Chance Information Systems Project Director: HSC Budget Office

Technical Lead

Jeffrey O’Keefe Manager, Applications Programming: ITS Computing Services

Date Reviewed: ___/___/______ Comments:

Page 7: Technical Change Request & Design Specificationsit.unm.edu/dashboard/BudgetPlannerPhase2.pdf · batch mode via AppWorx, thereby avoiding the timeout issue. 1.1.1.4 Modifications to

Budget Planner Phase 2 Enhancements Technical Change Request.doc Page 7 of 31

Part 2: Design Specifications 14. Technical Design Specification Sections Included

Section 1: Requirements Specifications Section 2: Input File Specifications Section 3: Oracle and Non-Oracle Object Information Section 4: Banner Job Submission Information Section 5: Appworx Job Scheduling Information Section 6: Oracle Forms Information Section 7: Oracle Reports Information Section 8: Quality Assurance Information

SECTION 1 REQUIREMENTS SPECIFICATIONS

1.1 Functional:

1.1.1 Budget Development Reports

1.1.1.1 Index Out Of Balance Report

1.1.1.1.1 Correct Index Out Of Balance report The Index Out Of Balance report disagrees with the Budget Development Working report when run for the same organization. In most cases, the Index Out of Balance report shows no indices that are out of balance, whereas the Budget Development Working report shows indices that do not net to zero.

1.1.1.1.2 Remove lock requirement from Index Out Of Balance report Currently, the Index Out of Balance report requires that organizations must be locked prior to running. This feature makes it difficult for users to ensure that all indices are balanced prior to locking the organization. The users must wait until after the organization is locked to determine if any indices are out of balance, then they must be unlocked, corrected and re-locked. The lock requirement will be removed from the Index Out Of Balance report.

1.1.1.2 On Operating Budget Summary, show 1901 and whether it nets to zero Account code 1901 (budgeted balance change) will be displayed on the Operating Budget Summary to ensure that budget carry-over that is intended to be expensed in the upcoming fiscal year is figured into the current year’s budget balance.

1.1.1.3 Budget Development Working Report Performance The Budget Development Working Report currently runs slow when run for a level 1 or 2 organization. As a result, the Self-Service session will time out before the report completes. This report will be set up with the option of running in batch mode via AppWorx, thereby avoiding the timeout issue.

1.1.1.4 Modifications to All Reports

1.1.1.4.1 Organization and FOP Parameters for Running Reports Currently, all reports require an organization in order to run. Change parameter logic on all reports to run by index and/or organization and/or program and/or fund. At least one of the four must be specified; more than one may be entered. Organization will not be a required parameter on the Budget Development Working Reports.

1.1.1.4.2 Fund and Program Hierarchies and Data-enterable FOPA’s

Currently, the reports are set up to use the org hierarchy; the same logic needs to be built into the fund and program parameters. For fund and program, the report should return the entered fund/program plus all funds/programs below them in the hierarchy. The requirement to input only data-enterable orgs/funds/program will also be removed.

Page 8: Technical Change Request & Design Specificationsit.unm.edu/dashboard/BudgetPlannerPhase2.pdf · batch mode via AppWorx, thereby avoiding the timeout issue. 1.1.1.4 Modifications to

Budget Planner Phase 2 Enhancements Technical Change Request.doc Page 8 of 31

1.1.1.4.3 Display of Zeros

Reports must not display line items with only zero amounts.

1.1.1.4.4 Default Budget ID, Phase and Chart Budget ID and phase on all reports will default to current budget year and current open work phase. If no work phase is open, the phase will default to the most recent approved phase. Chart defaults to U. Users will still have the ability to look up these fields or change them directly.

1.1.1.5 Budgeted Account Code Report Comment The Budgeted Account Code report will display comments for any account code if they exist.

1.1.2 Budget Development Worksheet

1.1.2.1 Worksheet Navigation to Index Entry Page A link will be added to the Budget Worksheet page to navigate back to the Create Budget Worksheet page. The link will be inserted near the bottom and top of the Budget Worksheet. The data from the previous query will be retained in the Create Budget Worksheet after navigation back from the Budget Worksheet.

1.1.2.2 Inclusion of Salaries in Summary Totals

The Budget Worksheet will pull salaries (account type 61) from Salary Planner and display them in the summary block at the bottom of the worksheet. The proposed budget amount for Operating Expense Labor will be a hyperlink that goes back to Salary Planner to the position distribution.

1.1.2.3 Account Code Lookup Problem The account code lookup from the Budget Worksheet/new row section does not return account codes having a data-entry indicator of ‘B’ (budget only). The account code can be entered directly. Correct account code lookup to pull account code 80SA Salary Adjustments. Other account codes having a data-entry indicator of ‘B’ will not be pulled up (this is current state).

Page 9: Technical Change Request & Design Specificationsit.unm.edu/dashboard/BudgetPlannerPhase2.pdf · batch mode via AppWorx, thereby avoiding the timeout issue. 1.1.1.4 Modifications to

Budget Planner Phase 2 Enhancements Technical Change Request.doc Page 9 of 31

1.1.2.4 Default Records Returned from Lookup Set all lookups to return 100 records by default. Other record count selections will still be allowed. Results returned will be sorted in ascending order by account code.

1.1.2.5 Round budget change amount to whole dollars On budget worksheet, round change amount and proposed budget fields (normal rounding) to whole dollars. The rounded amounts are both displayed and stored in tables.

1.1.2.6 Correct Budget Refresh Process Exclude account codes 1901 and 1903 from the budget refresh process.

1.1.2.7 Budget Phase The budget phase dropdown list will contain only open budget phases; projection phases will not be displayed in the list. Reference requirement 1.1.6.4.1.

1.1.3 Salary Planner Reports

1.1.3.1 Salary Planner Working Report

1.1.3.1.1 Run by Index and Fund The Salary Planner Working Report currently runs by organization only. This report will be modified to run by index, organization or organization/fund combination.

1.1.3.1.2 Include or Exclude Vacant Positions Option Provide an option to include or exclude vacant positions on the Salary Planner Working Report. Default should be Yes (include vacant positions).

1.1.3.1.3 Exclude FTE Outside Hiring Organization Exclude FTE for people outside the hiring organization on the Salary Planner Working Report. Persons will show up on report if they are paid from the org, but their FTE will not be displayed and will not be counted toward the total.

1.1.3.2 Update Exception Report for FY10 guidelines Update Exception Report for the following edits: 1. Check for labor distributions that do not total 100% (Salary Planner allows users to set a distribution that does not total

100%). 2. Remove error check for contract employees on report, contract employees will be separate scenario. Certain guidelines can be changed in FTMSDAT by the user. Other FY10 guidelines to be determined might result in further modifications to this report.

1.1.3.3 Default Budget ID, Phase and Chart Budget ID and phase on all Salary Planner reports will default to current budget year and current open work phase. If no work phase is open, the phase will default to the most recent approved phase. Chart defaults to U. Users will still have the ability to look up these fields or change them directly.

1.1.4 Salary Planner Worksheet

1.1.4.1 Labor Distribution Index-Centricity On the Account Distribution screen (accessed by clicking on a labor distribution hyperlink on the Job/Position Labor Distribution screen), change the FOPAL input to be index-centric: 1. Default the FOPA elements to those associated with the input index 2. Disable Fund, Organization, Program, Activity and Location Fields (display only); only index and account are

enterable by user 3. Perform an index expansion, FOAPAL validation and page refresh after initial press of the Save button and display a

validation message

Page 10: Technical Change Request & Design Specificationsit.unm.edu/dashboard/BudgetPlannerPhase2.pdf · batch mode via AppWorx, thereby avoiding the timeout issue. 1.1.1.4 Modifications to

Budget Planner Phase 2 Enhancements Technical Change Request.doc Page 10 of 31

4. Perform actual save after the second press of the Save button The Default From Index button functionality will still populate the FOPAL elements from the index as before (see 1.1.4.2).

1.1.4.2 Account Code Blanking

Do not blank account code when an index is changed on the Account Distribution screen and the Default From Index button is pressed. The account code field is enterable by the user.

1.1.4.3 Labor Distribution Amount/Percentage Edit

Disallow zero on percentage or amount on position or job labor distribution. Zero amounts or percentages for job/position distributions cause load problems.

1.1.4.4 Organization Security and Lock Functionality

Currently, a user cannot lock/unlock orgs at a lower level, only the current level. For example, if a user has security access to a level 3 organization, he can lock/unlock the level 3 organization, but not a level 4, 5 or lower organization that belongs to his level 3 organization. The organization lock should allow a user to lock or unlock the organization for which access is granted or any organization below it in the hierarchy. The Banner Access Request will be changed so that if a user changes organizations, Budget Office will not get the request since access to Budget Planner is already granted.

1.1.4.5 Default Records Returned from Lookup Set all lookups to return 100 records by default rather than the current 10 records. Other record count selections will be allowed as before.

1.1.4.6 Salary Rounding

1.1.4.6.1 Position Budget/Distribution Round position budget distribution amounts (normal rounding) to the nearest whole dollar. Amounts must be stored in tables as rounded amounts.

1.1.4.6.2 Job Salary Rate/Distribution Round job salary rate to whole cents. Amounts will be stored in tables as dollars/cents.

1.1.4.7 Job Detail Fields

Disable updates to fields on job detail screen, except for proposed appointment percent. Disabled fields should appear grayed out to provide users with a visual cue that the fields do not allow entry. The mass change fields will be removed, preventing users from entering a mass change amount or percent. In addition, thousands separator commas will be displayed in the following dollar amount fields: • Annual Salary • Total Change Amount • Estimated Fiscal Year Budget

Page 11: Technical Change Request & Design Specificationsit.unm.edu/dashboard/BudgetPlannerPhase2.pdf · batch mode via AppWorx, thereby avoiding the timeout issue. 1.1.1.4 Modifications to

Budget Planner Phase 2 Enhancements Technical Change Request.doc Page 11 of 31

1.1.4.8 Disable Changes to Base Amounts On position detail screen, disable changes to base amounts. Disabled fields should appear grayed out to provide users with a visual cue that the fields do not allow entry.

Page 12: Technical Change Request & Design Specificationsit.unm.edu/dashboard/BudgetPlannerPhase2.pdf · batch mode via AppWorx, thereby avoiding the timeout issue. 1.1.1.4 Modifications to

Budget Planner Phase 2 Enhancements Technical Change Request.doc Page 12 of 31

1.1.4.9 Disable Changes to Extracted Jobs On Employee Detail Screen Disable all inputs on the Employee Detail screen, i.e. Proposed Appointment Percent, Annual Salary Increase Percent, Annual Salary Increase Amount, Percent and Amount. Changes to these data are normally made on other screens; allowing users to input changes here results in confusion or inconsistent results. See screen shot below.

1.1.4.10 Correct Salary Planner Refresh Process When a change to a job title is made via EPAF while salary planning is in process, the refresh does not update the proposed title in the extract with the new title in some (but not all) cases. As a result, the old title is re-uploaded to Banner. This defect will be located, corrected and reported to Sungard as appropriate.

1.1.4.11 Force Distributions to 100% Do not allow users to leave the distribution screens (job or position) if the sum of the distributions does not equal 100%. The Save button will be disabled until the distribution total equals 100%.

1.1.4.11.1 Enterable Fields The labor distribution section will allow the Index, Account and Percentage to be input.

1.1.4.11.2 Add/Delete Distribution Records The labor distribution section will contain an Add Record button that will allow the user to dynamically add distribution records. Each row of the distribution will also contain a delete button that will allow the user to delete the row from the distribution.

1.1.4.12 Exclusion of Pooled Jobs from Extract The Salary Planner refresh process will be modified to exclude pooled jobs.

1.1.5 Product Maintenance

1.1.5.1 Apply Sungard Patch pcms_dfct90919_bwf70300 The patch to Finance Self-Service, pcms_dfct90919_bwf70300, will be applied. Using the browser back button does not reverse calculated but un-posted changes made to the budget worksheet, although the changes appear on screen as if a reversal had successfully occurred. When changes are made to the subsequent screen and saved, the changes written to the

Page 13: Technical Change Request & Design Specificationsit.unm.edu/dashboard/BudgetPlannerPhase2.pdf · batch mode via AppWorx, thereby avoiding the timeout issue. 1.1.1.4 Modifications to

Budget Planner Phase 2 Enhancements Technical Change Request.doc Page 13 of 31

database includes the first set of changes. This patch causes the application to save only the amounts on the current screen. Use of the Back button is still not recommended.

1.1.5.2 Re-apply UNM Modifications This patch impacts the Budget Worksheet, therefore, all UNM modifications to the Budget Worksheet will need to be re-applied to the patched version of the impacted modules. Reference the following UNM change requests: BUCR_002 SSB-BP COA Element Lookup Enhancements BUCR_003 SSB-BP Index-Centricity Enhancements BUCR_008 SSB-BP Business Process Support

1.1.6 Budget Projections

1.1.6.1 Budget Planner Menu Item A new link will be added to the Budget Planner menu. The link text will be “Create Projected Actuals Worksheet.” The description will be “Create financial projections through current fiscal year end via a projected actuals worksheet.”

1.1.6.2 Create Projections Worksheet Query Page After clicking on the Create Projected Actuals Worksheet hyperlink, the initial query setup page will appear. This page will allow the user to create a new query or retrieve an existing query. The saved queries dropdown will only contain budget projections queries, not budget worksheet queries.

1.1.6.3 Create Projected Actuals Worksheet Parameter Page After the Create Query button is pressed, the parameters page will appear. Similar to the budget worksheet parameters page, this page will allow the user to select the fiscal year/period, comparison fiscal year/period, chart and index. This page will be index-centric: 1. Default the FOPA elements to those associated with the input index 2. Fund, Organization, Program, Activity and Location Fields will be shown, but will not be data-enterable. 3. Perform an index expansion, FOAPAL validation and page refresh after initial press of the Save button and display a

validation message

Page 14: Technical Change Request & Design Specificationsit.unm.edu/dashboard/BudgetPlannerPhase2.pdf · batch mode via AppWorx, thereby avoiding the timeout issue. 1.1.1.4 Modifications to

Budget Planner Phase 2 Enhancements Technical Change Request.doc Page 14 of 31

4. Perform actual save after the second press of the Save button

1.1.6.3.1 Projections Phases The budget phases drop-down list on the projections parameter page will have only projection phases, not budget phases. Reference requirement 1.1.2.7.

1.1.6.3.2 Default Budget ID, Phase and Chart Budget ID and phase will default to current budget year and current open work phase. If no work phase is open, the phase will default to the most recent approved phase. Chart defaults to U. Users will still have the ability to look up these fields or change them directly.

1.1.6.4 Projections Detail Page After the projections parameter page is submitted, the system will display the projections report which will allow the user to input new projections amounts. The report will contain the following columns, listed by account:

1. Account Code 2. Account Title 3. Adopted Budget 4. Adjusted Budget 5. YTD Actuals 6. Projections (input field) 7. FY Projected Balance (computed field) 8. Commitments

Page 15: Technical Change Request & Design Specificationsit.unm.edu/dashboard/BudgetPlannerPhase2.pdf · batch mode via AppWorx, thereby avoiding the timeout issue. 1.1.1.4 Modifications to

Budget Planner Phase 2 Enhancements Technical Change Request.doc Page 15 of 31

1.1.7 Report Optimization Reports developed in the initial release of Budget Planner will be analyzed and optimized for faster run times. The reports affected will be:

1. Projections Working Report 2. Budget to Projected Actuals Report 3. Budget Year Financial Projections Report 4. Unrestricted Financial Projections by Exhibit Report 5. Salary Planner Working Report 6. Salary Planner Exception Report 7. Vacant Positions Report 8. Budget Development Working Report 9. Budget Development Working Report Comparison 10. Operating Budget Summary Report 11. Index Out of Balance Report 12. Organization Summary Report 13. Budgeted Account Code Report

1.2 Performance: No performance requirements have been defined.

1.3 Environmental:

No environmental requirements have been defined.

Page 16: Technical Change Request & Design Specificationsit.unm.edu/dashboard/BudgetPlannerPhase2.pdf · batch mode via AppWorx, thereby avoiding the timeout issue. 1.1.1.4 Modifications to

Budget Planner Phase 2 Enhancements Technical Change Request.doc Page 16 of 31

SECTION 2 INPUT FILE SPECIFICATIONS

No input file required.

Page 17: Technical Change Request & Design Specificationsit.unm.edu/dashboard/BudgetPlannerPhase2.pdf · batch mode via AppWorx, thereby avoiding the timeout issue. 1.1.1.4 Modifications to

Budget Planner Phase 2 Enhancements Technical Change Request.doc Page 17 of 31

SECTION 3 ORACLE AND NON-ORACLE OBJECT INFORMATION

3.1 UNIX Shell Scripts:

None required.

3.2 Oracle Tables:

None required.

3.3 Oracle Constraints / Indexes / Triggers: None required.

3.4 Oracle Stored Functions / Procedures / Packages:

Name: BWFKBRPT Title: Report Parameter Pages

Description: A database package to submit Oracle Reports File Name: /UNM/finweb/dbprocs/bwfkbrpt.sql

Name: BWFKBWSH Title: Budget Worksheet Page

Description: A database package for Budget Worksheet File Name: /UNM/finweb/dbprocs/bwfkbwsh.sql

Name: BWPKSJOB Title: Salary Planner Employee Job Information

Description: Provides web pages for Salary Planner employee and job information. File Name: /UNM/finweb/dbprocs/bwpksjob.sql

Name: BWPKSPLD Title: Salary Planner Labor Distribution

Description: Provides web pages for Salary Planner labor distribution. File Name: /UNM/payweb/dbprocs/ bwpkspld.sql

Name: BWPKSMEX Title: Salary Planning/Position Budgeting Multiple Extracts

Description: Multiple extract functionality for Budget Planner File Name: /UNM/payweb/dbprocs/ bwpksmex.sql

Name: BWPKSPOS Title: Salary Planner Position Budgeting

Description: Provides web pages for Salary Planner position budgeting. File Name: /UNM/payweb/dbprocs/ bwpkspos.sql

Name: BWFKBPLN Title: UNM Budget Planner Functionality

Description: Utility package for Budget Planner. File Name: /UNM/finweb/dbprocs/ bwfkbpln.sql

Name: BWFKPROC Title: Lookup Utility Package

Description: Provides lookup functionality for Budget Planner and Finance Self-Service. File Name: /UNM/finweb/dbprocs/ bwfkproc.sql

Name: BWFKBDWS Title: Budget Development Worksheet Support

Description: Provides functions/procedures to support the budget development worksheet File Name: /UNM/finweb/dbprocs/ bwfkbdws.sql

Name: BWPKSALA Title: Salary Planner Scenario Creation

Page 18: Technical Change Request & Design Specificationsit.unm.edu/dashboard/BudgetPlannerPhase2.pdf · batch mode via AppWorx, thereby avoiding the timeout issue. 1.1.1.4 Modifications to

Budget Planner Phase 2 Enhancements Technical Change Request.doc Page 18 of 31

Description: Creates scenarios for Salary Planner File Name: /UNM/payweb/dbprocs/bwpksala.sql

Name: FZKBPRF Title: UNM Budget Refresh Package

Description: Refine the Budget phases after initial creation. File Name: /UNM/finance/dbprocs/fzkbprf.sql

Name: NBKBUDG Title: Salary Planner Utility Package

Description: Common functions and procedures for Salary Planning. File Name: /UNM/posnctl/dbprocs/nbkbudg.sql

Name: FZKPRWR Title: Projections Working Report

Description: Package to create the Projections Working Report. File Name: /UNM/finance/dbprocs/fzkprwr.sql

Name: FZKPBTA Title: Budget to Projected Actuals Report

Description: Package to create the Budget to Projected Actuals Report File Name: /UNM/finance/dbprocs/fzkpbta.sql

Name: FZKPRBY Title: Budget Year Financial Projections Report

Description: Package to create the Budget Year Financial Projections Report. File Name: /UNM/finance/dbprocs/fzkprby.sql

Name: FZKPREX Title: Unrestricted Financial Projections by Exhibit Report

Description: Package to create the Unrestricted Financial Projections by Exhibit Report File Name: /UNM/finance/dbprocs/fzkprex.sql

Name: FZKSPWR Title: Salary Planner Working Report

Description: Package to create the Salary Planner Working Report File Name: /UNM/finance/dbprocs/fzkspwr.sql

Name: FZKSPER Title: Salary Planner Exception Report

Description: Package to create the Salary Planner Exception Report File Name: /UNM/finance/dbprocs/fzksper.sql

Name: FZKUPOS Title: Vacant Positions Report

Description: Package to create the Vacant Positions Report File Name: /UNM/finance/dbprocs/fzkupos.sql

Name: FZKBCUR Title: Budget Development Working Report

Description: Package to create the Budget Development Working Report File Name: /UNM/finance/dbprocs/fzkbcur.sql

Name: FZKBUDG Title: Budget Development Working Report Comparison

Description: Package to create the Budget Development Working Report Comparison File Name: /UNM/finance/dbprocs/fzkbudg.sql

Name: FZKOPLR Title: Operating Budget Summary Report

Description: Package to create the Operating Budget Summary Report File Name: /UNM/finance/dbprocs/fzkoplr.sql

Name: FZKBIOB

Page 19: Technical Change Request & Design Specificationsit.unm.edu/dashboard/BudgetPlannerPhase2.pdf · batch mode via AppWorx, thereby avoiding the timeout issue. 1.1.1.4 Modifications to

Budget Planner Phase 2 Enhancements Technical Change Request.doc Page 19 of 31

Title: Index Out of Balance Report Description: Package to create the Index Out of Balance Report File Name: /UNM/finance/dbprocs/fzkbiob.sql

Name: FZKOSRP Title: Organization Summary Report

Description: Package to create the Organization Summary Report File Name: /UNM/finance/dbprocs/fzkosrp.sql

Name: FZKBAIA Title: Budgeted Account Code Report

Description: Package to create the Budgeted Account Code Report File Name: /UNM/finance/dbprocs/fzkbaia.sql

3.5 Oracle Views: None required.

3.6 Pro-Cobol Programs: None required.

3.7 Pro-C Programs: None required.

3.8 Impact on Database Tables:

Table Name Schema New Select Insert Update Delete FZTPRBY UNM X X X X X FZTPRB1 UNM X X X X X FZTPREX UNM X X X X X FZTPRE1 UNM X X X X X FZBPROJ UNM X X X X X FZTPROJ UNM X X X X X FZTPRWR UNM X X X X X FZTPBTA UNM X X X X X FZTPBT1 UNM X X X X X FZTSPWR UNM X X X X FZTSPER UNM X X X X FZTUPOS UNM X X X X FZTBCUR UNM X X X X FZTBUDG UNM X X X X FZTOPLR UNM X X X X FZTBIOB UNM X X X X FZTOSRP UNM X X X X FZTBAIA UNM X X X X

3.9 Output Files:

None.

3.10 Exception Handling: None required.

Page 20: Technical Change Request & Design Specificationsit.unm.edu/dashboard/BudgetPlannerPhase2.pdf · batch mode via AppWorx, thereby avoiding the timeout issue. 1.1.1.4 Modifications to

Budget Planner Phase 2 Enhancements Technical Change Request.doc Page 20 of 31

SECTION 4 BANNER JOB SUBMISSION INFORMATION No Banner job submission changes required.

Page 21: Technical Change Request & Design Specificationsit.unm.edu/dashboard/BudgetPlannerPhase2.pdf · batch mode via AppWorx, thereby avoiding the timeout issue. 1.1.1.4 Modifications to

Budget Planner Phase 2 Enhancements Technical Change Request.doc Page 21 of 31

SECTION 5 APPWORX JOB SCHEDULING INFORMATION No AppWorx scheduling required.

Page 22: Technical Change Request & Design Specificationsit.unm.edu/dashboard/BudgetPlannerPhase2.pdf · batch mode via AppWorx, thereby avoiding the timeout issue. 1.1.1.4 Modifications to

Budget Planner Phase 2 Enhancements Technical Change Request.doc Page 22 of 31

SECTION 6 ORACLE FORMS INFORMATION None required.

Page 23: Technical Change Request & Design Specificationsit.unm.edu/dashboard/BudgetPlannerPhase2.pdf · batch mode via AppWorx, thereby avoiding the timeout issue. 1.1.1.4 Modifications to

Budget Planner Phase 2 Enhancements Technical Change Request.doc Page 23 of 31

SECTION 7 ORACLE REPORTS INFORMATION

7.1 Reports 7.1.1 Projections Working Report

Title: UNM Projections Working Report

Description: Reports projected actuals by index or any combination of fund, organization, and/or program summarized by account.

Submitted From: Finance Self-Service/Budget Planner File Name: /UNM/finance/forms/fzrprwr.sql

Selection Criteria: Field Name Default Value

Chart of Accounts [U] Budget ID Budget Phase Fiscal Year Fiscal Period Index Optional if Organization is specified. Organization Optional if Index is specified Fund Optional Program Optional

Header Data: Field Name Justification

( Left, Center, or Right ) “University of New Mexico” Center “Projections Working Report” Center Fiscal Year Center Level 2 Organization Left Organization, Organization Title Left Fund (opt) Program (opt)

Body Data: Field Name Displayed When

Organization Code Always Organization Title Always Account Type Always Account Code/Title Always Current Year Revised Budget Always Current Year YTD Actuals Always Projected Year-end Actuals Always Previous Year Year-end Actuals Always Variance Dollars Always Variance Percent Always

Sorting: Field Name Ascending or Descending

Organization Code Ascending Account type Ascending Account code Ascending

Totaling: Field Name Total Type

( sub-total at, total at, or report total ) All Sub-total by revenues/expenditures All Summary by organization/revenue/expenses All Report total

Page 24: Technical Change Request & Design Specificationsit.unm.edu/dashboard/BudgetPlannerPhase2.pdf · batch mode via AppWorx, thereby avoiding the timeout issue. 1.1.1.4 Modifications to

Budget Planner Phase 2 Enhancements Technical Change Request.doc Page 24 of 31

Page Breaks: Field Name

Footer Data: Field Name Justification

( Left, Center, or Right ) Report run date Left Page number/total pages Center

7.1.2 Budget to Projected Actuals Report

Title: Budget to Projected Actuals Report

Description: Reports projected actuals by index or any combination of fund, organization, and/or program summarized by account type.

Submitted From: Finance Self-Service/Budget Planner File Name: /UNM/finance/forms/fzrpbta.sql

Selection Criteria: Field Name Default Value

Chart of Accounts [U] Budget ID Budget Phase Fiscal Year Fiscal Period Index Optional if Organization is specified. Organization Optional if Index is specified Fund Optional Program Optional

Header Data: Field Name Justification

( Left, Center, or Right ) “University of New Mexico” Center Fiscal Year/Period Center Budget Code/Budget Year Center Level 2 Organization Left Organization, Organization Title Left Fund (opt) Left Program (opt) Left Index (opt) Left

Body Data: Field Name Displayed When

Account Title Always Current Year Revised Budget Always YTD Actuals Always Projected Year-end Actuals Always Previous Year-end Actuals Always Proposed FTE Always Budget to Projections Variance (Dollars) Always Budget to Projections Variance (Percent) Always

Sorting: Field Name Ascending or Descending

Account type Ascending Account code Ascending

Totaling: Field Name Total Type

( sub-total at, total at, or report total ) All, except percent Sub-total by Account Type All, except percent Report total

Page 25: Technical Change Request & Design Specificationsit.unm.edu/dashboard/BudgetPlannerPhase2.pdf · batch mode via AppWorx, thereby avoiding the timeout issue. 1.1.1.4 Modifications to

Budget Planner Phase 2 Enhancements Technical Change Request.doc Page 25 of 31

Page Breaks: Field Name

Footer Data: Field Name Justification

( Left, Center, or Right ) Report Date Left Page Center

7.1.3 Budget Year Financial Projections Report

Title: Budget Year Financial Projections

Description: Reports projected actuals summarized by organization. Submitted From: Finance Self-Service/Budget Planner

File Name: /UNM/finance/dbprocs/fzrprby.sql

Selection Criteria: Field Name Default Value Chart of Accounts U Budget ID Budget Phase Fiscal Year Fiscal Period Organization

Header Data: Field Name Justification

( Left, Center, or Right ) “University of New Mexico” Center “Budget Year Financial Projections” Center Fiscal Year Center Budget Code/Budget Phase Center Organization Code/Title Center

Body Data: Field Name Displayed When

Account Title Always Current Year Unrestricted Budget Always YTD Actuals, Unrestricted Always YTD Actuals, Restricted Always YTD Actuals, Total Always Projected Fiscal Year Total, Unrestricted Always Projected Fiscal Year Total, Restricted Always Projected Fiscal Year Total, Total Always Budget Variance, Dollars Always

Sorting: Field Name Ascending or Descending

Account Type Ascending Account Code Ascending

Totaling: Field Name Total Type

( sub-total at, total at, or report total ) All Sub-total by Account Level 1 All Sub-total by Account Type Level 2 All Total All Total All Report Total

Page Breaks: Field Name

Page 26: Technical Change Request & Design Specificationsit.unm.edu/dashboard/BudgetPlannerPhase2.pdf · batch mode via AppWorx, thereby avoiding the timeout issue. 1.1.1.4 Modifications to

Budget Planner Phase 2 Enhancements Technical Change Request.doc Page 26 of 31

Footer Data: Field Name Justification ( Left, Center, or Right )

Run Date Left Page/Number of pages Center

7.1.4 Financial Projections by Exhibit Report

Title: UNM Financial Projections by Exhibit

Description: Reports main campus current unrestricted financial projections summarized by exhibit. Submitted From: Finance Self-Service/Budget Planner

File Name: /UNM/{system name}/forms/

Selection Criteria: Field Name Default Value Chart of Accounts U Budget ID Budget Phase Fiscal Year Fiscal Period Organization

Header Data: Field Name Justification

( Left, Center, or Right ) “University of New Mexico” Center

“Main Campus Current Unrestricted Financial Projections by Exhibit”

Center

Fiscal Year/Fiscal Period Center Budget Code/Budget Phase Center

Organization Level/Organization Code/Organization Title

Center

Body Data: Field Name Displayed When

Account Type Level 1 Always Account Title Always I&G Always Student Social and Cultural Always Research Always Public Service Always Internal Services Always Student Aid Always Auxiliaries Always Athletics Always Total Always

Sorting: Field Name Ascending or Descending

Account type Ascending Account code Ascending

Totaling: Field Name Total Type

( sub-total at, total at, or report total ) All Sub-total by Account Type Level 1 All Sub-total by Account Type Level 1 All Total All Total All Total All Report Total

Page Breaks: Field Name

Page 27: Technical Change Request & Design Specificationsit.unm.edu/dashboard/BudgetPlannerPhase2.pdf · batch mode via AppWorx, thereby avoiding the timeout issue. 1.1.1.4 Modifications to

Budget Planner Phase 2 Enhancements Technical Change Request.doc Page 27 of 31

Footer Data: Field Name Justification

( Left, Center, or Right ) Run Date Left Page/Number of pages Center

Page 28: Technical Change Request & Design Specificationsit.unm.edu/dashboard/BudgetPlannerPhase2.pdf · batch mode via AppWorx, thereby avoiding the timeout issue. 1.1.1.4 Modifications to

Budget Planner Phase 2 Enhancements Technical Change Request.doc Page 28 of 31

SECTION 8 QUALITY ASSURANCE INFORMATION 8.1 Test Plan

8.1.1 Phased Approach As modifications are completed, they will be individually unit-tested then migrated to the INTG environment. Functional users will perform tests in INTG and report defects to the development team on an ongoing basis.

8.1.2 Tools Tests will be run manually on the Budget Planner Self-Service module, and results will be validated in Budget Planner or directly in the database using TOAD. INB will also be used to change data as needed for test setup.

8.2 Test Case Overview:

Name: Worksheet Navigation to Index Entry Page Description: Ensures that the links back to the Create Budget Worksheet page works correctly.

Name: Inclusion of Salaries in Summary Totals

Description: Ensures that the summary block of the Budget Worksheet displays salaries (account type 61).

Name: Base Salary Link to Salary Planner

Description: Ensures that the base amount for the salary in the summary block is a hyperlink that goes back to Salary Planner.

Name: Default Records Returned from Lookup (Budget)

Description: Verifies that all lookups in Budget Development (index, account code, etc.) has the number of records returned value set to 100 by default. Other values in the list are selectable.

Name: Budget Change Amount Rounding

Description: Ensures that amounts (change/proposed) are rounded to whole dollars on the worksheet page and in the database.

Name: Correct Budget Refresh Process

Description: Verifies that the budget refresh process excludes account codes 1901 and 1903.

Name: Labor Distribution Index-Centricity

Description: Ensures that the input of accounting information for labor distributions follows UNM’s standard of allowing input of only index and account code, not individual FOAPAL’s.

Name: Distribution Account Code Blanking

Description: Verifies that the Default From Index button does not result in the account code field being nulled.

Name: Labor Distribution Amount/Percentage Edit

Description: Verifies that zero is not allowed on labor distribution percent or amount.

Name: Organization Security and Lock Functionality

Description: Validates that the organization lock functions correctly with respect to the organization hierarchy.

Name: Default Records Returned from Lookup (Salary Planner)

Description: Ensures that all lookups within Salary Planner are set to return 100 records by default. Other return count values are selectable.

Page 29: Technical Change Request & Design Specificationsit.unm.edu/dashboard/BudgetPlannerPhase2.pdf · batch mode via AppWorx, thereby avoiding the timeout issue. 1.1.1.4 Modifications to

Budget Planner Phase 2 Enhancements Technical Change Request.doc Page 29 of 31

Name: Position Budget/Distribution Rounding

Description: Ensures that position budget distribution amounts are rounded to whole dollars and that stored amounts are rounded to whole dollars.

Name: Job Detail Fields Disabled

Description: Verifies that all fields on the Job Detail page except proposed appointment percent do not allow input.

Name: Base Amounts Changes

Description: Ensures that base amount fields on the position detail screen do not allow input.

Name: Changes to Extracted Jobs On Employee Detail Screen Description: Ensures that all fields on the Employee Detail screen do not allow input.

Name: Salary Planner Refresh Process

Description: Validates that changes made to job title via EPAF when salary planning in process are correctly updated in the Salary Planner system.

Name: Distribution Total Edit

Description: Ensures that users cannot save job or position distributions that do not total to 100%.

Name: Salary Planner Extract (Pooled Positions)

Description: Verifies that the Salary Planner extract process does not extract pooled positions into Salary Planner.

Name: Budget Worksheet Phase I Modifications

Description: Ensures that all changes made to the Budget Worksheet in Phase I are re-implemented following the application of patch pcms_dfct90919_bwf70300.

Page 30: Technical Change Request & Design Specificationsit.unm.edu/dashboard/BudgetPlannerPhase2.pdf · batch mode via AppWorx, thereby avoiding the timeout issue. 1.1.1.4 Modifications to

Budget Planner Phase 2 Enhancements Technical Change Request.doc Page 30 of 31

Part 3: Implementation Approvals 15. Quality Assurance and Implementation Approvals

(Those providing acceptance of effort deliverables and approval to implement in production) Name Title, Department Signature

Business Process Owners

Norma Allen Assoc Dir: Budget Office

Vanessa Hawker Assoc Dir,Univ Budget Opns: HSC Budget Office

IT Management Sponsor

Bonnie Young Executive Project Director: ITS Computing Services

Functional Lead

Lorie Chance Information Systems Project Director: HSC Budget Office

Technical Lead

Jeffrey O’Keefe Manager, Applns Programming: ITS Computing Services

Date Reviewed: ___/___/______ Comments:

Page 31: Technical Change Request & Design Specificationsit.unm.edu/dashboard/BudgetPlannerPhase2.pdf · batch mode via AppWorx, thereby avoiding the timeout issue. 1.1.1.4 Modifications to

Budget Planner Phase 2 Enhancements Technical Change Request.doc Page 31 of 31

Part 4: Planning, Design, Testing, & Implementation Calendar

Page 32: Technical Change Request & Design Specificationsit.unm.edu/dashboard/BudgetPlannerPhase2.pdf · batch mode via AppWorx, thereby avoiding the timeout issue. 1.1.1.4 Modifications to

July 27

Sunday Monday Tuesday Wednesday Thursday Friday Saturday28 29 30 31 August 1 2

3 4 5 6 7 8 9

10 11 12 13 14 15 16

17 18 19 20 21

DEVL -1. SSB 7.3.0.1 Upgrade (5 UNM-modified programs in which Defect CMS-

-DFCT90919 has been corrected.)

22 23

24 25 26

Steering Committee Technical ChangeRequestPresentation

27 28 29 30

31

Budget Planner Phase 2 Enhancements ( August 2008 )

Develop Technical Change Request

Develop Technical Change Request

Develop Technical Change Request

Develop Technical Change Request

Re-Apply UNM Modifications to SSB 7.3.0.1 Upgrade

Re-Apply UNM Modifications to SSB 7.3.0.1 Upgrade

Assess Phase 2 Enhancement Specifications

Page 33: Technical Change Request & Design Specificationsit.unm.edu/dashboard/BudgetPlannerPhase2.pdf · batch mode via AppWorx, thereby avoiding the timeout issue. 1.1.1.4 Modifications to

August 31

Sunday Monday Tuesday Wednesday Thursday Friday SaturdaySeptember 1 2 3 4 5 6

7 8 9

Steering Committee Technical Change Request Approval

10 11 12 13

14 15 16 17 18 19 20

21 22

ERP LeadershipBudget PlannerPhase 2EnhancementsPresentation

23 24 25 26 27

28 29 30 October 1 2 3 4

Budget Planner Phase 2 Enhancements ( September 2008 )

Develop Phase 2 Enhancements

Develop Phase 2 Enhancements

Develop Phase 2 Enhancements

Develop Phase 2 Enhancements

Assess Phase 2 Enhancement Specifications

Assess Phase 2 Enhancement Specifications

Page 34: Technical Change Request & Design Specificationsit.unm.edu/dashboard/BudgetPlannerPhase2.pdf · batch mode via AppWorx, thereby avoiding the timeout issue. 1.1.1.4 Modifications to

September 28

Sunday Monday Tuesday Wednesday Thursday Friday Saturday29 30 October 1

INTG –1. SSB 7.3.0.1 Upgrade2. SSB Object Migration3. INB Object Migration4. Oracle Reports Object Migration5. INB Job Submission Data Migration

2 3 4

5 6 7 8 9 10 11

12 13

ERP Leadership Project Status Update

14 15 16 17 18

19 20 21 22 23 24 25

26 27 28 29 30 31 November 1

Budget Planner Phase 2 Enhancements ( October 2008 )

Unit Test of Phase 2 Enhancements

Unit Test of Phase 2 Enhancements

Unit Test of Phase 2 Enhancements

Unit Test of Phase 2 Enhancements

Migration Verification of Phase 2 Enhancements

Page 35: Technical Change Request & Design Specificationsit.unm.edu/dashboard/BudgetPlannerPhase2.pdf · batch mode via AppWorx, thereby avoiding the timeout issue. 1.1.1.4 Modifications to

October 26

Sunday Monday Tuesday Wednesday Thursday Friday Saturday27 28 29 30 31 November 1

2 3 4 5 6 7 8

9 10

ERP Leadership Project Status Update

11 12 13 14 15

16 17 18 19 20 21 22

23 24 25 26 27 28 29

30

Budget Planner Phase 2 Enhancements ( November 2008 )

System Test of Phase 2 Enhancements

System Test of Phase 2 Enhancements

System Test of Phase 2 Enhancements

System Test of Phase 2 Enhancements

Page 36: Technical Change Request & Design Specificationsit.unm.edu/dashboard/BudgetPlannerPhase2.pdf · batch mode via AppWorx, thereby avoiding the timeout issue. 1.1.1.4 Modifications to

November 30

Sunday Monday Tuesday Wednesday Thursday Friday SaturdayDecember 1 2 3 4 5 6

7 8

ERP Leadership Project Status Update

9 10 11 12 13

14 15 16

Steering Committee Approval for Implementation

“Go / No Go”

17

BANP –1. SSB 7.3.0.1 Upgrade2. SSB Object Migration3. INB Object Migration4. Oracle Reports Object Migration5. INB Job Submission Data Migration

18 19 20

21 22 23 24 25 26 27

28 29 30 31 January 1 2 3

Budget Planner Phase 2 Enhancements ( December 2008 )

System Testing of Phase 2 Enhancements

System Testing of Phase 2 Enhancements

Implementation Verification of Phase 2 Enhancements

Implementation Verification of Phase 2 Enhancements

Page 37: Technical Change Request & Design Specificationsit.unm.edu/dashboard/BudgetPlannerPhase2.pdf · batch mode via AppWorx, thereby avoiding the timeout issue. 1.1.1.4 Modifications to

Patch # Module Defects Addressed Date AppliedDEVL

Date AppliedINTG

Date AppliedBANP

Notes

pcms-dfct90919_bwf70300 Finance Self-Service CMS-DFCT90919 8/22/2008 10/2/2008 12/13/2008 This affects packages: bwfkbdws.sql; bwfkbws1.sql; bwfkbdw1.sql; bwfkbpa1.sql; and bwfkbwsh.sql

Budget Development 7.3 Patches

Memorandum To: Jeff O’Keefe From: Robert Barraza Date: 08/28/08 Purpose: Final Task Status Update Task: Merger of UNM Custom Code with Banner Release 7.3.0.1

Status Duration

bwfkbdws.sql Review – 100% .16 hr (10 min). Analysis – 100% .16 hr (10 min) Code Merge – 100% .66 hr (40 min) Compile / Test – 100% Desk Check 1 hr On Line Banner (DEVL) 1 hr Code Correction 2 hr

bdfkbdw1.sql Review – 100% .25 hr (15 min)

Analysis – 100% .25 hr (15 min) Code Merge – 100% 1.5 hrs Compile / Test – 100%

Desk Check 2 hr On Line Banner (DEVL) 1 hr Code Correction 2 hr

bwfkbwsh.sql Review – 100% .25 hr (15 min) Analysis – 100% .25 hr (15 min) Code Merge – 100% 1 hrs Compile / Test – 100%

Desk Check 2 hr On Line Banner (DEVL) 1 hr Code Correction 2 hr

Page 38: Technical Change Request & Design Specificationsit.unm.edu/dashboard/BudgetPlannerPhase2.pdf · batch mode via AppWorx, thereby avoiding the timeout issue. 1.1.1.4 Modifications to

bdfkbws1.sql Review – 100% .5 hr (30 min)

Analysis – 100% .5 hr (30 min) Code Merge – 100% 2 hrs Compile / Test – 100%

Desk Check 2 hr On Line Banner (DEVL) 1 hr Code Correction 1 hr

bdfkbpa1.sql Review – 100% .5 hr (30 min) Analysis – 100% .5 hr (30 min) Code Merge – 100% 2 hrs Compile / Test – 100%

Desk Check 2 hr On Line Banner (DEVL) 1 hr Code Correction 1 hr ==========

Total 32.5 hours