Cutover Information

• Description:  ATS transactions that are submitted with transaction ID prefix / unit code combinations that match existing draft pending transactions in CORE are causing the system to try and submit those additional draft pending transactions, instead of only processing the submitted ATS transaction with that prefix ID and unit code combination.

• Workaround: Submit your ATS with an invalid or closed period so that it uploads as rejected. Then, copy your rejected ATS transaction in CORE as a new transaction, make data corrections so it is valid, and then submit. This allows the system to process only that one transaction prefix ID / unit code and try to also submit any other draft pending transactions with that same prefix and unit code combination.

• Description:  There is a problem with the throughput of processing ATS transactions, such that the system gets bogged down and does not process uploads within the expected ~5 minutes or less, and sometimes ATS uploads do not make it into the system to process at all.

• Workaround: We are investigating options to improve the overall process for ATS transactions. Users can help with this by only submitting ATS in the approved .xls or .xlsx template formats. Do not submit .pdf, .xlsm, .csv or any other file extension format.

• Description:  Intermittently, issued remittance advice for EFT payments is showing duplicate lines. The payment amount on the EFT is correct. Only the lines on the remittance are showing twice.

• Workaround: None at this time, other than communicating to vendors their payment amounts are accurate and to ignore duplicate / identical lines of information on the RA while we work on a fix for the issue.

• 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:  Two jobs within the HRM Nightly Cycle are not processing timely, and as a result the HRM Nightly Cycle is not able to complete. As a result, any LA15 adjustments that would normally be processed nightly from CLAS/CPPS into HRM and to CORE Financial have not been processed since the CORE Upgrade go live.

• Workaround: None.  We are currently investigating issues with processing for the two impacted jobs so that this systemic process can be sped up.

• 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:  There are two notification parameters in CORE 4 that must be turned on in order for buyers and managers on a team to receive a notification when a procurement is assigned,  BUYR_TEAM_NOTIF_RECIPIENTS and  BYPASS_BUYR_POPUP_ALERT.  When both parameters are on, users are receiving a severe "Recipients is required" error when attempting to assign procurements that were converted from 3.9.

• Workaround: CORE Ops discussed with SPCO and for Go_Live decided to Blank out the Parameter Value field on the BUYR_TEAM_NOTIF_RECIPIENTS parameter, which means buyer team managers are not notified of the assignment, but the assigned buyer will receive a notification.

• Description:  Intermittently, UDOCs to disable user access are getting stuck at Level 10 workflow and are not going to Final.

• Workaround: None. Agencies should just leave those disable UDOCs in pending status at that Level 10 for now. We are working on a defect resolution with CGI.

• Description:  On a PGPHR transaction, when a user unchecks an item in Configure Columns (Magic Wheel), it disappears from the transaction rather than being placed “secondary” under General Information.

• Workaround: No workaround to prevent the issue. Please use “Reset” in Configure Columns.

You can still look up Draft/Rejected transactions on the Transaction Catalog page to see what needs further work and attention.

There will be no change to what details a vendor receives on their warrant or EFT remittance. They will still receive the payment transaction #, Invoice #, Invoice Date, Invoice Line #, Line Description, and Check Description.

These won't be saved.  New favorites will have to be made by users.