Results for “igs_ad_ps_appl_hist”

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

Overview

IGS_AD_PS_APPL_HIST is an Oracle EBS 12.1.1 / 12.2.2 view owned by the APPS schema within the IGS (Student System) product family. It exposes the history of prospective-student admission applications, specifically presenting records from the admissions application history entity together with the operative ADMISSION_CD attribute that identifies the admission category assigned to an applicant. In operational terms, the base entity stores successive versions of an application's key admission attributes; this view surfaces those versions with effective dating so that prior and current values can be reported side by side.

The view is a multi-organization (MOAC) secured reporting object. Its defining query selects from IGS_AD_PS_APPL_HIST_ALL and filters rows so that ORG_ID matches the organization context carried in the session's CLIENT_INFO, with a NVL fallback of -99. This makes it suitable for institution-scoped reports, extracts, and integrations without requiring the caller to write explicit organization predicates. Because it is a view rather than a table, it carries no independent storage and reflects the current state of the underlying _ALL table at query time. It is most commonly used by admissions functional users, student-records reporting, and interface programs that need an auditable trail of admission decisions and application amendments.

Underlying Base Objects

The view is defined exclusively over the table IGS_AD_PS_APPL_HIST_ALL. The ETRM metadata documents no other referenced base objects. As the _ALL suffix indicates, the base table is organization-partitioned by ORG_ID, and the view applies the standard Oracle multi-org security predicate against it.

The view does not denormalize or join to any lookup or reference table; all decoding of code values (for example, admission category, basis for admission type, or course code) must be performed by the reporting query against the appropriate IGS/HR lookup views. Consequently the view can be treated as a thin, security-filtered projection of the base history table. Change history is preserved by the HIST_START_DT, HIST_END_DT, and HIST_WHO columns, which in the underlying entity typically correspond to date-tracked (date-effective) attributes; the view exposes them directly rather than at a single point in time.

Key Columns

• ROW_ID — the ROWID of the underlying _ALL row; useful for de-duplication and for driving updates or row-level joins.
• ORG_ID — the operating unit / organization identifier applied by the MOAC predicate.
• PERSON_ID — the applicant's party/person identifier, the primary link to person and applicant records.
• ADMISSION_APPL_NUMBER — the admission application number, the business key of the application.
• ADMISSION_CD — the code indicating the type or outcome of the admission (for example, the admission category or route applied to the application). This is the column most commonly searched by users.
• BASIS_FOR_ADMISSION_TYPE — the basis or criterion on which the admission decision was made.
• NOMINATED_COURSE_CD and TRANSFER_COURSE_CD — the course nominated by the applicant and any transfer course involved.
• HIST_START_DT / HIST_END_DT / HIST_WHO — effective start and end dates and the actor for the history record, supporting point-in-time and audit reporting.
• COURSE_RANK_SET / COURSE_RANK_SCHEDULE — identifiers for the course ranking set and schedule used in selection.
• REQ_FOR_RECONSIDERATION_IND / REQ_FOR_ADV_STANDING_IND — flags indicating a request for reconsideration and a request for advanced standing.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, CREATED_BY, CREATION_DATE, LAST_UPDATE_LOGIN — standard Oracle audit columns.

Common Use Cases and Queries

Typical usage includes audit reporting of admission decisions, reconciliation of current versus historical ADMISSION_CD values, and integration extracts feeding data warehouses or downstream student systems. Because the view is organization-secured, it should be queried from within an application session or with MOAC context set. A basic lookup by application number might be written as:

• SELECT person_id, admission_appl_number, admission_cd, hist_start_dt, hist_end_dt FROM igs_ad_ps_appl_hist WHERE admission_appl_number = :p_appl_number ORDER BY hist_start_dt;
• SELECT admission_cd, COUNT(*) FROM igs_ad_ps_appl_hist WHERE hist_end_dt IS NULL GROUP BY admission_cd;
• SELECT a.person_id, a.admission_appl_number, a.admission_cd, a.hist_start_dt FROM igs_ad_ps_appl_hist a WHERE a.person_id = :p_person_id AND NVL(a.hist_end_dt, SYSDATE) >= SYSDATE;

For human-readable output, join ADMISSION_CD to the appropriate admissions lookup view, and correlate PERSON_ID to person and applicant views. Always constrain by PERSON_ID, ADMISSION_APPL_NUMBER, or effective dates to avoid full scans of the _ALL table, and be aware that the view returns history rows rather than a single current row unless filtered by HIST_END_DT IS NULL or the applicable date range.