Description of Issue
- Site ran GL Encumbrance Utility (GLENCUTE) and are unsure if they should process the utility or have questions about UPD Action Codes
- How or why did UPD Action Codes occur?
Context
- GLENCUTE
- Encumbrances
Cause
- The General Ledger tables were not correctly updated by an Encumbrance Transaction through between proof and output post actions
- Missing Encumbrance Journal(s)
- Double Posted Encumbrance Journal(s)
Resolution
- Reconcile Encumbrances amount(s) with GL Master Amount and Journal Amounts to identify root cause
- Never trust a utility, it is only a tool, ensure the utility is not providing false positive errors
- False errors if processed will insert errors into the General Ledger
- Run the 'Process" option to bring the master amount in line with the journal amount
- Contact Munis Financials General Ledger Support if there are any questions or concerns
- Support will tie out to known issues or submit any utility or encumbrance program coding concerns to development
Additional Information
- Best practices for the Live database include:
- Complete a system backup of the Live database
- Ensure users are logged out of the Munis Live database
- If unsure refresh Train and process in Train to see the end result
Handling UPD Action Code for Budgetary Carry Forward Method Sites
0 Comments