Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Current »

Description of Issue

When I run a query, what do the _proj codes mean?

Context
  • Enterprise ERP
  • Payroll
  • Human Resources
Cause


Resolution

The _proj fields exist in many of the Munis Payroll/HR tables and are used to segregate data.

  • proj 0 is for live records
  • proj 1 is for records in the Terminated programs
  • proj 2-100 are for Personnel Actions that have not yet been posted to the live records
  • proj 101-200 and 1001-2000 are for Salary & Benefit Projections (where _proj = the Salary & Benefit Projection Run #)
  • proj 201-300 are for Retro Pay files
  • proj 401-499 are for Attendance Bonus Pay Runs
  • proj 401-500 are used with Mass Step Increases, Mass Contract Increases, Mass Index Step Increases and Pay Band Increase processing
  • proj 501-600 are for Longevity
  • proj 900-902 are used for ESS Accruals records. 
    • 900 reflects time that has been requested through ESS
    • 901 reflects time that has been requested through ESS and subsequently Approved
    • 902 reflects time that has been requested through ESS and subsequently Denied
  • proj 999 used for applicants
  • proj 5000-5999 are used for a holding place for Employee Import
Additional Information

Enterprise ERP uses the proj numbers because all of the above listed functionalities use the same data tables. 

For Example:

  • An employee  will have a record in Munis Employee Master (prempmst table).  The record that is used in the regular payroll process is the live record. (proj 0)
  • If that employee had an address change, the site might create a Personnel Action which would create a second Employee Master record that would sit inside that Personnel Action with the new address until it was posted to live. (proj 2-100)
    • There can be up to 100 different Personnel Actions sitting out there at a time. 
  • If the site was going through a budget process and created a Salary & Benefit Projection, that employee might have a third Employee Master record inside the Salary & Benefit Projection. (proj 101-200 and/or 1001-2000)
    • There can be as many as 100 different Salary & Benefit Projections out there at a time. 
  •  Using the above example, that Munis employee number is linked to 3 separate records on the prempmst table.  It is the proj number that identifies which set of data on the table belongs to which piece of functionality in the system, or which Employee Master record belongs to which process. 

The _proj field is also referred to as Data Set in the Data Integrity Assistant (DIA).





  • No labels

0 Comments

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.