Top of COFI | Interface Index | Index | Table of Contents | Feedback |
INTJ0020 - Prepare Customers For Transfer to External System
Purpose |
To prepare Customer records for transfer to an external system. |
|
Subsystem | Callista Open Finance Interface | |
Normally Run By | A Fees Specialist | |
Anticipated Frequency | At the start of a Fee Period, and then generally as an integral part of an Invoice job, in a planned cycle. | |
Structure | Block | Process Finance Customers |
Tab | Parameters |
There are two ways to use INTJ0020. With or without the Test for Student and Sponsor Activity. INTJ0020 will always run Prepare Customer Records for Transfer to External System, regardless if the checkbox is selected or not. If the check box is selected, it will ALSO Test for Student and Sponsor Activity. Beware of the extra time required if the check box is selected. Processes write data to customer records, update transfer statuses and create or update customer information in a customer table (I_FIN_CUSTOMER table) The modules of this job can be incorporated into the invoices INTJ0021. The context for this job is described in the overview. Run
Details Job
Conflict Transfer
Statuses
Timing Running Test for Student and Sponsor Activity can be used as a cleanup process. This should only be used if the Target System sets an Inactive status, as the process can take a long time. As such it might be run only once a year, as part of an initial run at the start of a new financial period. Error Handling
Checking
on the Job Run If the system is not configured to continue job processing for COFI jobs the job log could be helpful in explaining why, if INTJ0022 FAILED. 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. If the system is configured for COFI jobs to continue processing then the job log will contain a Summary which includes:
Important: Note that in order for this summary information to be included in the run log, the PASS_RJR_ID_IND value for this job, must be set to 'Y' in the S_JOB table. To view the job log, see JBSF5301 (via JBSF5300). To view system error details see GENF0001. |
The Process Finance Customers block contains: Parameters Tab This job:
Optionally:
|
|
Prepare Customer Records for Transfer to External System This picks up customer records with a value of TODO in the transfer status field and carries out preliminary tasks to prepare records for transfer. It is quite possible that several TODO records will exist in the I_FIN_CUSTOMER table for a single student or Sponsor. For example, a record will be created for a new student both on offer of a place and when a student course attempt record is created through pre-enrolment. Since only one TODO record per customer is needed to prompt action, the first task is to physically delete all but the most recent record with this status from the I_FIN_CUSTOMER table. As a further housekeeping task, the module also logically deletes fully processed records in the table, with the exception of the most recent. These are records where data has been successfully transferred to the external system. Information for transfer is retrieved from the Student Finance database and written to the appropriate records in I_FIN_CUSTOMER. For a Student, these are the details written to the record:
For a Sponsor, these are the details written:
For a Loan Scheme, these are the details written:
|
Rules/Notes: A person that is a Student and a Sponsor is recognised as a Student by their Person ID and as a Sponsor by their Sponsor code. Payment Advice Number is generated for them the first time a person payment schedule is created. Batch number and batch date columns are added to the transfer table of I_FIN_CUSTOMER table to support the batch loading of export data. In addition, columns for generic attributes are added for future development. SPON_PERSN
are for Sponsors who are persons in the system. |
Test for Student and Sponsor Activity check box This is typically run at the start of a new interface cycle to perform a 'cleanup operation' for customers who have been active in a previous cycle, but are now inactive. For all active customers in the I_FIN_CUSTOMER table, the process checks Student Finance data for student or Sponsor activity, as appropriate. If either is discovered to be no longer active, a TODO customer record is created in I_FIN_CUSTOMER. ConditionsA Student is regarded as inactive if all the following conditions are met:
A Sponsor is regarded as inactive if these conditions are met:
A Loan Scheme is always reported as Active
If a currently inactive customer becomes active again in Student Finance, this triggers another TODO record, and the customer reverts to Active on the database. |
Rules/Notes: A student reverting from Discontinued to an Active status will trigger a new TODO record. For the latest TODO record details are written to the file. TRANSFER STATUS of this record is set to READY. If the checkbox is not selected, the Customer_cat column in I_FIN_CUSTOMER file will be null |
Last Modified on: 11-Oct-2010 4:29 PM
History Information
Release Version | Project | Change to Document |
11.0.0.0.0.0. | 1350 - Job Error Handling | Added details relating to error handling and log entries |