Search Results reviewer_number

Overview

IGS_PE_CREDENTIALS_V is a read-only view owned by the APPS schema in the Oracle E-Business Suite Student System (IGS) product family. It exposes credential details recorded against a person, such as academic or professional credentials submitted for review, together with the evaluating reviewer's identifying information. The view is documented as VALID in ETRM for release 12.2.2 and is present in both 12.1.1 and 12.2.2 environments as part of the standard IGS schema deployment.

Its primary role is to denormalize the credential record so that reporting, inquiry forms, and integration extracts can retrieve descriptive attributes—credential type description, rating meaning, and reviewer identity—without writing explicit joins to lookup, type, and person tables. This makes the view a convenient source for concurrent programs, Oracle Reports, and inbound/outbound interfaces that need credential information in a single query.

Underlying Base Objects

The view text is defined over three underlying objects:

• IGS_PE_CREDENTIALS (aliased C) — the driving table holding individual credential rows for a person, including credential type, date received, rating code, and reviewer assignment.
• IGS_AD_CRED_TYPES (aliased CT) — the credential type definition table, joined on CREDENTIAL_TYPE_ID, providing CREDENTIAL_TYPE, SYSTEM_TYPE, and CT_DESCRIPTION.
• IGS_LOOKUP_VALUES (aliased CC) — an outer-joined source of the rating description, restricted to LOOKUP_TYPE = 'PE_CRE_RATING', so RATING_CODE is resolved to a MEANING and RATING_DESCRIPTION.
• IGS_PE_PERSON_BASE_V (aliased P) — an outer-joined person view supplying PERSON_NUMBER and FULL_NAME for the reviewer, exposed as REVIEWER_NUMBER and REVIEWER_NAME.

The join between IGS_PE_CREDENTIALS and IGS_PE_PERSON_BASE_V is an outer join on REVIEWER_ID = PERSON_ID, meaning credentials without an assigned reviewer still return a row, with null reviewer attributes. The rating lookup join is likewise outer-joined, so an unmapped or absent rating code does not suppress the credential row.

Key Columns

• CREDENTIAL_ID / ROW_ID — the unique credential identifier and the ROWID of the base row, used for row-level reference.
• PERSON_ID — the person to whom the credential belongs.
• CREDENTIAL_TYPE_ID, CREDENTIAL_TYPE, SYSTEM_TYPE, CT_DESCRIPTION — the credential category and its descriptive attributes.
• DATE_RECEIVED — the date the credential was received.
• RATING_CODE, RATING_DESCRIPTION — the assessment rating and its decoded meaning from the PE_CRE_RATING lookup.
• REVIEWER_ID, REVIEWER_NUMBER, REVIEWER_NAME — the reviewer's internal identifier, person number, and full name. REVIEWER_NUMBER is the column returned when a user searches for "reviewer_number".
• REVIEWER_NOTES — free-text comments recorded by the reviewer.
• RECOMMENDER_NAME, RECOMMENDER_TITLE, RECOMMENDER_ORGANIZATION — details of the party recommending the credential.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit (WHO) columns.

Common Use Cases and Queries

Typical uses include credential review reporting, reviewer workload analysis, and person-level credential extracts for downstream systems. Because REVIEWER_NUMBER is a frequently searched attribute, queries commonly filter or group on it.

SELECT credential_id,
       person_id,
       credential_type,
       date_received,
       rating_description,
       reviewer_number,
       reviewer_name
FROM   apps.igs_pe_credentials_v
WHERE  reviewer_number = :p_reviewer_number
ORDER  BY date_received DESC;

Grouping by reviewer supports workload analysis:

SELECT reviewer_number, reviewer_name, COUNT(*) credential_count
FROM   apps.igs_pe_credentials_v
WHERE  reviewer_id IS NOT NULL
GROUP  BY reviewer_number, reviewer_name
ORDER  BY credential_count DESC;

To list credentials lacking a reviewer, filter on the outer-joined columns:

SELECT credential_id, person_id, credential_type, date_received
FROM   apps.igs_pe_credentials_v
WHERE  reviewer_id IS NULL;

Access should be granted through the standard IGS responsibility and menu functions rather than direct grants, and because the view joins an outer-joined person view, queries should consider the possibility of null reviewer attributes when credentials have not yet been assigned for review.