Scheduling

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

•      KFS-COA populatePriorYearDataJob–This job needs to run after the system is brought down on the night of June 30 (or at the point in time you wish to capture fiscal year end account and organization snapshots).  Scheduling allows for a clean cut-off of the account and organization snapshots (off hours) when updates are not being performed

•      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.

Day 1

1.    Schedule:

•      KFS-GL organizationReversionPriorYearAccountJob

•      KFS-GL encumbranceForwardJob

•      KFS-LD laborBalanceForwardJob

Day 2

1.    Review output from yesterday's:

•      KFS-GL organizationReversionPriorYearAccountJob

•      KFS-GL encumbranceForwardJob

•      KFS-LD laborBalanceForwardJob

2.    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.

3.    Schedule KFS-GL nominalActivityClosingJob.

Day 3

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

•      KFS-GL organizationReversionPriorYearAccountJob

•      KFS-GL encumbranceForwardJob

•      KFS-LD laborBalanceForwardJob

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

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

4.    Schedule KFS-GL balanceForwardJob.

Day 4

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

2.    Review output from KFS-GL balanceForwardJob.

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

Day 5

1.    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.

 

 

More:

Parameters