Search Results igs_fi_a_hierarchies_u2

Overview

The IGS_FI_A_HIERARCHIES table is a core data repository within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the Oracle Student Financials module. It serves as the master table for storing the definition of application hierarchies. These hierarchies are critical configuration entities that govern the order and priority in which payments, credits, or other financial transactions are applied to student accounts. The table captures the setup information entered through the "Define Application Hierarchy" form, establishing the foundational rules for the automated application of funds within the institution's financial management processes.

Key Information Stored

The table's structure is designed to manage hierarchical definitions with versioning and effective dating. The primary key, APPL_HIERARCHY_ID, is a system-generated unique identifier. Each hierarchy is defined by a mandatory HIERARCHY_NAME and a VERSION_NUMBER, allowing for multiple iterations of a hierarchy over time. The EFFECTIVE_START_DATE and EFFECTIVE_END_DATE columns control the active period for each version, enabling temporal validity. A DESCRIPTION field provides contextual details. Notably, the CREDIT_TYPE_ID column is documented as "No Longer Used," indicating legacy functionality. Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) track audit information for all rows.

Common Use Cases and Queries

The primary use case is to retrieve active application hierarchy definitions for runtime processing or configuration reporting. A common query involves fetching the current, effective hierarchy for a specific name to inform the transaction application engine. For instance, to find all active hierarchies as of the current date:

• SELECT HIERARCHY_NAME, VERSION_NUMBER, DESCRIPTION FROM IGS_FI_A_HIERARCHIES WHERE SYSDATE BETWEEN EFFECTIVE_START_DATE AND NVL(EFFECTIVE_END_DATE, SYSDATE) ORDER BY HIERARCHY_NAME, VERSION_NUMBER;

Technical implementations, such as concurrent programs or backend APIs, will frequently query this table using the APPL_HIERARCHY_ID from related transactional or setup tables. Reporting on hierarchy setup and version history is another key use case, often joined with FND_USER tables via the WHO columns to display creator and updater information.

Related Objects

Based on the provided dependency information, the IGS_FI_A_HIERARCHIES table is referenced by other objects within the APPS schema. The unique index IGS_FI_A_HIERARCHIES_U1 on APPL_HIERARCHY_ID and the unique index IGS_FI_A_HIERARCHIES_U2 on the combination of HIERARCHY_NAME, VERSION_NUMBER, and EFFECTIVE_START_DATE are critical for enforcing data integrity and are likely referenced by foreign key constraints in dependent tables. While specific related table names are not listed in the excerpt, typical related objects in this functional area would include tables storing hierarchy details (e.g., hierarchy nodes or rules) and transactional tables that store a foreign key reference to APPL_HIERARCHY_ID to determine the application rule set used for a given financial item.