Results for “year_left”

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

Overview

The IGS_UC_ATTEND_HIST table belongs to the IGS (Student System) product family within Oracle E-Business Suite, and its metadata explicitly marks the object as obsolete. It is part of the legacy Oracle Students System / UCAS admissions integration schema, which was designed to capture academic history information supplied by applicants during the admissions cycle. According to the documented description, the table was intended to hold details of the last institution attended by an applicant, supporting the "Academic History Streamlining" initiative referenced in case and seed document UC_2893542_UCFD210.

From a Data Vault modeling perspective, the metadata classifies this object heuristically as a standalone structure. In practical terms this suggests the table behaves as a satellite-like record of applicant attributes rather than a true hub or link, since the foreign-key mining did not identify it as participating in a network of dependent relationships. The documented physical schema under ETRM 12.1.1 shows an owner of IGS with 11 columns. Critically, the implementation note states that the object is "Not implemented in this database," meaning that while the definition exists in the ETRM repository, no runtime physical table is expected in a standard 12.1.1 or 12.2.2 environment.

Key Information Stored

The column set is compact and centers on applicant identification and prior education dates:

• ATTEND_HIST_ID — the surrogate primary key defined by IGS_UC_ATTEND_HIST_PK and also exposed through the unique index IGS_UC_ATTEND_HIST_U1.
• PERSON_ID — the applicant identifier, forming the business-key candidate under the unique constraint IGS_UC_ATTEND_HIST_UK. This links the attendance record to the person party.
• INST_CODE — the code of the institution previously attended.
• YEAR_COMM — the year the applicant commenced study at that institution.
• YEAR_LEFT — the year the applicant left the institution.
• YEAR_COMP — the year of completion or expected completion.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN support the standard Oracle who-column auditing convention and are the remaining documented columns.

The separation between the surrogate key and the PERSON_ID business key matters because the unique constraint permits a single attendance-history record per person under this design, while the surrogate allows stable internal referencing.

Common Use Cases and Queries

Because the table is obsolete and not implemented, direct SQL against IGS.IGS_UC_ATTEND_HIST will typically fail in a live 12.1.1 or 12.2.2 database. Historical queries therefore usually target former installations, migration extracts, or ETRM metadata itself. A representative pattern, had it been implemented, would join the attendance record to the person hub:

• SELECT a.person_id, a.inst_code, a.year_comm, a.year_left, a.year_comp FROM igs.igs_uc_attend_hist a WHERE a.person_id = :p_person_id;
• Reporting on prior institution trends by joining INST_CODE to institution reference data.
• Gap analysis comparing YEAR_COMM and YEAR_LEFT to detect study gaps.
• Migration validation queries confirming one row per PERSON_ID, consistent with the unique constraint.

Related Objects

The relationship data identifies this object as standalone, so dependencies are inferred from key columns rather than documented foreign keys:

• PERSON_ID references the person/party entity used across IGS and HCM (commonly HZ_PARTIES or the IGS person tables) — the primary business-key join.
• IGS_UC_ATTEND_HIST_PK and IGS_UC_ATTEND_HIST_UK — the constraints that enforce uniqueness on ATTEND_HIST_ID and PERSON_ID respectively.
• Institution reference tables keyed by INST_CODE provide descriptive attributes for the attended institution.
• Other IGS UC academic-history objects from the same streamlining document, which may hold qualifications or grades supplementary to attendance dates.

Given the obsolete status, any integration or extension should validate current object availability before relying on this table in a 12.1.1 or 12.2.2 deployment.