Contract Contingency Invoke causes Project String issues





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