Results for “igs_fi_lb_fcis”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The IGS_FI_LB_FCIS table resides in the IGS (Student System) schema of Oracle E-Business Suite and serves as a configuration bridge within the Student System Financials lockbox processing framework. Its documented purpose is to map bank codes to fee calendar instances for a given lockbox in context, allowing the system to associate incoming lockbox payments with the correct fee calendar and sequence used for fee assessment and reconciliation.

From a data modeling perspective, the ETRM metadata classifies IGS_FI_LB_FCIS heuristically as a link entity. This classification reflects its structure: the table carries no descriptive attributes of its own beyond standard WHO audit columns, and instead resolves the many-to-many relationship between lockboxes and fee calendar instances. It therefore functions as an intersection table between IGS_FI_LOCKBOXES and IGS_CA_INST_ALL, with the composite unique index reinforcing that each lockbox/calendar instance pairing is recorded only once.

Key Information Stored

The table contains nine documented columns. The most significant are:

• LOCKBOX_NAME — Identifies the lockbox definition; participates in both the primary key and the unique business key, and is a foreign key to IGS_FI_LOCKBOXES.
• BANK_CD — The bank code associated with the lockbox; the second component of the primary key IGS_FI_LB_FCIS_PK.
• FEE_CAL_TYPE — The fee calendar type to which the lockbox is mapped; part of the unique key IGS_FI_LB_FCIS_UK1 (or IGS_FI_LB_FCIS_U1) and a foreign key into IGS_CA_INST_ALL.
• FEE_CI_SEQUENCE_NUMBER — The calendar instance sequence number within the fee calendar type; completes the unique business key and the foreign key to IGS_CA_INST_ALL.
• CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard Oracle WHO audit columns capturing row creation and modification metadata.

The primary key is the surrogate/composite identifier IGS_FI_LB_FCIS_PK (LOCKBOX_NAME, BANK_CD). The business-key candidates are the unique indexes: IGS_FI_LB_FCIS_UK1 on (LOCKBOX_NAME, FEE_CAL_TYPE, FEE_CI_SEQUENCE_NUMBER) and the primary key constraint itself. Note that BANK_CD is not part of the unique business-key index, indicating that the calendar instance mapping is unique per lockbox regardless of bank code.

Common Use Cases and Queries

Typical usages include validating lockbox-to-fee-calendar configuration, troubleshooting why an incoming lockbox payment failed to match a fee calendar instance, and producing setup reports for financial aid or receivables implementations.

• Retrieve the fee calendar mapping for a specific lockbox:

  SELECT lockbox_name, bank_cd, fee_cal_type, fee_ci_sequence_number
  FROM   igs.igs_fi_lb_fcis
  WHERE  lockbox_name = :p_lockbox;

• Reconcile all lockboxes against their fee calendar instance definitions by joining to IGS_CA_INST_ALL on FEE_CAL_TYPE and FEE_CI_SEQUENCE_NUMBER.
• Identify lockboxes that have no calendar instance mapping (orphan or incomplete setup) using an outer join to IGS_FI_LOCKBOXES.
• Audit configuration changes over time using the LAST_UPDATE_DATE and LAST_UPDATED_BY columns.

Related Objects

The FK relationships documented in the metadata identify the following dependent and referenced objects:

• IGS_FI_LOCKBOXES — Parent table; joined on IGS_FI_LB_FCIS.LOCKBOX_NAME = IGS_FI_LOCKBOXES.LOCKBOX_NAME.
• IGS_CA_INST_ALL — Parent table; joined on FEE_CAL_TYPE and FEE_CI_SEQUENCE_NUMBER to resolve the fee calendar instance.
• IGS_FI_LB_FCIS_PK / IGS_FI_LB_FCIS_UK1 — Constraints enforcing key uniqueness.
• Broader lockbox processing logic in the IGS Financials module, which consults this mapping during payment import and fee matching.