University of Minnesota
University of Minnesota
Enterprise Systems Upgrade Program
http://www.upgrade.umn.edu/
One Stop Twin Cities: (612) 624-1111 (System camupuses can find support on their One Stop website)
Academic Support Resources (ASR) Training Team: (612) 625-2803
Human Resources help: (612) 624-UOHR
Financial System help: (612) 624-1617
IT help: (612) 301-HELP
Work Steam Title - click to go to Home

Potential for Change by Module in EFS

Work groups have been reviewing version 9.2 of PeopleSoft Financials to identify gaps and improvements that may affect current processes. While we do not yet know the specifics of all the changes, nor do we know the exact methods that will be used to share new information, these are our best guesses at this time. Check back periodically for updates.


Green indicates that any changes in this area should be easily understood or take very small adjustments in your routine. Information about changes in these areas will be brief. You may have to read an email, review a message on the EFS message board, or view a job aid. Changes in these areas may not even be noticeable.

Yellow indicates slightly more change is possible. Expect to have to review a job aid, work through an online tutorial, or attend an information session. It may take a bit of effort to adapt to changes in this area but it shouldn't disrupt routines for long.

Orange indicates a large amount of change in the system, in the process, or both. Expect to have to review job aid(s), training materials, attend an information session or training, or review an online tutorial. The changes in this area will take some time and attention. Expect to have a learning curve and expect that performing this task will take longer for a period of time after the new functionality or process is rolled out to the community.

Red indicates wholesale redesign of the process and system functions. Expect training of some kind and a significant learning curve.


You can access and download this list here.


Other Recommendations for Change

Work groups have completed work on many important concerns thus far. The Finance Functional Steering Committee (FSC) reviews all change requests related to finance for the upgrade. The recommendations below are those that are ready to be shared with the community.

  1. Implement use of non-sponsored project functionality. 
    Recommendation Status:
    The work group recommended that the University not implement project costing, rather it should introduce a new multi-fiscal year report for non-sponsored activity. The FSC concurred. An alternative solution was approved to create a multi-fiscal year report for non-sponsored activity. This report request has been passed to the financial reporting and business intelligence module support and the Business Process Owners (BPOs) for review.
    More information can be found here. (PFM94088.doc will download to your machine.)
  2. Non-sponsored budget process change.
    Recommendation Status - Adopted. Recommendation will move forward as part of the upgrade work. More information can be found here. (PFM96367.docx will download to your machine.)
    Implement non-sponsored detailed expense budget checking.
    Recommendation Status - Adopted. Recommendation will move forward as part of the upgrade work. More information can be found here. (PFM96377.doc will download to your machine.)
  3. Replace BPEL COA Forms.
    Recommendation Status - Adopted. Recommendation will move forward as part of the upgrade work. The work group recommended that the University scuttle the BPEL forms and move to analysis of the PeopleSoft delivered tools to see if they will meet our needs.
    More information can be found here. (PFM98630.docx will download to your machine.)
  4. Change field header Fin EmplID to Chartfield3.
    Recommendation Status:
    The work group recommended that the University not change the name of Fin EmplID back to Chartfield3. The University renamed the Chartfield3 field as 'Fin EmplID' in 2008. This field answers the question, "If this financial activity needs to be tracked by individual employee, to which employee should this transaction be assigned?" For example, Fin EmplID values are used in combination with Program codes to aid in tracking funds designated for use by a specific faculty member. More information can be found here. (PFM94090.doc will download to your machine.)