Results for “entity_type_code”

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

Overview

IGS_FI_HIER_ACCT_TBL is a table within the IGS (Student System) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. The documented metadata classifies IGS as obsolete, and the table is marked "Not implemented in this database" in the reference ETRM documentation. It captures the entities that participate in an account hierarchy together with their respective ordering within that hierarchy. In practical terms, it functions as an ordered membership or sequencing table that positions each entity relative to an account hierarchy defined elsewhere in the IGS financial aid account structure.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign key structure is satellite-leaning. That is a modeling suggestion rather than a normative designation: the table behaves as a descriptive, attribute-bearing child of a parent hierarchy definition rather than as an independent hub or a pure association link. The presence of an ORDER_SEQUENCE attribute and an ENTITY_TYPE_CODE reinforces the satellite interpretation, since these are descriptive properties of a parent entity rather than independent business keys.

Key Information Stored

The table contains nine documented columns. The most significant are:

• ACCT_TBL_ID — the surrogate primary key, backed by the IGS_FI_HIER_ACCT_TBL_PK constraint and the unique index IGS_FI_HIER_ACCT_TBL_U1. It uniquely identifies each row in the table.
• ACCT_HIER_ID — the foreign key referencing IGS_FI_HIER_ACCOUNTS. This column links each row to the parent account hierarchy definition and is the principal join path for the table.
• ORDER_SEQUENCE — the ordinal position of the entity within the hierarchy. This is the attribute that distinguishes the table as a sequencing record rather than a simple membership record.
• ENTITY_TYPE_CODE — identifies the type of entity being placed in the hierarchy, allowing a single hierarchy to reference heterogeneous entity categories.
• CREATED_BY, CREATION_DATE — standard Oracle EBS WHO columns recording row creation audit information.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns capturing the most recent modification and the login context under which it occurred.

No non-key business attribute other than ORDER_SEQUENCE and ENTITY_TYPE_CODE is documented, and only ACCT_TBL_ID is listed as a unique index candidate. ACCT_HIER_ID is therefore a non-unique foreign key, meaning a single hierarchy may have many ordered entity entries.

Common Use Cases and Queries

The primary reporting use case is reconstructing the ordered structure of an account hierarchy. A typical query joins the table to its parent hierarchy definition and orders rows by the sequence column:

• SELECT h.ACCT_HIER_ID, t.ACCT_TBL_ID, t.ENTITY_TYPE_CODE, t.ORDER_SEQUENCE FROM IGS_FI_HIER_ACCT_TBL t, IGS_FI_HIER_ACCOUNTS h WHERE t.ACCT_HIER_ID = h.ACCT_HIER_ID ORDER BY t.ACCT_HIER_ID, t.ORDER_SEQUENCE;
• Filtering by ENTITY_TYPE_CODE to isolate entries of a particular entity category within a hierarchy.
• Aggregating COUNT(*) grouped by ACCT_HIER_ID to validate that each hierarchy contains the expected number of ordered entities.
• Detecting sequence gaps or duplicates within a hierarchy using analytic functions such as LAG or ROW_NUMBER over ORDER_SEQUENCE partitioned by ACCT_HIER_ID.

Because the object is documented as not implemented and the product is obsolete, these patterns are primarily relevant to migration analysis, legacy data extraction, or historical reference.

Related Objects

• IGS_FI_HIER_ACCOUNTS — the parent table referenced by the ACCT_HIER_ID foreign key; joins on IGS_FI_HIER_ACCT_TBL.ACCT_HIER_ID = IGS_FI_HIER_ACCOUNTS.ACCT_HIER_ID.
• IGS_FI_HIER_ACCT_TBL_PK — the primary key constraint on ACCT_TBL_ID.
• IGS_FI_HIER_ACCT_TBL_U1 — the unique index on ACCT_TBL_ID, confirming the surrogate key.
• Other IGS financial aid hierarchy tables sharing the IGS_FI_HIER prefix, which in a full implementation would participate in the same account hierarchy domain.

No additional referencing tables, views, or APIs are documented in the supplied metadata.