Search Results igs_as_exm_suprvisor




Overview
Explore in AI Chat

Overview

The IGS_AS_EXM_SUPRVISOR view is a reporting and integration object within the Oracle EBS Student System (IGS) product family. It exposes exam supervisor assignment data maintained by the institution, allowing external reports, concurrent programs, and integration interfaces to retrieve supervisor records without directly accessing the underlying transactional table. The view is owned by the APPS schema and is documented as VALID in ETRM for releases 12.1.1 and 12.2.2. Its principal architectural role is to apply Multi-Org (Operating Unit) security filtering at the database layer so that consumers of the view only see records belonging to the operating unit associated with the current session.

In the EBS Student System, exam supervisors are the individuals assigned to oversee examinations. The view provides a denormalized and Org-secured projection of this data, making it suitable for use in Oracle Reports, BI Publisher data templates, OAF-based pages, and inbound/outbound integration programs that need identity, responsibility, and audit information for each supervisor assignment.

Underlying Base Objects

The view is defined over a single underlying object, IGS_AS_EXM_SUPRVISOR_ALL, which is the Multi-Org "ALL" table holding supervisor rows across all operating units. The view selects from this table with a WHERE clause that enforces Org isolation:

  • The filter compares the ORG_ID column of the base table against a numeric value derived from USERENV('CLIENT_INFO'), the session-level client info string populated by the Multi-Org initialization routine (FND_CLIENT_INFO).
  • The expression NVL(ORG_ID, NVL(..., -99)) ensures that rows with a null Org ID are still eligible when the session context is similarly unknown, defaulting to the sentinel value -99.
  • The DECODE(SUBSTRB(...,1,1), ' ', NULL, ...) pattern treats a blank first character of CLIENT_INFO as "no Org context," returning NULL rather than an invalid number.

Because only one base object is referenced, the view introduces no joins and inherits the column set of the "_ALL" table verbatim.

Key Columns

  • ROW_ID — The ROWID of the underlying base table row. Useful for direct row identification in updates through the view.
  • PERSON_ID — Foreign key to the person (supervisor) record in PER_PEOPLE_F / PER_ALL_PEOPLE_F; identifies the individual acting as exam supervisor.
  • EXAM_SUPERVISOR_TYPE — Classifies the supervisor role or category (for example, internal versus external, or primary versus assistant).
  • PREVIOUS_SESSIONS — Captures prior examination sessions in which the supervisor has participated, supporting experience or eligibility checks.
  • RESPONSIBLE_ORG_UNIT_CD — The organization unit code accountable for the supervisor assignment.
  • RESPONSIBLE_OU_START_DT — Effective start date associated with the responsible organization unit designation.
  • COMMENTS — Free-text remarks about the supervisor or assignment.
  • CREATED_BY / CREATION_DATE / LAST_UPDATED_BY / LAST_UPDATE_DATE / LAST_UPDATE_LOGIN — Standard EBS WHO columns for audit traceability.
  • ORG_ID — The operating unit that owns the row; drives the Multi-Org filter applied by the view.

Common Use Cases and Queries

Typical usages include reporting the supervisor roster for a given operating unit, validating supervisor eligibility before scheduling exams, and extracting supervisor data for downstream integration. Because the view enforces Org security, the querying session must have initialized its Org context (for example, by running a request with a selected operating unit), otherwise only rows with a null Org ID are returned.

Sample query listing supervisors for the current Org context:

  • SELECT person_id, exam_supervisor_type, responsible_org_unit_cd, previous_sessions FROM igs_as_exm_suprvisor WHERE exam_supervisor_type = 'INTERNAL';
  • SELECT person_id, COUNT(*) sessions FROM igs_as_exm_suprvisor GROUP BY person_id;
  • SELECT s.person_id, p.full_name FROM igs_as_exm_suprvisor s, per_all_people_f p WHERE s.person_id = p.person_id AND TRUNC(SYSDATE) BETWEEN p.effective_start_date AND p.effective_end_date;

Developers should treat the view as read-only reporting surface and access the base table only through approved APIs when performing DML.