Known Issues

Description:  Payments are getting stuck on the AD/EF TRANSACTION EXCEPTION REPORT with the following Invalid Error:  The value for field First Name is too large, current length is 32, maximum allowed length is 30. (Q0226). A critical ticket has been submitted 

Workaround: None

Description:  The option to email a BIRT form in PRD is not working. 

• CGI is investigating.

Workaround: Please generate the form using the PDF option, save the form, and send it via email to the desired recipient.

Description:  When an SRQ is using accounting distribution splits, it causes the subsequent CI posting line to duplicate the COGS and inventory posting. 

• For example, SRQ accounting distribution splits as 40% and 60%, the commodity line amount is $1000.  The CI accounting line 1 will debit COGS for $1000 and credit inventory for $1000. CI accounting line 2 will repeat this posting. This causes the overstatement of COGS and the understatement of inventory.

Workaround: No workaround yet, single distribution SRQ/CI works as normal. Around 7% of SRQ uses splits.

Description:  Favorites not working in the “Send Page” functionality.

Workaround: This is a known issue and has been reported to CGI. Currently the only option is to manually enter the email address or Copy/Paste it from another location. 

Description:  Reports: GA-015 Light Version for Central Payroll, and LDC-007 Light for Central Payroll. The same issue applies to the Statewide versions.  When refreshing the prompt to get a list of, one example, GTN run numbers, the retrieval is very slow (several minutes). 

Workaround: Do not refresh the list of values, just enter the prompt value manually.

Description:  During the AD Chain process, EFT payments are generated (according to VCUST settings) and emails are sent to the vendors. The emails stopped after the migration of the 2025 FS1 GA in Production.

Workaround: None

Description:  Some department users see that their transaction is showing at the wrong level in the Track Work in Progress screen, but is in the correct queue level on the actual worklist screen for approvers to take task/approve.

Workaround: This issue does not affect the transaction's progression through the workflow. Transactions can still be processed to Final per existing workflow routing rules/levels.  The issue is confusing for users because, on the screen, it appears to the user that the transaction is stuck when it is not.