Search Results igsfv_person_credentials




Overview
Explore in AI Chat

Overview

The view IGSFV_PERSON_CREDENTIALS is an Oracle E-Business Suite (EBS) reporting and integration object owned by the APPS schema and associated with the IGS — Student System product family. In EBS 12.1.1 and 12.2.2 it is documented in the ETRM as a VALID view whose stated purpose is to present "information about the person's credentials." The F in the naming convention typically denotes a foreign-key–joined, denormalized "flat" view intended for external consumption — that is, for OBIEE/BI Publisher reports, extracts, and interface programs — rather than for transactional DML. The view is defined WITH READ ONLY, reinforcing its role as a query-only presentation layer. Note that the single-character prefix IGSFV and surrounding objects (IGS_PE_CREDENTIALS, HZ_PARTIES) make this a Student System construct; it should not be confused with similarly named Oracle iLearning/OLM credential objects found in other schema prefixes.

Underlying Base Objects

The view is defined over four base objects, joined as follows:

  • IGS_PE_CREDENTIALS (PEC) — the driving table, holding the person's credential records such as dates, reviewer notes, and recommender details.
  • HZ_PARTIES (HZP1) — the person (student/applicant) identified by PEC.PERSON_ID = HZP1.PARTY_ID. Although referred to as a Person, in the Trading Community Architecture (TCA) model the underlying record is a party.
  • HZ_PARTIES (HZP2) — the reviewer, joined with an outer join (HZP2.PARTY_ID(+)) on PEC.REVIEWER_ID, so credentials without an assigned reviewer still appear.
  • IGS_AD_CRED_TYPES (ADC) — the credential type, joined on PEC.CREDENTIAL_TYPE_ID = ADC.CREDENTIAL_TYPE_ID, supplying the type code and description.

Because two aliases of HZ_PARTIES are used, the view effectively resolves two distinct party roles (subject and reviewer) within a single row. The ETRM metadata lists no separately documented base objects for 12.2.2, but the embedded view text above provides the authoritative join definition.

Key Columns

Common Use Cases and Queries

The view supports credential tracking and reporting — for example, listing all credentials held by a person, identifying credentials still awaiting reviewer assignment, or extracting recommender information for accreditation and admissions reporting. A representative query retrieves a person's credential history:

SELECT person_number,
       credential_type_desc,
       date_received,
       reviewer_number,
       recommender_name
FROM   apps.igsfv_person_credentials
WHERE  person_number = :p_person_number
ORDER  BY date_received DESC;

To surface credentials lacking a reviewer, filter on the outer-joined column:

SELECT credential_id, person_number, credential_type_desc
FROM   apps.igsfv_person_credentials
WHERE  reviewer_id IS NULL;

Because the view is read-only and denormalized across TCA and Student System tables, it is well suited to concurrent program extracts and BI Publisher data templates. Report developers should apply the appropriate secure predicate on the person party where row-level security is required, and treat it as a query-only interface.