Results for “arp_gr_code_meaning”

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

Overview

IGS_AD_APR_RVGR_V is a reporting view within the Oracle E-Business Suite IGS (Student System) module. In Oracle EBS 12.1.1 and 12.2.2, this object resides in the obsolete Student System product line, which was superseded by Oracle Student Financial Planning and related higher-education solutions. The view consolidates Application Review Profile and Application Review Group Code information into a single queryable structure. It is primarily used for reporting and integration purposes, allowing downstream processes, concurrent programs, or custom reports to retrieve review group assignments associated with admissions application review profiles without directly joining the underlying transactional tables.

The view is documented in ETRM 12.2.2 metadata with the description "View where the Application Review Group Code related information will be recorded." This confirms its role as a denormalized read-only interface over review profile and review group configuration data.

Underlying Base Objects

According to the documented view text, IGS_AD_APR_RVGR_V is defined over two source objects:

• IGS_AD_APL_REV_PRF_V — the Application Review Profile view, aliased as RS in the SQL definition.
• IGS_AD_APL_RPRF_RGR — the Application Review Profile Review Group table, aliased as RG.

The two objects are joined on APPL_REV_PROFILE_ID (RS.APPL_REV_PROFILE_ID = RG.APPL_REV_PROFILE_ID). This relationship links each review profile to its associated review group code records. The ETRM metadata notes that no referenced base objects are documented for the view itself, reflecting the fact that it is not implemented in the current database and that its dependencies are recorded only through the view text. Because IGS_AD_APR_RVGR_V derives from another view (IGS_AD_APL_REV_PRF_V) rather than from base tables directly, its lineage traces further back into the admissions application review configuration schema.

Key Columns

The view exposes nineteen columns spanning profile attributes, review group codes, and standard audit fields:

• ROW_ID — unique row identifier from the review profile source.
• APPL_REV_PROFILE_ID — foreign key linking the profile to its review group records; the join key of the view.
• REVIEW_PROFILE_NAME — descriptive name of the application review profile.
• MIN_EVALUATOR / MAX_EVALUATOR — minimum and maximum number of evaluators permitted for the profile.
• PROG_APPROVAL_REQUIRED — indicates whether program-level approval is required.
• SEQUENTIAL_CONCURRENT_IND — flag indicating whether evaluations occur sequentially or concurrently.
• APPL_REV_PROFILE_GR_CD and ARP_GR_CODE_MEANING — the review profile group code and its decoded meaning.
• SITE_USE_CODE and SITE_USE_CODE_MEANING — site use context and its decoded meaning.
• REVPROF_REVGR_CD — the review group code, central to the user's search term.
• REVPROF_REVGR_NAME — the descriptive name of the review group; this is the column corresponding to the search string "revprof_revgr_name".
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Oracle audit columns.

Common Use Cases and Queries

Typical reporting scenarios include listing all review groups attached to a given review profile, resolving group code meanings for user-facing reports, and auditing profile configuration. A representative query follows:

SELECT APPLICATION_REV_PROFILE_ID, REVIEW_PROFILE_NAME, REVPROF_REVGR_CD, REVPROF_REVGR_NAME, MIN_EVALUATOR, MAX_EVALUATOR FROM IGS_AD_APR_RVGR_V WHERE APPL_REV_PROFILE_ID = :profile_id;

To locate a specific review group by name, the search term supplied by the user maps directly to the REVPROF_REVGR_NAME column:

SELECT APPL_REV_PROFILE_ID, REVIEW_PROFILE_NAME, REVPROF_REVGR_CD, REVPROF_REVGR_NAME FROM IGS_AD_APR_RVGR_V WHERE REVPROF_REVGR_NAME LIKE '%' || :group_name || '%';

Because the IGS Student System module is obsolete and the view is not implemented in the documented database, deployments should verify object existence before relying on it and consider migration to supported admissions or student planning alternatives.