Results for “igs_ps_type_hist”

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

Overview

The view IGS_PS_TYPE_HIST belongs to the IGS (Student System) product family in Oracle E-Business Suite, a module that Oracle has classified as obsolete in releases 12.1.1 and 12.2.2. In the ETRM repository the object is documented as "Not implemented in this database," which indicates that the view is defined in the IGS data model but is not created in every environment. Where it exists, IGS_PS_TYPE_HIST exposes the historical, or date-tracked, records of programme (course) types maintained by the Student System. Its role is to provide reporting and integration access to the full version history of a course type, allowing consumers to see not only the current definition but also prior states captured through the HIST_START_DT and HIST_END_DT date-tracked columns. The view enforces the standard Oracle EBS multi-tenant (operating unit) security predicate against ORG_ID, so results are filtered to the organization context supplied through the USERENV('CLIENT_INFO') session value.

Underlying Base Objects

The documented view text shows a single source object: the table IGS_PS_TYPE_HIST_ALL, aliased as TAB, wrapped in a SELECT that projects the ROWID as the ROW_ID pseudo-column. The ETRM metadata lists no additional referenced base objects. Because the view reads from the _ALL table, it inherits the operating-unit partition inherent to that table; the WHERE clause compares the table's ORG_ID to the numeric value extracted from the client information environment, defaulting the comparison to -99 when no organization is set. This is the conventional pattern used by the IGS and other EBS "secure" views to restrict rows to the caller's current organization. The reliance on IGS_PS_TYPE_HIST_ALL also means IGS_PS_TYPE_HIST is a thin projection rather than a join or aggregation: every column reported by the view maps one-to-one to a column of the base table, and no transformations are applied beyond the operating-unit filter.

Key Columns

• ROW_ID — the ROWID of the underlying IGS_PS_TYPE_HIST_ALL row, exposed for row addressing and updates.
• COURSE_TYPE — the identifier of the course or programme type, the primary business key of the record.
• HIST_START_DT / HIST_END_DT — the effective date range of the historical version; the currently active version is indicated by a null or future end date.
• HIST_WHO — the user or process responsible for the historical change.
• DESCRIPTION, GOVT_COURSE_TYPE, AWARD_COURSE_IND, COURSE_TYPE_GROUP_CD, TAC_COURSE_LEVEL, RESEARCH_TYPE_IND — descriptive and classification attributes of the course type as of the version.
• CLOSED_IND, PRIMARY_AUTO_SELECT, FIN_AID_PROGRAM_TYPE — status and functional flags controlling whether the type is closed, auto-selected as primary, or eligible for financial aid programmes.
• ORG_ID — the operating unit that owns the row, the basis of the security predicate.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns recording who created and last modified the version and when.

Common Use Cases and Queries

The principal use of IGS_PS_TYPE_HIST is historical reporting on course type definitions — for example, reconstructing what a course type's description, award indicator, or government classification looked like at a given point in time. Because the view applies the operating-unit filter, queries issued within a specific organization context return only that organization's rows. A typical query retrieving active versions is:

SELECT course_type, description, govt_course_type,
       hist_start_dt, hist_end_dt
  FROM igs_ps_type_hist
 WHERE hist_end_dt IS NULL
    OR hist_end_dt > SYSDATE;

A second common pattern audits change history for a single course type:

SELECT course_type, hist_start_dt, hist_end_dt, hist_who
  FROM igs_ps_type_hist
 WHERE course_type = 'PG'
 ORDER BY hist_start_dt;

Given that IGS is classified as obsolete and the view may not be implemented, implementations should confirm its existence in the target database before relying on it, and should prefer any supported successor objects where the Student System has been replaced. Where the view is present, its direct mapping to IGS_PS_TYPE_HIST_ALL makes it a reliable, read-only reporting surface over date-tracked course type data.