Purpose

This extract job highlights discrepancies between what has been paid/imported into COFI and what Callista reflects as the current status of Payments in the system.

Initially, after each run of the payments master job, INTJ0022, and then as required

This Extract Job compares records between the FEE_ASS and I_INVOICE_PAYMENT tables. Records that are inconsistent are made available for investigation via INTF0116.

The context for this job is described in the overview.

Run Details

This job is likely to be run concurrently with Debts Inconsistency Extract Job INTJ0117.

Job Conflict

There are no job conflicts for this job

Timing

The report would normally be run after running the finance interface master job, INTJ0022, which transfers payments from the external finance system to Callista and applies or re-applies payments to invoices.

For initial checking of system integrity, the report could be run after each run of INTJ0022. As long as errors are not encountered, institutions may then decide to schedule the report to run less frequently.

It would normally be run before end of financial year processing.

Checking on the Job Run

Always check the run log in form JBSF5301, to see that the job ran successfully. Custom built messages in the log indicate the outcomes for each component of the job.

The FAS COFI Payments Inconsistency Extract block contains:

Parameters Tab

• Fee Assessment Period:
• Currency:
• As At:
• Person ID Group Description:

Rules/Notes:

The Person ID Group (PIG) description must be unique.

Compare records in FEE_ASS table with I_INVOICE_PAYMENT table

When INTJ0116 is run an s_extract master record is created. This record holds Fee_cal_type, fee_ci_sequance_number, currency, description and the as at date that the job was run for. Records in the FEE ASS and I_INVOICE_PAYMENT are compared for the given fee period, due date and currency. When an inconsistency is identified, the record will be logged into the s_extract_record table and the person will be added to the INTJ0116 Person ID Group member (PIG).

• The number of records placed in the extract will be reported in the run log of the job
• The number of associated s_extract_records will be recorded in the s_extract master record. This field holds the job parameters and the number of inconsistent records

Rules/Notes:

The s_extract record holds the following data:

• S_EXTRACT_TYPE
• CREATION_DATE
• CUSTOMER_NUM
• PERSON_ID
• FEE_TYPE
• FEE_CAT
• COURSE_CD
• CSS_FEE_PAYMENT
• CSS_FEE_PAYMENT_TRANS_ID
• CSS_TAX_PAYMENT
• CSS_TAX_PAYMENT_TRANS_ID
• COFI_FEE_PAYMENT
• UNIT_CD
• UOO_ID