Results for “closed_flag”

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

Overview

The IGS.IGS_FI_ELM_RNG_ORDS table is a foundational reference object within the Oracle E-Business Suite Student System (IGS) product family. It stores element range order definitions, which control the sequencing in which attributes are evaluated when the Fee Calculation engine computes a student's fees. Because fee computation in Oracle Student System frequently depends on the order in which element ranges and their attributes are applied, this table provides the authoritative naming and descriptive framework used by downstream pricing and calculation logic.

In Oracle EBS 12.1.1 and 12.2.2, the table resides in the IGS schema and is reported with a VALID status in the ETRM data dictionary. The documented physical schema lists nine columns. Its heuristic Data Vault classification is hub-leaning, which suggests a modeling approach in which IGS_FI_ELM_RNG_ORDS functions as a hub of order-name business keys, with descriptive attributes and transactional detail distributed to satellite or dependent detail tables. This classification is a modeling suggestion rather than a physical constraint enforced by the application.

Key Information Stored

The primary key IGS_FI_ELM_RNG_ORDS_PK is defined on the single column ELM_RNG_ORDER_NAME. This column is therefore both the surrogate primary key and the sole documented business-key candidate, since no additional unique indexes are recorded in the ETRM metadata. The most significant columns are:

• ELM_RNG_ORDER_NAME — The unique identifier and order name that governs attribute sequencing during fee computation.
• ELM_RNG_ORDER_DESC — A descriptive label for the order definition, used in setup forms and reporting.
• ELM_RNG_ORDER_ATTR_CODE — The attribute code associated with the order, linking the order to a specific fee attribute.
• CLOSED_FLAG — Indicates whether the order definition is active or inactive for new fee computation events.
• CREATED_BY, CREATION_DATE — Audit columns capturing the creating user and timestamp.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns recording the most recent modification user, timestamp, and login session.

The audit columns follow the standard Oracle Applications WHO column convention and are populated automatically by the forms and concurrent processing infrastructure.

Common Use Cases and Queries

Typical usage centers on setup validation, fee calculation troubleshooting, and reporting on active order definitions. A common query lists all open order definitions with their descriptions and associated attribute codes:

• SELECT elm_rng_order_name, elm_rng_order_desc, elm_rng_order_attr_code FROM igs.igs_fi_elm_rng_ords WHERE closed_flag = 'N';
• Joining to the detail table IGS_FI_ER_ORD_DTLS to review the full ordering hierarchy: SELECT o.elm_rng_order_name, d.* FROM igs.igs_fi_elm_rng_ords o, igs.igs_fi_er_ord_dtls d WHERE o.elm_rng_order_name = d.elm_rng_order_name;
• Audit reconciliation queries using created_by, creation_date, last_updated_by, and last_update_date to track configuration drift between environments.

These patterns are frequently used during implementation cutover, when verifying that fee element range orders are correctly seeded and that no obsolete (closed) orders remain active in production.

Related Objects

The documented foreign-key relationship identifies IGS_FI_ER_ORD_DTLS as the principal dependent object. Its column ELM_RNG_ORDER_NAME references IGS_FI_ELM_RNG_ORDS.ELM_RNG_ORDER_NAME, forming a parent-child relationship between order headers and order detail lines. The significant related objects are:

• IGS_FI_ER_ORD_DTLS — Detail table referencing this table via ELM_RNG_ORDER_NAME.
• IGS_FI_ELM_RNG_ORDS_PK — The primary key index supporting lookups on ELM_RNG_ORDER_NAME.
• Fee calculation and element range processing logic within the IGS Financials module that consumes order names during attribute sequencing.
• Concurrent programs and setup forms that maintain order definitions and their closed status.

Because only one inbound foreign key is documented, referential integrity for this table is relatively contained, and its principal integration point remains the order detail table.