Results for “igs_ad_rvgr_evaltr_v”

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

Overview

The IGS_AD_RVGR_EVALTR_V view is an Oracle E-Business Suite database object owned by the APPS schema and classified under the IGS (Student System) product family. It resides within the Oracle Student System admissions and recruitment data model and serves as a consolidated, read-only presentation layer over the evaluator records associated with Application Review Profiles. Its stated purpose is to expose "all Evaluator corresponding to Application Review Profile related information," meaning that it presents the individuals assigned to evaluate student applications, together with their personal identifiers and sequencing attributes.

Because the view is maintained at the APPS layer and joins the evaluator transaction table against the Trading Community Architecture (TCA) party and person profile tables, it shields report writers and integration developers from having to reconstruct the multi-table join manually. It is therefore used primarily in reporting, inquiry screens, concurrent program outputs, and downstream integrations where the identity and ordering of application reviewers must be resolved to named parties.

Underlying Base Objects

The view is defined over three objects:

• IGS_AD_RVGR_EVALTR — the base transactional table storing evaluator assignments. Each row represents an evaluator associated with an Application Review Profile reviewer record. This is the driving table of the view and supplies the ROWID, primary key, sequence, approver flag, and audit columns.
• HZ_PERSON_PROFILES — the TCA person profile table supplying PERSON_NAME and effective-dating attributes. The join is on EV.PERSON_ID = PP.PARTY_ID.
• HZ_PARTIES — the TCA party registry supplying PARTY_NUMBER. The join is P.PARTY_ID = PP.PARTY_ID.

No additional documented base objects are referenced. The join also enforces an effective-date predicate, requiring SYSDATE to fall between the profile's effective start date and the NVL of its effective end date and SYSDATE, so only currently effective person profiles are returned. This restricts the view to evaluators whose TCA person profile is active at query time; historical or future-dated profiles are excluded.

Key Columns

• REVGR_EVALUATOR_ID — primary identifier of the evaluator assignment record.
• APPL_REVPROF_REVGR_ID — foreign key linking the evaluator to the parent Application Review Profile reviewer configuration.
• PERSON_ID — the evaluator's party identifier, aligning to HZ_PARTIES.PARTY_ID.
• PERSON_NUMBER — the TCA party number, a stable human-facing identifier for the person.
• FULL_NAME (mapped from PP.PERSON_NAME) — the evaluator's displayed name.
• EVALUATION_SEQUENCE — the order in which evaluators are expected to act or be presented.
• PROGRAM_APPROVER_IND — a flag indicating whether the evaluator holds program-approver authority for the associated review profile. This is the column most commonly filtered on when identifying which reviewer may grant final program approval.
• Standard audit columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, plus ROWID.

Common Use Cases and Queries

Typical usage includes listing all evaluators for a given review profile, isolating program approvers, and producing name-resolved reviewer rosters for admissions reporting.

All evaluators for a review profile:

SELECT revgr_evaluator_id, person_number, full_name,
       evaluation_sequence, program_approver_ind
FROM   apps.igs_ad_rvgr_evaltr_v
WHERE  appl_revprof_revgr_id = :p_revprof_revgr_id
ORDER  BY evaluation_sequence;

Program approvers only (the search term program_approver_ind):

SELECT person_number, full_name, evaluation_sequence
FROM   apps.igs_ad_rvgr_evaltr_v
WHERE  appl_revprof_revgr_id = :p_revprof_revgr_id
AND    program_approver_ind = 'Y';

Joined to application data for reporting, the view provides the evaluator identity and approval capability per review profile. Because it filters on effective person profiles using SYSDATE, queries intended for historical auditing should query the base table IGS_AD_RVGR_EVALTR directly rather than this view.