Invalid Entity/Purpose Code Combinations
New validation rules set to be implemented.
New validation rules will be implemented in Aggie Enterprise and UC Path that will only allow salary expenses with the Entity/Purpose code combinations listed in the table below. Any use of Entity/Purpose code combinations not in the chart will result in defaulted payroll.
| Valid Entity and Purpose Combinations | |
|---|---|
| Entity | Purpose |
| 3110, 3111 | 40, 41, 43, 44, 45, 60, 61, 62, 64, 68, 72, 76, 78 |
| 3310 | 40, 41, 43, 44, 45, 60, 61, 62, 64, 68, 72, 76 |
| 3210, 3299 | 42 |
In preparation, any existing COA entries in UCPath funding entry, that contain invalid Entity/Purpose code combinations must be fully corrected by June 6th at 8p.m.
Actions to take*:
- Identify Funding Entries in UCPATH that contain an invalid combination of Entity and Purpose segments. (Refer to the included table.) Run a UCP-391 Funding Entry Report for your departments to identify any conflicts.
- For those entries:
- Update Funding Entry in UCPath to a valid Entity/Purpose code combination and
- Complete Salary Cost Transfers (SCTs) in UC Path for any salary expenses that currently reside on the invalid COA.
- All payroll starting with the following pay periods should be reviewed:
- Bi-Weekly: PPE 12/24/2023
- Monthly: PPE 12/31/2023
*If these actions are not taken to clean up the above-mentioned entries, any new salary expenses tied to these invalid COA Entity/Purpose combinations will default in the new fiscal year. Once the new rules are in place, you will be unable to complete any Salary Cost Transfers (SCTs) with the invalid COA.