Scheduling Year-End Batch Jobs

General Ledger > General Ledger Year-End Processes

Scheduling Year-End Batch Jobs

Five year-end batch jobs generate GL data files.

• Financials-GL updatePriorYearDataStep–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

• Financials-GL organizationReversionPriorYearAccountJob

• Financials-GL encumbranceForwardJob

• Financials-GL nominalActivityClosingJob

• Financials-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:

• Financials-GL organizationReversionPriorYearAccountJob

• Financials-GL encumbranceForwardJob

• Financials-GL laborBalanceForwardJob

Day 2

1. Review output from yesterday's:

• Financials-GL organizationReversionPriorYearAccountJob

• Financials-GL encumbranceForwardJob

• Financials-GL laborBalanceForwardJob

2. For all valid output from those jobs, use the GLCP to input the files into this evening's batch cycle.

3. Schedule Financials-GL nominalActivityClosingJob.

Day 3

1. Verify that the entries from the following jobs posted without incident during last night's batch cycle:

• Financials-GL organizationReversionPriorYearAccountJob

• Financials-GL encumbranceForwardJob

• Financials-GL laborBalanceForwardJob

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

3. For all valid output from that job, use the GLCP to input the file into this evening's batch cycle.

4. Schedule Financials-GL balanceForwardJob.

Day 4

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

2. Review output from Financials-GL balanceForwardJob.

3. For all valid output, use the GLCP to input the file into this evening's batch cycle.

Day 5

1. Verify that the entries from yesterday's Financials-GL balanceForwardJob posted without incident.

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