Search Results igs_ad_ct_hecs_payop_n1

Overview

IGS.IGS_AD_CT_HECS_PAYOP is a reference and cross-reference table within the Oracle E-Business Suite IGS (Student Systems) schema. It stores the mapping between an institution-defined admission category and the HECS payment options available to applicants processed under that category. The Higher Education Contribution Scheme (HECS) is the Australian higher-education funding scheme, and this table governs which payment arrangements, such as deferred or up-front contribution, may be assessed when fees are generated from an admission fee category. The table is therefore a configuration object rather than a transactional one: it controls downstream fee assessment behaviour for admission categories.

From a heuristic Data Vault modelling perspective, this object is best classified as a link table. It resolves a many-to-many relationship between admission categories and HECS payment option codes, each of which is represented by a separate hub or reference structure. The table carries no descriptive attributes beyond the standard Who columns, reinforcing its role as a pure association or bridging entity. The ETRM metadata records the object as VALID in both 12.1.1 and 12.2.2, and stores it in the APPS_TS_TX_DATA tablespace with a PCTFREE of 10, indicating a low-frequency, low-volatility configuration table.

Key Information Stored

The documented physical schema contains seven columns. The two most important are the composite business-key columns that form the primary key, IGS_AD_CT_HECS_PAYOP_PK, and the unique index IGS_AD_CT_HECS_PAYOP_U1:

• ADMISSION_CAT (VARCHAR2(10)) — Institution-defined admission category code. An admission category groups applicants whose applications are processed by a common set of admission procedure steps. This column participates in the unique index and is a foreign key to IGS_AD_CAT_ALL.
• HECS_PAYMENT_OPTION (VARCHAR2(10)) — The HECS payment option available to the admission category, for example 10 for deferred or 11 for up-front. This column is a foreign key to IGS_FI_HECS_PAY_OPTN and is also indexed non-uniquely via IGS_AD_CT_HECS_PAYOP_N1 to support reverse lookups.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle EBS Who columns capturing the audit trail of the row's creation and last modification.

No surrogate system-generated key is documented; the primary key is the natural composite of ADMISSION_CAT and HECS_PAYMENT_OPTION, which mirrors the unique index IGS_AD_CT_HECS_PAYOP_U1. Business users should treat this pair as the identifying business key.

Common Use Cases and Queries

Typical scenarios include auditing which payment options are enabled for a given admission category, validating configuration before fee assessment runs, and joining to descriptive reference data for reporting. The standard query pattern is a simple filter or join:

• List all payment options for a category: SELECT HECS_PAYMENT_OPTION FROM IGS.IGS_AD_CT_HECS_PAYOP WHERE ADMISSION_CAT = :cat;
• Resolve descriptions by joining to the payment option reference table: SELECT a.ADMISSION_CAT, p.HECS_PAYMENT_OPTION, p.DESCRIPTION FROM IGS.IGS_AD_CT_HECS_PAYOP a JOIN IGS.IGS_FI_HECS_PAY_OPTN p ON p.HECS_PAYMENT_OPTION = a.HECS_PAYMENT_OPTION;
• Find categories offering a specific option (using the N1 index): SELECT ADMISSION_CAT FROM IGS.IGS_AD_CT_HECS_PAYOP WHERE HECS_PAYMENT_OPTION = '10';

Reporting use cases include configuration extracts for fee assessment rules, data-migration reconciliation between legacy HECS setup and EBS, and compliance audits confirming that only approved payment options are enabled per category.

Related Objects

The most significant objects related to this table, per the documented foreign key relationships and dependencies, are:

• IGS.IGS_AD_CAT_ALL — referenced by ADMISSION_CAT; the master table of admission categories.
• IGS.IGS_FI_HECS_PAY_OPTN — referenced by HECS_PAYMENT_OPTION; the reference table of valid HECS payment options.
• APPS.IGS_AD_CT_HECS_PAYOP — the APPS synonym through which the table is normally queried.

The object does not reference any other database object, and it is referenced only through its APPS synonym, confirming its role as a leaf-level configuration table in the HECS payment option chain.