UMS Project Updates

Code Build 4.71.805(March, 2008)
Code Build 4.68.789(October, 2007)
Code Build 4.64.751 (May, 2007)
Code Build 4.60 (January, 2007)
Code Build 4.56 (October, 2006)
Code Build 4.44 (December 2005)
  • UMS Release Notes version 4.44 PEAR Form
    This document is an overview of new features as follows.
  • Transaction Tags PEAR Form
    This document is a detailed description of the transaction tag module. It begins at tag setup and takes the user through the process of creating tag values, tag budgets, and attaching tags to documents in UMS.
  • Reconciliation through Automatching PEAR Form
    This document is a detailed description of the automatching functionality. It begins with user security rights and takes the user through the complete process of reconciling through the automatching process.
  • DropShift PEAR Form
    This document is a detailed look at the newest reporting tool in UMS. It will explain the different types of DropShift reporting and how to filter, group, and extract data.
Code Build 4.32 (May 2005)
  • Release Notes version 4.32 PEAR Form
    Important note: the Personnel Funding and the Center Rollover Wizard sections DO NOT apply to the MUSC version.
  • Attaching documents to Pears
    You can now attach documents to Pears (e.g. Affiliate Salary Worksheet). Note: The in-band exceptional pay increase form is obsolete and no longer needed.
  • Reset of Approvals upon certain edits
    Modifying an approved document in a way that would increase the salary commitment will reset approvals:
    • Approval Groups on affected UDAKs will be reset to "Awaiting"
    • the overall document status is reset to "Awaiting".
  • Specific Warning Messages displayed on the form print-out
    • "Not Approved"
      Blue watermark indicating the overall document status is still "Awaiting"
    • "Not valid for e-submission”
      Red marking above Signature Section shows when one or more UDAKs have not been approved electronically. This happens when:
      • UDAK is non-reporting
      • UDAK has no Approval Group set-up
      • There is an Approval Group, but the status is still ”Awaiting”
    • "Fund Total not equal to 100%”
      Shows at the bottom of the Funding Section when fund percentages do not add up to 100%.
    • "Verify end date of Previous Pear"
      Red message appears under the gray "HRM ONLY" box at the top of the form. On an existing employee Pear, this message will show when the end date of the previous Pear is not immediately before the start date of the new Pear. This should prompt the user to investigate the problem, as there is either a gap in salary coverage, or there are multiple encumbrances due to overlapping periods.
  • Modified Salary
    On the fund tab, the label “for Employer” has been edited to "Modified Salary". This is now showing the actual annual salary, right of the Annualized Salary.
  • File Copy
    When printing the Pear, you can now choose a third option "Print File Copy". This will print all fields in addition to a displaying a watermark “FILE COPY”. This is for internal use only and should not be used for submission to F&A.
Code Build (January 2005)
  • In-Band Exceptional Pay Request Form
    You do not need to submit this document anymore. Remember to indicate a reason for each salary increase.
  • Pear Officers
    This structure streamlines the routing and submission processes:
    • Only Pear Officers are allowed to submit the Pear forms to HRM. If the form is printed and submitted to HRM on paper, the Pear Officers have to sign in the "submitted by" box at the bottom of the form. When submitting the form electronically to HRM (not yet available), the Pear Officer's name will automatically appear in that box.
    • Pear Officer Routing Groups speed up inter-department or cross-entity communications and leverage campus resources.
  • Simplification of pay cycles
    The drop-down box options have been restricted to reflect the only two pay cycles available at MUSC: "Bi-Weekly" and "Monthly". A third option, "Daily", is reserved for UMA use only.
  • Funding Approvals
    If a UDAK has an Approval Group associated with it, the name of the approver will automatically print under the column "Funding Approval" of the fund distribution. No physical signature is required in this case for those UDAKs. Otherwise, it will display "Pending" and a physical signature will be required.
    Note: On the January software version, a small glitch in the code may cause the approval to display "Pending" even though the UDAK has received the group Approval. This should be fixed in the May release.
  • Simplification of the Rate
    It now defaults to Annually for all profiles. Even though other choices are available, they are restricted to the hospital, and all MUSC salaries have to be entered using using the Annualized Salary. Click here for illustrations.
UMS - GEAC integration project

Several phases are currently planned to ensure seamless integration of UMS with the F&A GEAC system (Smartstream and Hermit). These phases are scheduled to be completed over the course of the next years.

  • View of the System of Records
    A view of live Hermit data is planned to be displayed to UMS users when creating a new Pear form. This will ensure more accurate data and more informed decisions when preparing the personnel action requests.
  • HRM validation module
    Requests received from UMS in HRM will be reviewed electronically by HRM. This interface will provide HRM with the necessary compilation of data to ensure faster processing of the requests.
  • Business Rules workflow engine
    A dynamically configurable engine to automatically route transaction in UMS based on certain criteria. For example, in CoM, a routing would automatically be established through the Dean's Approval Office for all salary changes on Faculty employees.
  • Establish bi-directional dialog for workflow
    The goal is to allow users to track the progression and status of their request seamlessly throughout the various validation workflow engines. Real time feed-back on HRM validation status or Hermit processing status is intended to be established, especially in the case of rejected transactions (HRM validation denied or data integrity conflict).