Results for “igs_ps_unit_ofr_pat”

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

Overview

The view IGS_PS_UNIT_OFR_PAT belongs to the Oracle E-Business Suite Student System (IGS) product family, a module that has since been classified as obsolete in the EBS 12.1.1 and 12.2.2 release documentation sets. The view is a reporting and integration artifact defined over the IGS_PS_UNIT_OFR_PAT_ALL table, exposing organisation-scoped rows of unit offering pattern configuration. Its principal role within the Student System is to present the scheduling and enrolment-control attributes attached to a specific offering pattern of a unit (course) version, including the operational switches that determine whether waitlisting is permitted and, when it is, how many students may occupy the waitlist at any one time. The column MAX_STUDENTS_PER_WAITLIST is the attribute most frequently sought by implementers and report developers, and this view is one of the supported paths through which that value is surfaced.

The ETRM metadata records this object as "Not implemented in this database," indicating that in the documented environment the view does not physically exist. References to it in custom code, reports, or interfaces must therefore be validated against the actual application schema before deployment.

Underlying Base Objects

The view text references a single base object, IGS_PS_UNIT_OFR_PAT_ALL, which is the multi-organisation ("_ALL") table holding unit offering pattern definitions. Although the ETRM metadata lists no formally documented referenced base objects, the SELECT statement clearly derives every column from that table, aliased as TAB, and uses TAB.ROWID to populate the synthetic ROW_ID column. The view applies a mandatory organisation-security predicate: rows are filtered so that ORG_ID matches the value decoded from the USERENV('CLIENT_INFO') session context, defaulting to -99 when no organisation is set. This mirrors the standard multi-org view pattern used throughout the EBS schema, and it means no row is visible unless the operating unit context is correctly initialised by the application or by the report's runtime environment.

Key Columns

• ROW_ID — pseudo-column derived from the base table ROWID, used as a unique row identifier for the view.
• UNIT_CD, VERSION_NUMBER — identify the unit and the version of the unit to which the offering pattern applies.
• CAL_TYPE, CI_SEQUENCE_NUMBER, CI_START_DT, CI_END_DT — calendar type, calendar instance sequence, and the start and end dates of the calendar instance for the pattern.
• WAITLIST_ALLOWED — indicator of whether waitlisting is enabled for the offering pattern.
• MAX_STUDENTS_PER_WAITLIST — the maximum number of students permitted on the waitlist for the pattern.
• ORG_ID — the operating unit that owns the row, and the column driving the multi-org security filter.
• DELETE_FLAG, ABORT_FLAG — status markers indicating deletion or abort state of the pattern record.
• Audit and concurrent-program columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE — support auditing and traceability.

Common Use Cases and Queries

The primary practical scenario is exposing waitlist configuration to users or downstream systems. A typical query enumerating active waitlist-enabled patterns is:

SELECT unit_cd, version_number, cal_type,
       ci_sequence_number, waitlist_allowed,
       max_students_per_waitlist
FROM   igs_ps_unit_ofr_pat
WHERE  waitlist_allowed = 'Y'
AND    NVL(delete_flag,'N') = 'N';

Because the view enforces organisation scoping, callers must initialise the client info context — as the EBS application does at sign-on — or the query returns no rows. The view also underpins validation logic that prevents over-subscription of waitlists and feeds enrollment reporting extracts. Given the obsolete status of the IGS product and the note that the view is not implemented in the documented database, developers should confirm existence in their target instance and consider querying IGS_PS_UNIT_OFR_PAT_ALL directly with an explicit ORG_ID predicate where the view is unavailable.