Results for “acai_sequence_number”

50+ results




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

Overview

IGS_RE_CANDIDATURE is an Oracle E-Business Suite 12.1.1 / 12.2.2 view owned by the APPS schema and registered as VALID in the ETRM reference documentation. It belongs to the IGS product family, commonly identified as the Student System (formerly Oracle Student System, now part of the Oracle Higher Education / Student Administration footprint). The view presents research candidature records — the association between a person (candidate) and a research programme or course — and is used principally for multi-org security-filtered reporting and integration against research candidate data.

Its distinguishing characteristic is that it is a secured view: the defining query projects columns from the underlying table IGS_RE_CANDIDATURE_ALL and applies an ORG_ID predicate driven by USERENV('CLIENT_INFO'). Only rows whose ORG_ID matches the operating unit currently set in the session's client information are exposed. This makes the view the preferred access path for any consumer that must respect Organizational Unit (MOAC) security, rather than querying the _ALL table directly.

Underlying Base Objects

According to the documented view text, IGS_RE_CANDIDATURE is defined over a single base object, IGS_RE_CANDIDATURE_ALL. No other referenced base objects are documented in the ETRM metadata. The join is implicit — the view is a straight column projection (with ROWID aliased as ROW_ID) plus a WHERE clause:

  • SELECT TAB.ROWID ROW_ID, TAB.ORG_ID, ... FROM IGS_RE_CANDIDATURE_ALL TAB
  • The filter compares the session client info against the row's ORG_ID, defaulting to -99 when no client information is available: NVL(TAB.ORG_ID, NVL(TO_NUMBER(DECODE(SUBSTRB(USERENV('CLIENT_INFO'),1,1),' ',NULL,SUBSTRB(USERENV('CLIENT_INFO'),1,10))), -99)) = ...

Because there is no aggregation or join, the view is update-capable in principle, though it is generally consumed read-only for reporting. The _ALL suffix on the base table indicates that the underlying data is partitioned by operating unit, and the view exists solely to enforce that partitioning for the calling session.

Key Columns

Common Use Cases and Queries

Typical uses include research candidature listings for a given operating unit, admission-to-candidature reconciliation, and government activity reporting. A simple secured query is:

  • SELECT person_id, sequence_number, sca_course_cd, research_topic, min_submission_dt, max_submission_dt FROM apps.igs_re_candidature WHERE person_id = :p_person_id;
  • SELECT acai_admission_appl_number, acai_nominated_course_cd, sca_course_cd FROM apps.igs_re_candidature WHERE org_id = :p_org_id AND attendance_percentage IS NOT NULL;
  • SELECT COUNT(*) FROM apps.igs_re_candidature WHERE govt_type_of_activity_cd = :p_activity_cd AND max_submission_dt BETWEEN :p_from AND :p_to;

Because the view is MOAC-secured, callers should initialise client information (for example via FND_GLOBAL.APPS_INITIALIZE or MO_GLOBAL.SET_POLICY_CONTEXT) before querying; otherwise the predicate may resolve to the -99 default and return no rows. Where access to all operating units is genuinely required — for example a cross-org data warehouse extraction — the underlying IGS_RE_CANDIDATURE_ALL table should be used instead, subject to appropriate privileges.