Search Results exit_version_set

Overview

IGS_PE_ALTERNATV_EXT_V is a simple (non-join) Oracle EBS view owned by the APPS schema within the IGS – Student System product family, commonly known as Oracle Student System (OSS). It exposes alternate exit qualification data captured against a student's program enrolment, presenting the course, version, and exit-award attributes that describe an alternative exit route a learner may be permitted to take. Because the view is defined as a one-to-one projection over a single base table, it functions primarily as a reporting and integration access point rather than as a transformation or denormalisation layer. Institutions and integrators use it to retrieve alternate exit definitions without querying the underlying table directly, and external systems frequently consume it through EBS Integrated SOA Gateway or custom interfaces.

Underlying Base Objects

The view is defined exclusively over the base table IGS_PE_ALTERNATV_EXT. The view text is a straight column-for-column selection from that table, with no WHERE clause, joins, or aggregations. ETRM documentation records no other referenced base objects, confirming that all columns exposed by the view originate from that single table. Because no filter predicate is applied, the view returns every row present in the base table, subject only to the row-level security enforced by the caller's Oracle EBS responsibilities and any custom Row Level Security (RLS) policies applied to the underlying table.

Key Columns

• COURSE_CD – Identifies the course (program) against which the alternate exit is defined.
• VERSION_NUMBER – The version of the course record, enabling version-controlled tracking of the exit pathway.
• EXIT_COURSE_CD – The course code of the exit award that a student may transfer into.
• EXIT_VERSION_SET – The version set associated with the exit course, used to resolve the correct version of the exit programme.
• CREATED_BY, CREATION_DATE – Standard EBS WHO columns capturing the creating user and timestamp.
• LAST_UPDATED_BY, LAST_UPDATE_DATE – Standard WHO columns identifying the user who most recently modified the record and when.
• LAST_UPDATE_LOGIN – The login identifier associated with the last update; this is the column most relevant to the user's search term "last_updated_login". Note that the documented column list renders this attribute as LAST_UPDATED_LOGIN, while the view text exposes it as LAST_UPDATE_LOGIN. Both labels refer to the same underlying operational login sequence number, and the correct reference for SQL against this view is LAST_UPDATE_LOGIN.

Common Use Cases and Queries

The view is typically queried during audit and data-lineage activities where the update login sequence is required, and during integration extracts that push alternate exit definitions to downstream student record systems.

Simple retrieval of all alternate exits:

SELECT course_cd, version_number, exit_course_cd, exit_version_set
FROM   apps.igs_pe_alternatv_ext_v;

Audit query identifying records changed by a specific login (relevant to the "last_updated_login" search):

SELECT course_cd, version_number, exit_course_cd,
       last_updated_by, last_update_date, last_update_login
FROM   apps.igs_pe_alternatv_ext_v
WHERE  last_updated_login = :p_login_id;

Recently modified alternate exits:

SELECT course_cd, exit_course_cd, last_update_date
FROM   apps.igs_pe_alternatv_ext_v
WHERE  last_update_date >= SYSDATE - 30
ORDER  BY last_update_date DESC;

Because the view carries no filtering, callers requiring responsibility-scoped access should join to FND_LOGINS or equivalent user-context tables when translating LAST_UPDATE_LOGIN into a named user.