Cycle Notes (MEMBER.BAT)

Between the time the remittance has been authorized and the next cycle is opened for processing, a series of batch jobs is initiated to perform various update functions.  Refer to

Auxiliary Activities

Submitting Batch Jobs

 

The process is separated into three distinct steps.  The batch jobs will stop on any known error, and then continue with the next pay centre.  Error logs are available for viewing, and these can be used to ascertain the status of jobs in progress, and also to establish why any of the batch jobs may have failed.  Each of the steps is described briefly below, as well as which error log to view for errors arising out of each of the steps.

 

Step 1

This step determines what has changed, it does the necessary validations, and it creates the input files for Step 2.  The error log for this step can tell whether the job has started, finished, or is in progress.  To view the error log, from the main menu on the web, select System Administration, then from the sub-menu on the left, select View Log Status.

 

Step 2

This step is the member load (BJU3AR) that processes the changes. 

 

Note:

If a new salary record has been created and the membership status is EXIT IN PROCESS or EXIT FINALISED, an exits for revision report will be created and a warning message will be written to the error log.  In addition, the Salary Changes after Exit report will display all of these cases under scheme reports.

 

If the Identity Type is South African then the system will validate that the same ID Number does not exist on the system.

 

For more information on viewing the error log, refer to

Reports

General

Error Log Report

 

For more information on the Salary Changes after Exit report, refer to Salary Changes after Exit in

Reports

Payroll

 

Step 3

This step creates the money file.  If there are errors, these can only be corrected by the Vendor providing a script, or by the business reversing the errors.  Most problems encountered will originate from this step, and are usually anything that involves monies.  Errors are viewed on the master log.  Refer to

Processes

Contributions

Income

General

Master Log

 

Once Step 3 has been completed, the file can be viewed, and the batch can be submitted.  For information on viewing the file and submitting batches, refer to

Processes

Contributions

Income

Income

Select Batch

 

Once the batch has been submitted, program BJW1AE will be triggered.  Any errors will be available for viewing on the master error log.  Refer to

Processes

Contributions

Income

General

Master Log

 

Once the batch file has been successfully submitted, it will be available for viewing.  Refer to

Processes

Contributions

Income

Income

Authorising Batches

 

Once the batch has been confirmed, program BJU3AH will be triggered.  Any errors will be available for viewing on the error log.  For more information on viewing the error log, refer to

Reports

General

Error Log Report

 

If the batch is rejected under Auth Batch, it will become available again under Select Batch.

 

There may be instances where a batch needs to reloaded (e.g. to recreate the money file because the remittance was authorized with the wrong values).  The batch can be reloaded only if it hasn't been authorized yet (i.e. the file must be viewable under Select Batch).  If the batch is only viewable under Auth Batch, it must first be selected, then rejected.

 

For more information on authorising batches, refer to

Processes

Contributions

Income

Income

Authorising Batches