/
Contract Contingency Invoke causes Project String issues

Contract Contingency Invoke causes Project String issues

Owned by Knowledge Assistant
Feb 14, 2022
1 min read





Description of Issue

When invoking Contract Contingencies, if the Contract is Encumbered and has a Project String, the string's encumbrance can display incorrectly while the change order is unposted, and it will have a header/detail Encumbrance mismatch once the change order is posted. 



Context

  • Munis

  • Contract Management 



Cause

This is a Munis defect



Resolution

  • Please download MUN-431481 from the MIU/Tyler Deploy when available

  • Please contact Munis Financial Support for correction of the Project String mismatch



Additional Information












Related content

Changing Enforcement Method on Contract can leave Project String Header Encumbrance
Changing Enforcement Method on Contract can leave Project String Header Encumbrance
Knowledge Assistant
More like this
Project String issues when closing Contracts with Contingencies
Project String issues when closing Contracts with Contingencies
Knowledge Assistant
More like this
Project String discrepancies with Unposted Contract Change Orders COM and Purchase Order Change Orders POM
Project String discrepancies with Unposted Contract Change Orders COM and Purchase Order Change Orders POM
Knowledge Assistant
More like this
Issue with Project String Encumbrances after Rejecting and Posting Purchase Order
Issue with Project String Encumbrances after Rejecting and Posting Purchase Order
Knowledge Assistant
More like this
Project balance check is returning Encumbrance errors for future years
Project balance check is returning Encumbrance errors for future years
Knowledge Assistant
More like this
Taxable AP Invoice liquidating a taxable contract can cause Project String header detail mismatch
Taxable AP Invoice liquidating a taxable contract can cause Project String header detail mismatch
Knowledge Assistant
More like this