Search Results change_grading_schema_cd




Overview

The IGS_AS_CHN_GRD_REQ table is a core data object within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the Oracle Student Management (OSM) or Campus Solutions modules. It functions as a historical and transactional audit log for formal requests to alter a student's academic assessment. The table's primary role is to capture the complete lifecycle of a grade change request, from its initiation by a requester through to its approval or rejection by an authorized approver. This ensures a secure, auditable, and workflow-driven process for modifying critical student academic records, maintaining data integrity and compliance.

Key Information Stored

The table stores comprehensive details for each grade change transaction. Key columns are logically grouped to capture the original state, the proposed change, and the approval workflow. The original assessment is stored in the CURRENT_MARK, CURRENT_GRADING_SCHEMA_CD, CURRENT_GS_VERSION_NUMBER, and CURRENT_GRADE columns. The proposed change is captured in the parallel CHANGE_MARK, CHANGE_GRADING_SCHEMA_CD, CHANGE_GS_VERSION_NUMBER, and CHANGE_GRADE columns, directly addressing the user's search for "change_grading_schema_cd". The academic context is defined by PERSON_ID, COURSE_CD, UNIT_CD, UNIT_CLASS, and calendar columns (TEACH_CAL_TYPE, TEACH_CI_SEQUENCE_NUMBER). The request workflow is managed through REQUESTER_ID, REQUESTER_COMMENTS, APPROVER_ID, APPROVER_DATE, APPROVER_COMMENTS, and the CURRENT_STATUS column, which tracks the request as 'IN PROGRESS', 'REJECTED', or 'APPROVED'. Standard WHO columns (CREATED_BY, CREATION_DATE, etc.) provide audit trails.

Common Use Cases and Queries

This table is central to reporting and auditing grade change activities. Common use cases include generating audit reports for academic compliance, reviewing the history of changes for a specific student or unit offering, and monitoring pending requests. A typical query to find all approved changes for a specific grading schema would be:

  • SELECT person_id, unit_cd, current_grade, change_grade, requester_id, approver_date FROM igs.igs_as_chn_grd_req WHERE change_grading_schema_cd = '&schema_code' AND current_status = 'APPROVED';

Another frequent pattern is to join with person tables to generate a report of all pending ('IN PROGRESS') requests for an academic period, including requester names and justifications, for administrative review.

Related Objects

The IGS_AS_CHN_GRD_REQ table maintains critical referential integrity through defined foreign key relationships, linking it to master data and validation tables. As per the provided metadata, the documented relationships are:

  • IGS_AS_GRD_SCH_GRADE: The CHANGE_GRADING_SCHEMA_CD column references this table to validate the proposed new grading schema code. The CURRENT_GRADING_SCHEMA_CD column also references this same table to validate the original grading schema.
  • IGS_EN_SU_ATTEMPT_ALL: The PERSON_ID column references this student unit attempt table, ensuring the grade change request is associated with a valid student enrollment record.

Furthermore, the table's primary key (IGS_AS_CHN_GRD_REQ_PK) on PERSON_ID, COURSE_CD, UOO_ID, and REQUEST_DATE ensures uniqueness of each request record. It is commonly the parent table in joins for detailed historical reports and is a key source for the Grade Change workflow within the application.

  • TABLE: IGS.IGS_AS_CHN_GRD_REQ 12.1.1

    owner:IGS,  object_type:TABLE,  fnd_design_data:IGS.IGS_AS_CHN_GRD_REQ,  object_name:IGS_AS_CHN_GRD_REQ,  status:VALID, 

  • eTRM - IGS Tables and Views 12.1.1

    description: Holds applicant whose records are wrongly available . It is recommended that such applicant records are deleted from the system . It synchronizes with UCAS view 'ivStarW'. ,