Search Results igsbv_usec_grading_schemas

Overview

IGSBV_USEC_GRADING_SCHEMAS is a base database view within the Oracle E-Business Suite IGS — Student System product family. The product is flagged as Obsolete in the ETRM metadata, which signals that the surrounding functionality has been superseded by the Oracle Student System (formerly PeopleSoft Campus Solutions) and that no further development or support is delivered for these objects in EBS 12.1.1 or 12.2.2. The view presents grading schema assignments made at the unit section level, joining each unit section grading schema record to its grading schema definition and to the unit offering option to which it applies.

Its role is primarily reporting and integration: it flattens a three-way join into a single denormalized row, allowing report writers, extracts, and downstream interfaces to consume grading schema information without reconstructing the underlying relationships. Because it is a view with a WITH READ ONLY clause, it cannot be used as an update target, which reinforces its purpose as a query and extraction object rather than a transactional one.

Underlying Base Objects

The view is defined over three base tables, joined on grading schema code and version number, and on the unit offering option identifier:

• IGS_PS_USEC_GRD_SCHM — the driving table, holding the assignment of a grading schema to a unit section (alias US).
• IGS_AS_GRD_SCHEMA — the grading schema definition itself (alias GR), supplying the descriptive text.
• IGS_PS_UNIT_OFR_OPT_ALL — the unit offering option (alias UN), supplying unit, version, calendar, location, and unit class context. The _ALL suffix indicates that this table includes records across operating units and possibly across the full date-effective range.

The join predicates are US.GRADING_SCHEMA_CODE = GR.GRADING_SCHEMA_CD combined with US.GRD_SCHM_VERSION_NUMBER = GR.VERSION_NUMBER, ensuring the correct version of the schema is matched, and US.UOO_ID = UN.UOO_ID, tying the assignment back to the specific unit offering option. The view is documented as not implemented in the reference database, and referenced base objects are not separately documented in the ETRM metadata, so the join logic embedded in the view text is the authoritative source. In 12.1.1 and 12.2.2 these IGS tables follow identical structures, so the view behaves consistently across both releases.

Key Columns

• UNIT_SECTION_GRADING_SCHEMA_ID — Primary key of the underlying assignment record, uniquely identifying a grading schema attached to a unit section.
• UNIT_SECTION_ID — The unit offering option identifier (UOO_ID) that the grading schema applies to.
• GRADING_SCHEMA_CODE and GRD_SCHM_VERSION_NUMBER — The grading schema code and its version, together forming the logical reference to IGS_AS_GRD_SCHEMA.
• DEFAULT_GRAD_SCHEMA_INDICATOR — Derived from DEFAULT_FLAG; indicates whether this schema is the default for the unit section.
• GRADING_SCHEMA_DESCRIPTION — Descriptive text for the grading schema, useful for reporting without a further join.
• UNIT_CODE, VERSION_NUMBER, CALENDAR_TYPE, CAL_INST_SEQUENCE_NUMBER, LOCATION_CODE, UNIT_CLASS — Contextual attributes describing which unit, version, calendar, location, and class the offering belongs to.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — Standard EBS audit columns, inherited from the assignment table for traceability.

Common Use Cases and Queries

Typical uses include auditing which grading schemas are assigned to unit sections, confirming which schema is flagged as default, and feeding grading configuration into data warehouses or migration extracts.

SELECT unit_section_id, unit_code, version_number,
       calendar_type, grading_schema_code,
       grading_schema_description, default_grad_schema_indicator
FROM   igsbv_usec_grading_schemas
WHERE  unit_code = :p_unit_code
AND    calendar_type = :p_cal_type;

To identify default schemas per unit section:

SELECT unit_section_id, unit_code, grading_schema_code
FROM   igsbv_usec_grading_schemas
WHERE  default_grad_schema_indicator = 'Y';

Because the view is read-only and query-only, it is safe for concurrent reporting workloads, though as an obsolete IGS object it should be replaced by its supported successor in new development.