Search Results statistic_type




Overview
Explore in AI Chat

Overview

IGSFV_AD_ACT_STATS_ACCOMP is a read-only Oracle EBS view owned by the APPS schema and defined in the Oracle Student System (IGS) product family, part of the Student Information / Academic Records module set. It presents achievement-type admission test statistics ("accomplishment" records) associated with a person, and is the primary reporting and integration access point for this subset of statistics data. Because the view is created WITH READ ONLY, it is intended strictly for query, extraction, and concurrent-program reporting; it cannot be used for DML, and any data maintenance must be performed against the underlying base tables. Typical consumers are Discoverer/OBIEE reports, XML Publisher layouts, inbound/outbound interfaces, and custom APIs that need a stable name for what would otherwise be a multi-table join.

Underlying Base Objects

The view is a two-table join, filtered on STATISTIC_TYPE = 'ACCOMPLISHMENT':

  • IGS_AD_ACT_STATISTICS (aliased ACTST): the driving table, holding admission test statistics — reporting year, ACT identifier, test type, test date text, statistic category, and score. The STATISTIC_TYPE column on this table is the discriminator that limits the view to accomplishment records.
  • IGS_PE_ALT_PERS_ID (aliased PEA): the alternate person identifier table, providing the internal PERSON_ID. It is joined with an outer-join (+) on API_PERSON_ID, and further restricted to PERSON_ID_TYPE = 'ACTID'.

The join key is derived: DECODE(SUBSTR(ACTST.ACT_IDENTIFIER,1,1),'-',SUBSTR(ACTST.ACT_IDENTIFIER,2),ACTST.ACT_IDENTIFIER) = PEA.API_PERSON_ID (+). A leading hyphen on the ACT identifier is stripped before matching, so records are matched with or without that prefix. Because the person table is outer-joined, an accomplishment statistic is still returned even when no matching ACTID person record exists. Note that no base objects are enumerated in the ETRM metadata excerpt for this view, so the two tables above are identified from the view text itself.

Key Columns

Common Use Cases and Queries

A key reason users search for "statistic_type" against this view is that the literal value is hard-coded rather than exposed as a column: the filter STATISTIC_TYPE = 'ACCOMPLISHMENT' is baked into the view definition, so the view returns only accomplishment statistics. Other statistic types are retrieved from the base table IGS_AD_ACT_STATISTICS directly. Typical queries include:

  • Reporting a person's accomplishment scores for a reporting year: SELECT act_identifier, test_type, statistic_category_code, score FROM igsfv_ad_act_stats_accomp WHERE reporting_year = :year;
  • Resolving category meaning via the lookup table IGS_LOOKUP_VALUES on lookup type ACT_STATISTIC_CATEGORY.
  • Detecting unmatched identifiers (PERSON_IDENTIFIER IS NULL) caused by the outer join and the ACTID type restriction.

Because the view is read-only and driven by a single hard-coded statistic type, it should be treated as a stable reporting interface; any requirement to see other statistic types, or to write data, must be addressed against the underlying IGS_AD_ACT_STATISTICS and IGS_PE_ALT_PERS_ID tables.