Search Results lockbox_name




Overview
Explore in AI Chat

Overview

The IGS_FI_LB_FCIS table is a core configuration table within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the Financials product family. Its primary role is to manage the mapping between external bank transaction codes and internal fee calendar instances for automated payment processing via lockboxes. When a bank transmits a file of customer payments (a lockbox file), it includes transaction codes. This table provides the critical lookup that the system uses to correctly interpret these incoming bank codes (BANK_CD) and associate them with the appropriate internal fee calendar instance (FEE_CAL_TYPE and FEE_CI_SEQUENCE_NUMBER) for a specific lockbox setup (LOCKBOX_NAME). This mapping is essential for the accurate and automated posting of fee-related revenues within the institution's general ledger.

Key Information Stored

The table stores a unique combination of lockbox configuration and fee calendar mapping. The most critical columns are the components of its composite primary key and the fee calendar identifiers. The LOCKBOX_NAME identifies the specific lockbox configuration. The BANK_CD holds the exact code supplied by the bank in its transaction files. The FEE_CAL_TYPE and FEE_CI_SEQUENCE_NUMBER together uniquely identify the internal fee calendar period to which the bank code corresponds. The table also includes standard Oracle EBS "Who" columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) for auditing. As per the metadata, the primary key constraint IGS_FI_LB_FCIS_PK enforces uniqueness on the combination of LOCKBOX_NAME and BANK_CD, meaning a single bank code can be mapped only once per lockbox.

Common Use Cases and Queries

The primary use case is the setup and maintenance of lockbox fee processing rules. Administrators populate this table to define how each distinct bank transaction code should be treated for revenue recognition. Common reporting and validation queries include listing all mappings for a specific lockbox or identifying unmapped bank codes. A typical query to audit existing mappings would be:

SELECT LOCKBOX_NAME, BANK_CD, FEE_CAL_TYPE, FEE_CI_SEQUENCE_NUMBER
FROM IGS.IGS_FI_LB_FCIS
WHERE LOCKBOX_NAME = '&LOCKBOX_NAME'
ORDER BY BANK_CD;

Another critical use case is troubleshooting lockbox processing errors. If a bank file fails to post fees correctly, a query joining this table to the lockbox transaction staging tables can verify if the incoming BANK_CD has a valid, active fee calendar mapping configured in IGS_FI_LB_FCIS.

Related Objects

Based on the provided relationship data, IGS_FI_LB_FCIS has defined foreign key relationships with two key tables, ensuring referential integrity for its configuration data.

  • IGS_FI_LOCKBOXES: The LOCKBOX_NAME column in IGS_FI_LB_FCIS references a valid lockbox definition in this table. This ensures mappings are only created for configured lockboxes.
  • IGS_CA_INST_ALL: The FEE_CAL_TYPE column in IGS_FI_LB_FCIS references a valid calendar type in this calendar instances table, linking the bank code to an existing fee calendar period.

The table itself is referenced by the APPS synonym IGS_FI_LB_FCIS, which is the standard access point for all application code and queries within the EBS environment. This structure centralizes the bank code mapping, making it a single point of configuration for downstream lockbox processing logic.