Results for “score_band_upper”

26 results




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

Overview

IGS_AD_TST_RSLT_DTLS is a table in the IGS (Student System) product family of Oracle E-Business Suite. Per the ETRM metadata, its documented purpose is to hold test result details. The product designation carries an explicit "(Obsolete)" qualifier in the 12.1.1 and 12.2.2 documentation, and the ETRM record further records the object as "Not implemented in this database." This combination indicates that the object is retained for documentation, upgrade, and historical reference purposes but is not instantiated as a live, supported entity in a standard R12 environment. It should therefore be treated as a legacy or predecessor structure rather than a functional component of a current Oracle Student System implementation.

From a modeling standpoint, the heuristic Data Vault classification derived from the foreign key structure is satellite-leaning. This is consistent with the table's role: it carries descriptive attributes (scores, percentiles, bands, and irregularity references) that contextualise a parent assessment result, rather than defining a core business entity or resolving a many-to-many relationship between hubs.

Key Information Stored

The table is documented with 41 columns under schema owner IGS. The surrogate primary key is TST_RSLT_DTLS_ID, enforced by the unique index IGS_AD_TST_RSLT_DTLS_PK. No separate business-key candidate is documented beyond that single unique index; the key is purely system-generated.

Common Use Cases and Queries

Because the object is documented as not implemented, in R12.1.1 and R12.2.2 the primary practical uses are upgrade impact analysis, historical data migration validation, and reconciliation of legacy extracts. Queries typically reconstruct a complete result picture by joining the detail to its parent result and segment tables:

  • Reporting a candidate's segment-level outcomes: select the score, percentile variants, and score band from IGS_AD_TST_RSLT_DTLS joined to IGS_AD_TEST_RESULTS on TEST_RESULTS_ID to retrieve the candidate and test context, and to IGS_AD_TEST_SEGMENTS on TEST_SEGMENT_ID to retrieve segment descriptions.
  • Exception reporting: join IRREGULARITY_CODE_ID to IGS_AD_CODE_CLASSES to translate irregularity identifiers into meaningful, code-class descriptions for audit or appeal reporting.
  • Cohort analytics: aggregate PERCENTILE_YEAR_RANK and NATIONAL_PERCENTILE or STATE_PERCENTILE by segment to compare a candidate against national and state distributions.
  • Flexfield reporting: filter on ATTRIBUTE_CATEGORY and the ATTRIBUTE1–20 columns to surface institution-specific extensions captured on the legacy detail rows.
  • Lineage and audit: use REQUEST_ID and the PROGRAM_* columns to trace which concurrent program or process populated or updated a given detail row during legacy loads.

Related Objects

Relationship metadata identifies both inbound references (foreign keys defined on this table) and outbound references (tables that reference this table by its primary key).

  • IGS_AD_TEST_RESULTS — parent entity referenced by TEST_RESULTS_ID; supplies the overarching test result to which each detail belongs.
  • IGS_AD_TEST_SEGMENTS — referenced by TEST_SEGMENT_ID; identifies the segment or component being scored.
  • IGS_AD_CODE_CLASSES — referenced by IRREGULARITY_CODE_ID; provides the coded classification for irregularities.
  • IGS_AV_STND_UNIT_ALL — view/object referencing IGS_AD_TST_RSLT_DTLS via TST_RSLT_DTLS_ID.
  • IGS_AV_STND_UNIT_LVL_ALL — view/object referencing IGS_AD_TST_RSLT_DTLS via TST_RSLT_DTLS_ID.

These inbound references indicate that the standard unit views depend on test result detail identifiers, reinforcing the value of treating this table as a satellite of the result and segment structures when modelling legacy data for migration or archival reporting.