Results for “igs_fi_control_pk”

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

Overview

The IGS_FI_CONTROL table belongs to the IGS (Student System) product family, which is documented in Oracle E-Business Suite as an obsolete module. Its stated purpose, per the ETRM metadata, is narrow and specific: it stores a flag indicating whether Oracle Accounts Receivables (AR) is installed in the environment. This makes the table a control or configuration artifact rather than a transactional or master-data entity. It does not participate in the day-to-day flow of student financial data; instead, it serves as a runtime decision point that allows IGS financial integration logic to determine whether AR-dependent processing paths should be enabled.

Because the metadata explicitly states "Not implemented in this database," the table is effectively dormant in this instance. It is a legacy object retained for compatibility with the historical IGS Financials integration architecture. The heuristic Data Vault classification mined from the foreign key structure is standalone. In Data Vault modeling terms, this suggests the table is neither a hub, link, nor satellite in any meaningful sense, since it holds no business keys that participate in relationships and no foreign key dependencies. It is best modeled as an isolated reference or control table if represented in a modernized schema.

Key Information Stored

The metadata documents an unusually small column set. The primary key is IGS_FI_CONTROL_PK, and the only explicitly named column is REC_INSTALLED.

• REC_INSTALLED — The sole documented column, holding the flag that records whether Oracle Receivables is installed. This is the functional payload of the table. In practice, such a flag is typically a single-character or numeric indicator (for example, "Y"/"N" or 1/0), though the metadata does not specify the datatype.
• IGS_FI_CONTROL_PK — The surrogate primary key constraint defined on the table. Per the metadata, the primary key is composed of REC_INSTALLED, which means the key is the flag column itself rather than a synthetic identifier.

Because REC_INSTALLED doubles as both the primary key and the only functional column, there is no separate surrogate-versus-business-key distinction to draw. The table has no documented unique secondary indexes and no foreign key columns. Its extreme narrowness is consistent with a single-row control table design, where the presence, absence, or value of one row governs downstream behavior.

Common Use Cases and Queries

The principal use case is a pre-flight check within IGS financial integration routines. Before invoking AR-dependent logic — such as creating receivables transactions, validating customer accounts, or posting charges — application code would query this table to confirm AR availability. A representative pattern is:

• Querying the flag: SELECT rec_installed FROM igs_fi_control WHERE rec_installed = 'Y';
• Existential verification: SELECT COUNT(*) FROM igs_fi_control; — used to confirm whether the control record has been initialized.
• Diagnostic reporting to determine whether the IGS-AR integration switch is active in a given environment.

Because the object is obsolete and not implemented, these queries are relevant primarily for historical analysis, migration assessment, or documentation of legacy integration behavior. Reporting use cases are limited to configuration audits and upgrade impact analysis.

Related Objects

The metadata documents no foreign key relationships, and the Data Vault classification is standalone. Consequently, no join columns can be identified from documented facts. The table's logical dependents are the IGS Student System integration programs and concurrent processes that read the flag to decide whether to call Oracle Receivables APIs. In the broader EBS context, the meaningful related objects are therefore the AR application modules and their public APIs rather than other database tables. Any concrete join relationships would require inspection of the obsolete IGS financial integration code, which the provided metadata does not enumerate.