Results for “s_result_type”

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

Overview

IGS_AD_ADM_UT_STA_GD_V is a reporting and inquiry view within the Oracle E-Business Suite Student System (IGS) module. It presents the grading schema code grades that are applicable to an administrative unit status, resolving the versioned relationship between an administrative unit status configuration and the grading schema grades that drive academic outcomes. The view is documented in ETRM as part of the obsolete IGS - Student System product family, and the ETRM record notes that it is not implemented in the reference database instance.

The view's central purpose is to answer the business question: "For a given administrative unit status, which grade within a grading schema applies, what does that grade mean, and what is its result type?" Because grading schemas are versioned, the view joins across version numbers so that only the grading schema grade matching the administration unit status record's version is returned. The description explicitly states that at any point in time only one grading schema code grade should be applicable to an administrative unit status, making this view a canonical source for a singular, effective grade mapping. The S_RESULT_TYPE column, which the user searched for, is exposed here through the IGS_AS_GRD_SCH_GRADE table and decoded into a human-readable MEANING via the IGS lookups view.

Underlying Base Objects

The view is defined over four referenced objects, though the ETRM metadata records no formally documented base objects for this view. The view text identifies them as follows:

• IGS_AD_ADM_UT_STA_GD (aliased AUSG) — the primary administrative unit status / grading schema grade assignment table, supplying ROW_ID, administrative unit status, grading schema code, version number, grade, and audit columns.
• IGS_AS_GRD_SCH_GRADE (aliased GSG) — the grading schema grade definition table, supplying the full grade name and the S_RESULT_TYPE value.
• IGS_AS_GRD_SCHEMA (aliased GS) — the grading schema header, supplying the effective START_DT and END_DT for the schema version.
• IGS_LOOKUPS_VIEW (aliased LKUPS) — the standard IGS lookup view, restricted to LOOKUP_TYPE = 'RESULT_TYPE', used to translate the result type code into its decoded meaning.

The joins enforce version alignment: grading schema code, version number, and grade must match between the administrative unit status assignment and the grading schema grade, with null-safe comparisons for version number and grade.

Key Columns

• ROW_ID — the ROWID of the underlying IGS_AD_ADM_UT_STA_GD row, useful as a surrogate identifier.
• ADMINISTRATIVE_UNIT_STATUS — the administrative unit status to which the grade applies.
• GRADING_SCHEMA_CD / VERSION_NUMBER / GRADE — the grading schema identifier, its version, and the specific grade value.
• S_RESULT_TYPE — the result type code associated with the grading schema grade; the primary search term for this view.
• MEANING — the decoded, descriptive meaning of the result type from the RESULT_TYPE lookup.
• FULL_GRADE_NAME — the descriptive name of the grade.
• START_DT / END_DT — the effective date range of the grading schema version.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

Typical uses include validating that each administrative unit status maps to exactly one effective grade, reporting result types by administrative unit status, and integration extracts that require the decoded result type meaning. A representative query filtering on the searched term follows:

SELECT administrative_unit_status,
       grading_schema_cd,
       version_number,
       grade,
       full_grade_name,
       s_result_type,
       meaning
FROM   igs_ad_adm_ut_sta_gd_v
WHERE  s_result_type = :p_result_type;

A second common pattern checks current applicability by date, restricting to schemas whose effective range brackets the current date. Because the view is documented as not implemented in the reference database, deployment validation should confirm the underlying IGS tables exist and are populated before the view is relied upon in production reports.