Kuali Cloud Internal test 1-Nightly Schedule Batch jobs

Y  3/28/23

Got an Incident Report error when trying to load a .csv file. so I can't run the job until this is fixed.

N 8/3/2023

Ran after uploading GLCP file and running scrubber job.  checking individual entries under General Ledger lookup shows the entries posted successfully. 

3/28-29:  did above test of GLCP.  Scrubber and Poster both successful.

Y

3/28/23

4/30 Kathy stated this functionality has been removed from KFS including the table CG_PRPSL_CLOSE_T

4/28 job fails when ran with no detailed error.  not sure if the entire tree needs to be run or just the few jobs before it for it not to fail.

**

The intent of this job is to find all unclosed Awards that are not underwritten and all unclosed Proposals. For each of those proposals and awards the close date is set to the date on which the close was executed.**

Bruce

BC DISCONTINUED

No testing necessary - Don't use/won't be used

proCard xml file created 

report ran successfully and generated a correct report.  including newly created payments from Spreadsheet upload.

Created PO Awaiting Receiving then ran job, all succeeded

10/16:  see instructions from Kymber on how to get the PREQ into Awaiting Receiving status.  email dated 10/16.

upload csv or xml file that was used in PRD

both csv and xml loaded successfully 

upload 2 encumbrance files with partial data from prior PPE  One Encumbrance Accrual and the other Encumbrance liquidation. 

note that these then fed into the ensuing Labor nightly jobs, Discontinued 5/30/23.

successfully processed file, assets were retired and acknowledgments sent as expected

Y

4/10/23

3/12:  tested with DV/PDP process, successful (Bruce)

7/24: tested with Payment Spreadsheet upload, worked successfully although spreadsheet upload generated GL entries for wrong object code.  I don't believe that is caused within this job.  See FINUCONN-508.

04/28: Ran successfully after creating a payment with pay date of 4/29 and loading qty.  ran to also run purchasingPreDisbursementExtractJob

-Manually create PREQ and manually ran the job, it works. -Lan

Ran after uploading a GLCP file. 

3/28:  Ran GLCP then let scrubber/poster run overnight.  both successful, verified scrubber report and that GL entries posted correctly.

Y

3/28/23

successfully processed file, assets routed into workflow.  upon approval, assets were created.

load csv, run job

Y

4/10/23

Validate Procurement Card Defaults when testing - Bryon

10/17/23:  Normally run at year end to disapprove specific enroute documents.  It selects eDocs still enroute, with a create date equal to or earlier than the YEAR_END_AUTO_DISAPPROVE_DOCUMENT_CREATE_DATE.  There is no harm in not running it. It's mainly used to clean up documents that may have been started in the prior fiscal year to prevent posting entries that may not be appropriate for the new year.

For UConn this is not invoked as the create date is set for 6/30/2010, which is prior to the KFS go live.  So there would not be any eDocs with that create date condition.  Labeled not used.

4/25:  if this is Labor purgejob, it is discontinued.  5/10: NOT labor, this purges all batch files older than 90 days.

5/17: 1st pass, last night the job removed files dated 2/15 (90 days before 5/16).  check again next wk, should have removed files thru 2/22).  5/24-25:  checked both days - first day it had purged up to 2/22 (OK) and 5/25 it had purged the 2/22 files, leaving 2/23 and forward.  this is all OK.  pass

Y

5/25/23

4/28:  will need to work with David Ferreira on how to design this test, since the documentation on this job indicates it creates assets from purchasing data.

6/16:  Testing in process.  creating PREQ and DI using capital object code for CAB extract to pick up.

6/17:  reran nightlyOutJob, scrubber, poster and poster balance.  then reran cabExtractJob and the two transactions from 6/16 now appear in the General Ledger Transactions and Purchasing Transactions functions to process into an asset.  successful test

log files look ok but cannot find output or input file.  6/6/23

10/16:  sufficient funds checking is not used, therefore not even configured.