Results for “appl_hierarchy_id”

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

Overview

IGS_FI_A_HIERARCHIES is a configuration table within the Oracle E-Business Suite Student System (IGS) module, historically delivered as part of Oracle's higher-education application set. The table stores application hierarchy definitions created through the Define Application Hierarchy form. Each hierarchy associates a named, versioned grouping of application rules with a specific credit type, allowing institutions to model how financial aid or credit-related application logic is organized and sequenced.

The product designation "IGS - Student System (Obsolete)" indicates that this object is no longer actively implemented in current database instances. The ETRM metadata explicitly notes "Not implemented in this database," meaning the table exists in the data model and documentation but is not physically populated or maintained in supported releases. In Oracle EBS 12.1.1, the documented physical schema shows the table owned by the IGS schema with 12 columns. In 12.2.2, the same logical structure is referenced, though the online patching editioning model may alter how such obsolete objects are handled during upgrades.

A heuristic Data Vault classification of this table suggests a hub-leaning role: APPL_HIERARCHY_ID functions as a durable business key that is referenced by multiple dependent tables, which is characteristic of a hub entity. This is a modeling suggestion rather than a documented fact.

Key Information Stored

The table's primary key is IGS_FI_A_HIERARCHIES_PK, defined on APPL_HIERARCHY_ID. This surrogate identifier uniquely distinguishes each hierarchy record and is the column referenced by dependent foreign keys throughout the IGS financial aid schema.

Two unique indexes supply business-key candidates. IGS_FI_A_HIERARCHIES_U1 is defined on APPL_HIERARCHY_ID alone, reinforcing the primary key. IGS_FI_A_HIERARCHIES_U2 is a composite unique index across HIERARCHY_NAME, VERSION_NUMBER, and EFFECTIVE_START_DATE, indicating that a hierarchy name may be versioned over time, with each version taking effect on a specific date.

• APPL_HIERARCHY_ID — surrogate primary key and the join column used by all child tables.
• HIERARCHY_NAME — the user-defined name of the application hierarchy.
• VERSION_NUMBER — version identifier enabling multiple iterations of the same named hierarchy.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — date-range validity columns supporting time-based versioning.
• CREDIT_TYPE_ID — foreign key to IGS_FI_CR_TYPES_ALL, linking the hierarchy to its associated credit type.
• DESCRIPTION — free-text description of the hierarchy's purpose.
• Audit columns — LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, CREATED_BY, and CREATION_DATE provide standard EBS row-level audit tracking.

Common Use Cases and Queries

Because the table is obsolete and not implemented in documented databases, reporting queries are primarily of interest for migration analysis, historical data reconstruction, or impact assessment when upgrading from 12.1.1 to 12.2.2. A typical query retrieves the current effective hierarchy for a given credit type:

SELECT h.appl_hierarchy_id, h.hierarchy_name, h.version_number, h.effective_start_date, h.effective_end_date FROM igs_fi_a_hierarchies h WHERE h.credit_type_id = :credit_type_id AND SYSDATE BETWEEN h.effective_start_date AND NVL(h.effective_end_date, SYSDATE);

Another common pattern joins the hierarchy to its dependent application rules to enumerate the rule set associated with each hierarchy version. Analysts performing data lineage or Data Vault modeling exercises also use this table as a hub candidate, tracing APPL_HIERARCHY_ID references across satellite and link structures.

Related Objects

The most significant related objects are defined through foreign key relationships documented in the ETRM metadata.

• IGS_FI_CR_TYPES_ALL — referenced from IGS_FI_A_HIERARCHIES.CREDIT_TYPE_ID; also holds APPL_HIERARCHY_ID, creating a bidirectional association between credit types and hierarchies.
• IGS_FI_APPLICATIONS — references IGS_FI_A_HIERARCHIES via APPL_HIERARCHY_ID, tying individual applications to their governing hierarchy.
• IGS_FI_APP_RULES — references IGS_FI_A_HIERARCHIES via APPL_HIERARCHY_ID, storing the rule definitions that execute within a hierarchy.

These three dependent tables form the core of the application hierarchy framework. Any archival or migration effort involving IGS_FI_A_HIERARCHIES must account for these relationships to preserve referential integrity, particularly since the parent object is marked obsolete and may not be carried forward in supported 12.2.2 environments.