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).

Browser not supported