Results for “qual_period_start_date”

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

Overview

The IGS_HE_SUB_RTN_QUAL table belongs to the IGS (Student System) product family within Oracle E-Business Suite, and is documented in ETRM as an obsolete component. Its stated purpose is to store the Qualifying Period details associated with a DLHE (Destinations of Leavers from Higher Education) Submission Return. In practical terms, the table defines the qualifying reference periods — census, survey, and reporting windows — that govern how a DLHE return is assembled and validated for a given submission.

ETRM notes that this object is not implemented in the database in the documented 12.1.1 environment, meaning the table may exist only in legacy or reference schemas rather than active production instances. The Data Vault classification derived heuristically from the foreign key structure is satellite-leaning: the table is keyed entirely by business attributes and carries descriptive period data rather than introducing new hubs or connections between hubs. Under a Data Vault model, this pattern would typically be represented as a satellite attached to the submission return hub, with the qualifying period code acting as a descriptive discriminator.

Key Information Stored

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

• SUBMISSION_NAME, USER_RETURN_SUBCLASS, RETURN_NAME, QUAL_PERIOD_CODE — the composite primary key IGS_HE_SUB_RTN_QUAL_PK, which also serves as the unique business-key candidate. Together these identify a qualifying period within a specific return class of a submission.
• QUAL_PERIOD_DESC, QUAL_PERIOD_TYPE — the descriptive label and category of the qualifying period (for example, census-based or survey-based).
• QUAL_PERIOD_START_DATE, QUAL_PERIOD_END_DATE — the effective start and end boundaries of the qualifying period itself.
• CENSUS_DATE — the census reference date tied to the return, used for student population snapshots.
• SURVEY_START_DATE, SURVEY_END_DATE — the survey response window associated with the qualifying period.
• CLOSED_IND — a flag indicating whether the period has been closed to further activity.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS auditing columns.

There is no separate surrogate key column in the documented schema; the primary key is composed entirely of business dimensions, so the PK doubles as the natural business key.

Common Use Cases and Queries

Typical reporting and validation scenarios include identifying which qualifying periods are open, comparing census and survey dates for a return, and confirming that a DLHE return's periods are correctly defined. A representative query listing active periods for a submission would use:

SELECT submission_name, user_return_subclass, return_name, qual_period_code, qual_period_desc, qual_period_start_date, qual_period_end_date FROM igs_he_sub_rtn_qual WHERE closed_ind = 'N' AND submission_name = :p_submission_name;

A further pattern joins the qualifying periods back to the student-level DLHE records to reconcile period codes against collected data:

SELECT q.qual_period_code, COUNT(s.student_id) FROM igs_he_sub_rtn_qual q, igs_he_stdnt_dlhe s WHERE q.submission_name = s.submission_name AND q.user_return_subclass = s.user_return_subclass AND q.return_name = s.return_name AND q.qual_period_code = s.qual_period_code GROUP BY q.qual_period_code;

Related Objects

The table participates in two documented foreign key relationships:

• IGS_HE_SUBMSN_RETURN — the parent return definition. IGS_HE_SUB_RTN_QUAL.SUBMISSION_NAME, USER_RETURN_SUBCLASS, and RETURN_NAME reference this table, making it the primary parent in the hierarchy.
• IGS_HE_STDNT_DLHE — the student-level DLHE data. This table references IGS_HE_SUB_RTN_QUAL on SUBMISSION_NAME, USER_RETURN_SUBCLASS, RETURN_NAME, and QUAL_PERIOD_CODE, so qualifying periods act as a validation parent for individual student records.

Because the object is documented as obsolete and not implemented, no active APIs or concurrent programs are listed. Readers migrating legacy data should treat IGS_HE_SUBMSN_RETURN and IGS_HE_STDNT_DLHE as the principal integration points and verify availability against their specific environment.