Introduction and general background
Oracle's PeopleSoft applications are the basis for a great number of the University's mission-critical functions. Other enterprise applications - supported by OIT or by other distributed IT units - integrate with PeopleSoft to provide specific functionality to targeted user populations. The OIT PeopleSoft team publishes the change control schedule on this page for the University of Minnesota business analysts and technology staff who represent business process owners in the support of the group of PeopleSoft applications. Other University support applications may follow the same general schedule.
Page Audience
Business analysts and application development staff responsible for direct support of one or more modules of a PeopleSoft application
Page Purpose
Establishes a general schedule and baseline service level agreement (SLA) for code migration/deployment activities.
| Target Instance | Migration Schedule | Approval Deadline | Critical Requests |
|---|---|---|---|
| PeopleSoft: xxTST xxQAT FSQRPT | Monday – Friday Requests are processed in the order in which they are received. | Requests in "Pending Migration" status BY 12:00 p.m. (noon) Monday–Friday will be migrated by the end of the same business day. Requests in "Pending Migration" status AFTER 12:00 p.m. (noon) Monday–Friday will be migrated by 12:00 p.m. (noon) the next business day. | Critical requests are migrated as they are requested and prioritized ahead of non-critical requests. |
| PeopleSoft: xxFIX | N/A due to daily refreshes from PRD | N/A | While rare, some development efforts may require testing in FIX in addition to the normal SDLC environments. Critical requests are migrated as requested by a Service Owner. Note that remigration will be necessary each day if testing spans multiple days due to the daily refresh from PRD. |
| PeopleSoft: xxPRD FSRPT xxTRN | Sundays, monthly release 6:00 a.m. – 12:00 p.m. (noon) | Requests in a "Pending Migration" status by 4:00 PM on the Thursday prior to the Sunday migration window will be migrated in that release. Any request approved after this will be migrated in the next scheduled release. | Additional notification and approval from a Service Owner is required. Critical requests are migrated beginning at 4:00 PM the day they are requested. If a time other than 4:00 PM is needed, it must be indicated in the Service Owner's notification. Approval of test results should be submitted to a Service Owner by noon for a request to be migrated at 4:00 PM. If the migration is to occur at a time other than 4:00 PM, approval of test results should be submitted 4-hours prior. |
Page last reviewed/updated: September 2023.