Search Results transcript_source_id




Overview

IGSBV_PERSON_ACAD_TRANSCRIPTS is a read-only view owned by the APPS schema in the Oracle E-Business Suite Student System (IGS) product family. It exposes person-level academic transcript details, providing a denormalized reporting surface for transcript records held in the transactional model. The view is documented as VALID in ETRM 12.2.2 and is present in both 12.1.1 and 12.2.2 releases.

The "BV" prefix denotes a business view intended primarily for inquiry, reporting, and integration rather than for data maintenance. Because the underlying SELECT statement carries the WITH READ ONLY clause, no DML is permitted against the view. Its principal architectural role is to flatten and label lookup-driven values (transcript type, transcript status, term type) into their descriptive meanings via inline lexical parameters, avoiding repeated joins to IGS_LOOKUP_VALUES in downstream reports.

Underlying Base Objects

The documented view text identifies a single base object: IGS_AD_TRANSCRIPT. All columns exposed by the view are drawn from that table; no joins to external tables and no union operations appear in the definition. However, the first three projected columns are not physical columns of the base table. They are Oracle Application Object Library lexical parameters of the form:

  • '_LA:TRANSCRIPT_TYPE:IGS_LOOKUP_VALUES:TRANSCRIPT_TYPE:MEANING' → exposed as "_LA:TRANSCRIPT_TYPE"
  • '_LA:TRANSCRIPT_STATUS:IGS_LOOKUP_VALUES:TRANSCRIPT_STATUS:MEANING' → exposed as "_LA:TRANSCRIPT_STATUS"
  • '_LA:TERM_TYPE:IGS_LOOKUP_VALUES:TERM_TYPE:MEANING' → exposed as "_LA:TERM_TYPE"

These parameters are resolved at runtime by the Oracle EBS localization/flexfield mechanism, substituting the MEANING column from IGS_LOOKUP_VALUES for the corresponding lookup type. The view therefore has a logical dependency on IGS_LOOKUP_VALUES even though the ETRM "referenced base objects" list documents none. Administrators should treat IGS_LOOKUP_VALUES and IGS_AD_TRANSCRIPT as the effective dependency set when assessing invalidation.

Key Columns

Common Use Cases and Queries

Typical usage covers admission evaluation, transcript verification, and statistical cohort reporting. Because the lookup columns resolve dynamically, queries should not rely on the quoted identifiers in application code; selecting them is supported, but referencing them by name is fragile.

Retrieving all approximate-rank transcripts for a person:

SELECT transcript_id,
       rank_in_class,
       class_size,
       approximate_rank_indicator,
       weighted_rank_indicator,
       date_of_issue
FROM   apps.igsbv_person_acad_transcripts
WHERE  approximate_rank_indicator = 'Y'
AND    education_id = :p_education_id;

Producing a percentile distribution report:

SELECT decile_rank,
       quartile_rank,
       percentile_rank,
       COUNT(*) records
FROM   apps.igsbv_person_acad_transcripts
GROUP  BY decile_rank, quartile_rank, percentile_rank
ORDER  BY percentile_rank;

Listing transcripts with GPA conversions and overrides:

SELECT education_id,
       entered_gpa,
       converted_gpa,
       core_curriculum_value,
       override_indicator,
       override_date
FROM   apps.igsbv_person_acad_transcripts
WHERE  override_indicator = 'Y';

Integration consumers should note the read-only nature of the view and the dependency on lexical lookup substitution; when extracting to a data warehouse, materialize the resolved locale text rather than the lexical token to avoid ambiguity across language installations.