Results for “igs_ad_ps_aplinstunt_unithst_v”

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

Overview

IGS_AD_PS_APLINSTUNT_UNITHST_V is a database view belonging to the IGS (Student System) product family in Oracle E-Business Suite. Within ETRM metadata it is catalogued as an obsolete component and is flagged as "Not implemented in this database" for the documented 12.2.2 environment. The view is designed to expose the historical (history-tracked) records associated with admission application instance units — that is, the units attached to a prospective student's admission application at the point of application and nomination to a course. Its name decomposes into "APL INST UNIT" (Application Instance Unit) with the "HST" suffix denoting a history table pattern, so its purpose is to surface date-effective, versioned rows rather than only the current state of an application unit record.

In Oracle EBS reporting and integration terms, such views act as a read-only abstraction layer over the transactional application tables. They allow concurrent programs, reports, and interface extracts to retrieve the full historical lineage of an application unit — including superseded rows — without embedding the complex NVL/DECODE fallback logic directly in each downstream query.

Underlying Base Objects

The ETRM record documents no referenced base objects, and the view text itself is the primary evidence of its structure. The FROM clause centres on an alias ACAIUH1, which corresponds to the history table for admission application instance units (the ACAIU history counterpart to the ACAIU base table, aliased ACAIU1). The naming convention follows the IGS pattern where a "_H" or "H" suffix marks the history-tracked sibling of a transactional table.

The view relies heavily on the package function IGS_AU_GEN_001.AUDP_GET_ACAIUH_COL, invoked repeatedly to recover column values from the history row. Each column is resolved through a nested NVL: the value present on the history row (ACAIUH1) is used first; failing that, the function retrieves the value from the history record via its composite key; and finally the value falls back to the base ACAIU1 row. This three-tier resolution ensures a value is returned even where the history row carries a null.

Key Columns

• PERSON_ID — the identifier of the applicant (prospective student) associated with the application instance unit.
• ADMISSION_APPL_NUMBER — the admission application number linking the unit to a specific application.
• NOMINATED_COURSE_CD — the course to which the applicant is nominated.
• ACAI_SEQUENCE_NUMBER — sequence number identifying the specific application instance unit line.
• UNIT_CD — the code of the unit (subject) recorded against the application.
• HIST_START_DT / HIST_END_DT — the effective date range of the historical row; HIST_END_DT is also used as a key argument to the lookup function.
• HIST_WHO — the user or process responsible for the historical change.
• UV_VERSION_NUMBER — the unit version, resolved via NVL and TO_NUMBER, with fallback to the base row.
• CAL_TYPE, CI_SEQUENCE_NUMBER, LOCATION_CD, UNIT_CLASS, UNIT_MODE — calendar type, calendar instance sequence, location, unit class, and unit mode, each resolved with SUBSTR handling for character columns.

Common Use Cases and Queries

The view supports historical auditing and reporting of application units — for example, showing how a unit's version, mode, or location changed across an admission cycle. Because it is documented as obsolete and unimplemented, queries should be validated against the target instance before use.

SELECT person_id,
       admission_appl_number,
       unit_cd,
       uv_version_number,
       unit_mode,
       hist_start_dt,
       hist_end_dt
FROM   igs_ad_ps_aplinstunt_unithst_v
WHERE  admission_appl_number = :appl_number
ORDER  BY hist_start_dt;

Typical scenarios include reconstructing the point-in-time state of an applicant's unit selections for a given HIST_END_DT, and feeding historical admission extracts where only the as-at value is required. Reports that must not depend on the newest row can constrain by HIST_END_DT to obtain the correct effective version.