COFI Specialist Functions

Callista Open Finance Interface (COFI) Specialist Functions

This page provides the following information:

In Other Subsystems
In COFI

Setting Up the COFI Data

This section is written for the student records and financial system staff who have responsibility for setting up and maintaining the interface between Callista (primarily the Student Finance subsystem) and the institution's financial system external to Callista.

Extensive technical documentation is provided in the Callista Product Centre (wiki.callista.com.au/display/CPC), and this is likely to be the primary resource for specialist staff managing the interface. An assumption is that staff setting up the interface will have an understanding of external finance system applications.

To understand COFI, familiarity with the following will be especially useful:

The general overview, Understanding Callista Open Finance Interface and job and report documentation linked from that overview.
Callista's Student Finance subsystem (Student Finance Table of Contents).
Callista's Calendar subsystem (Calendar Table of Contents) and Job Control and Scheduling subsystem (JBS Table of Contents).

In Other Subsystems

This table lists data in the Student Finance and other subsystems that must be in place for interface processing, and provides links to further documentation as appropriate.

Reference Data	Purpose	Mandatory ?	Maintenance Form
Student Finance
Account Codes	Account Codes of system account type REVENUE, and where applicable TAX, must be established for each fee type (see Account Codes in Special Topics). The same Account Codes must also exist for the General Ledger in the external financial system.	Yes	FINF1800 FINF2110 (access via FINF2100)
Fee Structure Status	Maps to System Fee Structure Status FINALISED - used to set fee period calendars for final processing in an interface cycle (see Matching Receipts).	Yes	FINF1200
Payment Rank	To establish the position of a fee liability in the payment hierarchy which determines the order in which invoices get paid (see Payment Hierarchy in Special Topics).	Yes	FINF2100 FINF2800
Person ID Type	To record a Person ID Type against the PAY_ADV_NO system Person ID Type in order to store payment advice numbers as students' Alternate Person IDs (see documentation for ENRF3010). It is recommended that only one Person ID Type is mapped to the system ID type.	Yes	ENRF01B0
Payment Advice Numbers	Note that these are created automatically by the system for each student and sponsor (see documentation in ENRF3010 and FINF4100).		Not maintained by users.
External Reference Type	External reference types of RECEIPT , INVOICE_AR and INVOICE_AP are recorded by the system. They appear in the form FINF1A00, and should not be deleted.	Required	Value recorded by system.
Job Control And Scheduling
Job Conflicts	To prevent different instances of the same job from running concurrently, and to prevent a job running at the same time as other named jobs (see JBSF4110). No master job in COFI should run with any other COFI job, and none should have more than one instance running at the same time.	Yes	COFI is released with recommended job conflicts already set up.
Run Window	It is recommended that a special Run Window (e.g. INT_HOURS) is used for the finance interface, to enable direction of interface jobs to a specific batch queue or queues.		JBSF4410 JBSF4500

In COFI

The following points deal with COFI requirements:

When initially establishing the interface, the customer base of students and sponsors will need to be initially loaded using SQL code supplied as a part of the release.
The control/configuration table I_INT_CONTROL must be set up. This table is edited directly and only contains one record. These entries are required in the I_INT_CONTROL table:
- The method of transferring invoice data must be specified. A value of Y in INV_SUMMARY_IND indicates that COFI uses invoice summary as its method of transferring invoice data. Similarly a value of Y in DEBIT_MEMO_SUMMARY_IND indicates that the invoice data for refunds is summarised in I_INVOICE_SUMMARY. See the Callista Development Centre - wiki.callista.com.au/display/CDC for more information.
- The number of days to check when reconciling Debit Memos for Invoice Summary against Invoices must be specified in INVSUM_DEBMEM_CHK_DAYS. This is used when running a consistency report between Invoice and Invoice Summary.
- If DESIGNATED_MODEL_IND is set to 'Y' in the I_INT_CONTROL then the institution follows the COFI designated payment model. This affects the way in which payments are matched and the way in which sponsors payments can be allocated. It is also means that a different set of jobs and forms is available to the the user. For more information see COFI Designated Payment model.

For more information, see the Callista Product Centre (wiki.callista.com.au/display/CPC).

Last modified on 12 November, 2015 4:12 PM

History Information

Release Version	Project	Change to Document
18.0.0.2	2146 - VU Payment Matching.	Added note about DESIGNATED_MODEL_IND setting in I_INT_CONTROL.
18.0.0.2	2011 - Calipso 41512	Updated reference and link to the CPC wiki space.