Scheduling

Five year-end batch jobs generate General Ledger data files.

•      KFS-COA populatePriorYearDataJob–This job must be run prior to running the other year end jobs. Normally it’s run on June 30 after the last day of the fiscal period. It adds all the accounts that were created in the fiscal year to the prior year account table that is used by the other jobs for processing. Parameter RUN_DATE needs to be set to the date that this job needs to run.

•      KFS-GL organizationReversionPriorYearAccountJob

•      KFS-GL encumbranceForwardJob

•      KFS-GL nominalActivityClosingJob

•      KFS-GL balanceForwardJob

Files output by these jobs are not automatically fed into the scrubber, so an administrator must review the files to be sure the data seems valid and then use the GLCP to make the data available for the next nightly batch processing. 

These four jobs may be run over a period of several days. For example, after the final close, jobs might be run according to a schedule like the following.

exclaim    The populatePriorYearDataJob must be run prior to running the following jobs. Set the RUN_DATE parameter to the date that this job should run.

Day 1

1.  Schedule:

•      KFS-GL organizationReversionPriorYearAccountJob

•      KFS-GL encumbranceForwardJob

•      KFS-LD laborBalanceForwardJob

Day 2

2.  Review output from yesterday's:

•      KFS-GL organizationReversionPriorYearAccountJob

•      KFS-GL encumbranceForwardJob

•      KFS-LD laborBalanceForwardJob

3.  For all valid output from those jobs, use the General Ledger Correction Process and Labor Ledger Correction Process documents to input the files into this evening's batch cycle.

4.  Schedule KFS-GL nominalActivityClosingJob.

Day 3

5.  Verify that the entries from the following jobs posted:

•      KFS-GL organizationReversionPriorYearAccountJob

•      KFS-GL encumbranceForwardJob

•      KFS-LD laborBalanceForwardJob

6.  Review output from yesterday's KFS-GL nominalActivityClosingJob.

7.  For all valid output from that job, use the General Ledger Correction Process document to input the files into this evening's batch cycle.

8.  Schedule KFS-GL balanceForwardJob.

Day 4

9.  Verify that the entries from yesterday's KFS-GL nominalActivityClosingJob posted without incident.

10. Review output from KFS-GL balanceForwardJob.

11. For all valid output, use the General Ledger Correction Process document to input the files into this evening's batch cycle.

Day 5

12. Verify that the entries from yesterday's Financials-GL balanceForwardJob posted.

 

If a problem (for example, if the scrubber finds errors) arises at any point, fix the problem before continuing with the remaining steps.

 

exclaim       The delivery mechanism of these reports depends on the implementing institution.

 

More:

Parameters