Search Results igs_fi_lb_fcis_pk

Overview

The IGS_FI_LB_FCIS table is a core technical component within the Oracle E-Business Suite Student System (IGS), specifically for the financial aid and fee management modules. Its primary function is to serve as a configuration and mapping table within the lockbox processing framework. A lockbox is a banking service where a financial institution processes incoming student payments directly and transmits the remittance data to the institution. This table defines the critical association between a specific bank code (as transmitted by the bank) and a specific fee calendar instance within the academic structure. This mapping is essential for the system to correctly apply received payments to the appropriate fee assessment period for a student.

Key Information Stored

The table stores a unique combination of lockbox configuration, bank identifier, and academic calendar data. The most critical columns are those comprising its primary and unique keys. The primary key (IGS_FI_LB_FCIS_PK) consists of LOCKBOX_NAME and BANK_CD, ensuring that for a given lockbox, each bank code is uniquely defined. A separate unique key (IGS_FI_LB_FCIS_UK1) on LOCKBOX_NAME, FEE_CAL_TYPE, and FEE_CI_SEQUENCE_NUMBER ensures that a fee calendar instance is not mapped more than once within the same lockbox context. Therefore, the table holds the BANK_CD value as provided in the lockbox file, and links it to the internal academic calendar identifiers (FEE_CAL_TYPE, FEE_CI_SEQUENCE_NUMBER) that identify a specific fee period.

Common Use Cases and Queries

The primary use case is during the automated import and application of lockbox payment data. When a payment file is processed, the system reads the bank code from the transaction record and queries this table, using the configured LOCKBOX_NAME and the incoming BANK_CD, to determine the correct fee calendar instance. This allows the system to post the payment against fees assessed for that specific term or session. A common diagnostic or setup validation query would join this table to the calendar instance table to list all mappings.

SELECT lb_fcis.lockbox_name,
       lb_fcis.bank_cd,
       lb_fcis.fee_cal_type,
       lb_fcis.fee_ci_sequence_number,
       ci.start_dt,
       ci.end_dt
FROM   igs_fi_lb_fcis lb_fcis,
       igs_ca_inst_all ci
WHERE  lb_fcis.fee_cal_type = ci.cal_type
AND    lb_fcis.fee_ci_sequence_number = ci.sequence_number
AND    lb_fcis.lockbox_name = '&LOCKBOX_NAME';

Related Objects

The IGS_FI_LB_FCIS table maintains strict referential integrity with two key parent tables, as defined by its foreign keys. The relationship to IGS_FI_LOCKBOXES via the LOCKBOX_NAME column ensures that a mapping cannot exist for an undefined lockbox configuration. Its relationship to IGS_CA_INST_ALL via the composite foreign key on FEE_CAL_TYPE and FEE_CI_SEQUENCE_NUMBER ensures that the mapped fee calendar instance is valid and exists within the system's academic calendar structure. These relationships are fundamental to maintaining data consistency between the lockbox banking interface and the core student academic and financial records.

• IGS_FI_LOCKBOXES: Parent table. Joined via IGS_FI_LB_FCIS.LOCKBOX_NAME = IGS_FI_LOCKBOXES.LOCKBOX_NAME.
• IGS_CA_INST_ALL: Parent table. Joined via IGS_FI_LB_FCIS.FEE_CAL_TYPE = IGS_CA_INST_ALL.CAL_TYPE AND IGS_FI_LB_FCIS.FEE_CI_SEQUENCE_NUMBER = IGS_CA_INST_ALL.SEQUENCE_NUMBER.