/
Project String issues when closing Contracts with Contingencies

Project String issues when closing Contracts with Contingencies

Owned by Knowledge Assistant
Jan 12, 2023
1 min read



Description of Issue

When closing a Contract with a Contract Contingency, certain problems can occur with the Project String. Header/Detail mismatches can happen, along with Journals not being created at all, if you close a Contract that only has a encumbered contingency but fully expended Revised Amount.



Context

Munis ERP

Contract Management



Cause

This is a Munis Defect



Resolution

  • Please download MUN-453528 from the MIU or Tyler Deploy when available

  • Please contact Munis Financial Support for any assistance with project string corrections 



Additional Information












Related content

Contract Contingency Invoke causes Project String issues
Contract Contingency Invoke causes Project String issues
Knowledge Assistant
More like this
Project Strings are being stored on the wrong Journal Line for CRP Journals
Project Strings are being stored on the wrong Journal Line for CRP Journals
Knowledge Assistant
More like this
Unable to Delete Project String - Project Accounts Monthly Amounts Exist
Unable to Delete Project String - Project Accounts Monthly Amounts Exist
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
Rolling contracts with contingencies is erroneously associating the contingency COM with the wrong contract reference PORef2
Rolling contracts with contingencies is erroneously associating the contingency COM with the wrong contract reference PORef2
Knowledge Assistant
More like this
Error using project string - Project String status is invalid for posting transactions.
Error using project string - Project String status is invalid for posting transactions.
Knowledge Assistant
More like this