Results for “igs_ad_adv_placement”

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

Overview

The IGS_AD_ADV_PLACEMENT table resides in the IGS schema, which is the foundation of the Oracle Student System (formerly Oracle Advanced Education) module. It stores the placement test exemption records associated with an individual person in the student population. In practical terms, the table captures the fact that a specific learner has been granted a waiver of one or more placement assessments, and links that learner to a coded exemption classification defined centrally in the code classes reference table. The object therefore acts as the transaction-of-record for exemption decisions and supports downstream academic rules such as course registration eligibility, cohorting, and prerequisite bypass evaluation.

From a Data Vault modeling perspective, the metadata leads to a heuristic classification of link. The table carries two foreign keys pointing outward to independent business entities (the person and the exemption code), and its own surrogate primary key. This structure is characteristic of a relationship record that resolves the association between a party and a reference classification, rather than a descriptive hub or a historized satellite.

Key Information Stored

The documented physical schema contains eight columns. The most significant elements are as follows:

• TEST_EXEMPTION_ID — the surrogate primary key (IGS_AD_ADV_PLACEMENT_PK). It uniquely identifies each exemption row and is the column referenced by dependent child tables. It is also the sole documented candidate for the unique business key index, alongside PERSON_ID and EXEMPTION_ID in the U1 and U2 unique constraints.
• PERSON_ID — the foreign key to HZ_PARTIES, identifying the student or applicant who holds the exemption. This is the primary link back to the party registry and is a documented unique-key component.
• EXEMPTION_ID — the foreign key to IGS_AD_CODE_CLASSES, identifying which exemption category applies. This is the other unique-key component and the semantic driver of the record.
• CREATED_BY, CREATION_DATE — the standard Oracle EBS "who and when" audit columns capturing row creation.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS audit columns capturing the most recent modification and the login/session responsible for it.

Common Use Cases and Queries

Typical reporting scenarios include listing all exempt students for a term, auditing exemption grants by category, and feeding eligibility checks in registration processes. A frequent query joins the placement exemption to the party and to the code classification:

• Retrieve exemption records for a person:
  SELECT p.test_exemption_id, p.person_id, p.exemption_id, p.creation_date FROM igs.igs_ad_adv_placement p WHERE p.person_id = :person_id;
• Count exemptions by code to measure which categories are most used:
  SELECT c.description, COUNT(*) FROM igs.igs_ad_adv_placement p, igs.igs_ad_code_classes c WHERE p.exemption_id = c.code_class_id GROUP BY c.description;
• Join to HZ_PARTIES to resolve the person name for a report extract.
• Audit recently created exemptions using CREATION_DATE ranges and CREATED_BY.

Related Objects

The FK/PK metadata identifies the principal relationships:

• IGS_AD_CODE_CLASSES — referenced through IGS_AD_ADV_PLACEMENT.EXEMPTION_ID; supplies the coded description of the exemption type.
• HZ_PARTIES — referenced through IGS_AD_ADV_PLACEMENT.PERSON_ID; supplies the identity of the exempted person.
• IGS_AD_ADV_PLACEMENT_PK / U1 / U2 — the unique constraints and indexes on TEST_EXEMPTION_ID and on PERSON_ID + EXEMPTION_ID that enforce uniqueness and drive lookup performance.

The table is typically consumed by Oracle Student System registration, admissions, and academic advising APIs and concurrent programs that evaluate placement rules; any child table that stores exemption details will carry TEST_EXEMPTION_ID as its foreign key back to this parent.