Results for “igs_fi_control_all”

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

Overview

IGS_FI_CONTROL_ALL is a configuration and control table within the Oracle E-Business Suite Student System (IGS) product family. The IGS product line is marked as obsolete in Oracle EBS 12.1.1 and 12.2.2, meaning it is retained only in legacy installations that have not migrated their student and financial aid processing to a successor application. Despite its obsolete status, the table remains structurally significant because it occupies a central position within the IGS financial integration schema.

According to the documented ETRM metadata, the table stores flags and reference pointers that govern the integration between IGS financial processing and Oracle Accounts Receivables, including a flag indicating whether Oracle Receivables is installed. The physical table is owned by the IGS schema and contains 46 documented columns in the 12.1.1 release.

From a modeling perspective, the heuristic Data Vault classification mined from its foreign-key structure suggests this object behaves as a link. This is consistent with its role: the table does not hold a business transaction but rather binds together account definitions, currency codes, date aliases, and general ledger code combinations into a single integration record. The single-row or near-single-row control semantic reinforces this link interpretation, since the primary key IGS_FI_CONTROL_PK is defined on REC_INSTALLED, a low-cardinality installation indicator rather than a true entity identifier.

Key Information Stored

The documented primary key is IGS_FI_CONTROL_PK, defined on the column REC_INSTALLED. This column functions as the surrogate key and simultaneously carries the installation status flag described in the object definition. Because the key is a status indicator, the table is expected to hold an extremely small number of rows — in practice a single configuration record per environment.

The most operationally significant columns fall into several groups:

• Integration control: REC_INSTALLED, ACCOUNTING_METHOD, ACCT_CONV_FLAG, CONV_PROCESS_RUN_IND, PLANNED_CREDITS_IND.
• Receivables defaults: BATCH_SOURCE_ID, CUST_TRX_TYPE_ID, TERM_ID, NEXT_INVOICE_NUMBER, AR_INT_ORG_ID.
• Accounting references: SET_OF_BOOKS_ID, ORG_ID, REC_GL_CCID, CASH_GL_CCID, UNAPP_GL_CCID, REFUND_DR_GL_CCID, REFUND_CR_GL_CCID.
• Account code foreign keys to IGS_FI_ACC_ALL: REC_ACCOUNT_CD, REV_ACCOUNT_CD, CASH_ACCOUNT_CD, UNAPP_ACCOUNT_CD, REFUND_DR_ACCOUNT_CD, REFUND_CR_ACCOUNT_CD.
• Date alias foreign keys to IGS_CA_DA: RES_DT_ALIAS, REFUND_DT_ALIAS, PRG_CHG_DT_ALIAS.
• Currency and refund routing: CURRENCY_CD (references FND_CURRENCIES), RFND_DESTINATION, AP_ORG_ID, DFLT_SUPPLIER_SITE_NAME.
• Audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

The business-key candidate documented in the metadata is the unique index IGS_FI_CONTROL_ALL_PK on REC_INSTALLED, which coincides with the surrogate key rather than identifying a separate natural key.

Common Use Cases and Queries

The principal use case is configuration validation. When an IGS financial interface fails, the standard diagnostic is to confirm that the control record exists and that the REC_INSTALLED flag reflects the true state of the Receivables installation. A representative query follows:

• SELECT rec_installed, accounting_method, set_of_books_id, org_id FROM igs_fi_control_all;
• SELECT currency_cd, rec_account_cd, rev_account_cd, cash_account_cd, unapp_account_cd FROM igs_fi_control_all;
• SELECT res_dt_alias, refund_dt_alias, prg_chg_dt_alias FROM igs_fi_control_all;

Reporting scenarios include auditing the default Receivables transaction type and batch source used by IGS fee interfaces, verifying that refund general ledger code combinations are populated before a refund run, and confirming that the accounting method and conversion flags are consistent between a source and target environment after a clone. Because the table is typically a single row, joins to it are usually unqualified scalar lookups rather than set-based associations.

Related Objects

The table sits at the junction of several IGS and Oracle Financials objects. The documented foreign keys identify the following dependencies:

• IGS_FI_ACC_ALL — referenced through REC_ACCOUNT_CD, REV_ACCOUNT_CD, CASH_ACCOUNT_CD, UNAPP_ACCOUNT_CD, REFUND_DR_ACCOUNT_CD, and REFUND_CR_ACCOUNT_CD. This is the dominant relationship and supplies the account code definitions used by the control record.
• IGS_CA_DA — referenced through RES_DT_ALIAS and REFUND_DT_ALIAS, supplying date alias definitions for reservation and refund processing.
• FND_CURRENCIES — referenced through CURRENCY_CD, providing the functional currency context for the IGS financial configuration.
• Oracle Receivables objects — implied by BATCH_SOURCE_ID, CUST_TRX_TYPE_ID, and TERM_ID, which point to Receivables batch sources, transaction types, and payment terms respectively.
• Oracle General Ledger — implied by SET_OF_BOOKS_ID and the GL_CCID columns, which reference code combinations in the ledger.

Consumers of this table include the IGS financial interface programs and any custom extension that performs fee assessment, receipting, or refunds on behalf of the Student System. Because the IGS product is obsolete, new development should treat IGS_FI_CONTROL_ALL as read-only reference data and avoid relying on it in designs intended for long-term support.