Batch Jobs

The jobs are listed alphabetically in the table below and the last column indicates the location in the Batch Catalog. For detailed information on the jobs (such as when to run, input, output, and process parameters) refer to the associated run sheet in the following user guides: CGI Advantage General Accounting Run Sheets, CGI Advantage Financial - Utilities Run Sheets, CGI Advantage Financial - Accounts Payable Run Sheets, CGI Advantage Financial - System Assurance Run Sheets, and CGI Advantage Financial - Administration Utilities Run Sheets. (Note: The Posting run sheets are located in the CGI Advantage General Accounting Run Sheets guide.)

Job Name

Description

Batch Catalog Section

Automatic Transaction Correction

This job uses the Automatic Transaction Correction Page (ADCP) to select accounting lines on draft transactions using the left-hand column of criteria and make changes to the accounting line with right-hand column values. The intended use is to fix certain accounting line errors on a group of rejected transactions.

Utilities

Bank Account Balance (ABAL)

The ABAL job updates the Bank Account Balance (ABAL) page with a day’s worth of increases and decreases to cash, outstanding disbursements, and outstanding deposits.

General Accounting

Begin Day

The Begin Day job increments the Application Date forward to signify the completion of a nightly cycle.

Utilities

Cash and Fund Balance Sync

The Cash and Fund Balance Sync job synchronizes the data involved with Cash and Fund Balance tracking with data recorded from transaction processing when a discrepancy is reported by the System Assurance 2 report or other diagnostic effort.

General Accounting

Annual Financial Reporting Data Load

The Annual Financial Reporting Data Load job reads the setup on the various Statement setup pages and the input sources defined in that setup to populate tables that are used in the generation of the Annual Comprehensive Financial Reports and the supplementary reports. The process can also generate other types of financial reports other than those related to ACFR.

General Accounting

Identify and Archive Stale Gaps

The Identify and Archive Stale Gaps job performs maintenance on the Journal Log (JLOG) gap records created by those batch & chain jobs that track progress through a journal. When such journal tracking encounters a range of records that are not on the journal, it is logged as a gap for later review. After a period of time, these gap records can be marked as stale so processing will not read them.  Eventually the records are archived with this same job.

Posting

Journal Engine

The Journal Engine journalizes posting lines which have not been journalized and are marked as ’ready for posting’ either from the Journal Posting Initiator job or from normal transaction processing with Real Time Journal Posting turned off.

Posting

Journal Posting Initiator

The Journal Posting Initiator is used in conjunction with the Asynchronous Posting setting on the Transaction Control (DCTRL) page. This job marks those posting lines created from asynchronous posting as ’ready for posting.’

Accounts Payable

Journal Rebuild

The Journal Rebuild job clears out and rebuilds a journal or populates a journal that has not been active.

Posting

Ledger Engine

The Ledger Engine ledgerizes journal records. The job is also used when rebuilding a ledger after running the Rebuild Ledger batch job.

Posting

Multi Process Disb Journal Posting

The Multi Process Disbursement Journal Posting is used in conjunction with the Asynchronous Posting setting on the Transaction Control (DCTRL) page for the Auto Disbursement transaction codes. The job performs the same tasks as the Journal Posting Initiator and then spawns multiple Journal Engine jobs to post all of the selected automatic disbursements.

Accounts Payable

Partial Transaction Ledger Engine

This job handles such a rare scenario that, ideally, it should never have to be used. It is used when an instance of the Ledger Engine failed to write out all the journal records for a transaction to all the ledgers built from that journal. If this partial ledgerization scenario takes place, it was most likely due to some unusual situation. The functional and technical recommendation for this outcome is to rebuild the ledger(s) affected, so as to ensure that Journal Record(s) are neither missed nor double counted. In the case where rebuilding of the ledgers is not feasible then this Partial Transaction Ledger Engine job can be utilized. 

General Accounting

Populate Transaction Codes

When a new transaction code is setup, the Populate Transaction Codes job registers that code in the Administration application for workflow purposes.

Admin Utilities

Populate FY Beginning Balance

This job ledgerizes journal records from Annual Close.

General Accounting

Rebuild BBAL

The Rebuild BBAL synchronizes data involved with Balance Sheet Account Balance tracking with data recorded from transaction processing when a discrepancy is reported by the System Assurance 2 report or other diagnostic effort.

General Accounting

Rebuild Ledger

The Rebuild Ledger job prepares the application for a Ledger Engine in rebuild mode to rebuild a ledger or populate one for the first time.

Posting

SA01 Pre Processor

The SA01 Pre Processor job prepares the application for a System Assurance 1 run to assure budget line amounts updated directly by accounting transactions. It is run as part of the System Assurance 1 chain or independently as part of a job scheduler before running any System Assurance 1 batch jobs.

System Assurance

SA02 Pre Processor

The SA02 Pre Processor job prepares the application for a System Assurance 2 run to assure the Accounting Control Pages: ITD Balance Sheet Detail, Cash Balance Detail, and Fund Balance Detail.  It is run as part of the System Assurance 2 chain or independently as part of a job scheduler before running any System Assurance 2 batch jobs.

System Assurance

System Assurance 1

The System Assurance 1 job takes input ledger and journal records and posts them to a ’shadow’ table for later validation of the accounting amounts found on budget lines by the System Assurance 1 Report job. It is run as part of the System Assurance 1 chain or independently as part of a job scheduler before running any SA01 Report job.

System Assurance

System Assurance 2

The System Assurance 2 job takes input ledger and journal records and posts them to a ’shadow’ table for later validation of accounting control pages by the System Assurance 2 Report job. It is run as part of the System Assurance 2 chain or independently as part of a job scheduler before running any SA02 Report job.

System Assurance

System Assurance 3

The System Assurance 3 job ensures total debits equal total credits for a journal or ledger.

System Assurance

System Assurance 4

The System Assurance 4 job is the first of two assurance jobs for disbursement requests. This job performs an assurance from the Disbursement Request data to payment-requesting transactions.

System Assurance

System Assurance 5

The System Assurance 5 job is the second of two assurance jobs for disbursement requests. This job performs an assurance from payment-requesting transactions to the Disbursement Request data.

System Assurance

System Assurance 6

The System Assurance 6 job assures consistency of data (transaction phase, function, and status) across the various components of a transaction. The job also assures the journal posting indication of any posting lines.

System Assurance

System Assurance 7

The System Assurance 7 job ensures all source journal records have been summarized into a ledger.

System Assurance

System Assurance 8

The System Assurance 8 job ensures the amount of a ledger record equals the sum of journal records logged to the ledger record on the Journal Ledger Crosswalk page.

System Assurance

System Assurance 9

The System Assurance 9 job ensures amounts updated by transaction processing on the Customer Account Information matches what is recorded in the Accounting Journal.

System Assurance

System Assurance 10

When an expense and a revenue budget structure are linked, the System Assurance 10 job ensures that links established are in sync between the revenue and the expense budget lines.

System Assurance

System Assurance 11

The System Assurance 11 job ensures those budget line amounts updated by budget transaction processing matches what is recorded in the Budget Journal.

System Assurance

SA12 Pre Processor

The SA12 Pre Processor job prepares the application for a System Assurance 12 run to assure budget line constraint amount records are in sync with budget lines. It is run as part of the System Assurance 12 chain or independently as part of a job scheduler before running any System Assurance 12 Update batch jobs.

System Assurance

SA12 Update

The SA12 Update job takes active budget controls and calculates them from budget line data on a ’shadow’ table for later validation against the Budget Constraint Amount table by the SA12 Report job.

System Assurance

SA13 Out of Sync differences between Financial and VSS

When Vendor Self Service (VSS) is used, SA 13 is used to report on all out of sync differences between Financial and VSS tables.

System Assurance

System Assurance 15

The System Assurance 15 job ensures open accounting line amounts match the corresponding budget line amount. When there is not a match, the job will accumulate all journal postings by and against the accounting line for evaluation.

System Assurance

System Assurance 16

The System Assurance 16 job evaluates all processed transactions to see if a posting line is missing.

System Assurance