Search Results core_indicator_code




Overview
Explore in AI Chat

Overview

The IGS_PR_UL_MARK_DTL table is a configuration table within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, owned by the IGS (iGrads/Student) product family. It plays a critical role in the academic progression and assessment modules by defining the detailed rules for calculating student marks based on their unit load. Specifically, it stores configuration details that dictate how unit attempts—categorized as core, optional, or elective—are selected and prioritized for inclusion in a student's overall mark calculation. This table operates as a child to the primary mark configuration header, enabling a flexible and rule-based approach to academic performance evaluation.

Key Information Stored

The table's columns define the parameters for unit selection in marks calculation. The primary identifier is the composite key of MARK_CONFIG_ID and CORE_INDICATOR_CODE. The MARK_CONFIG_ID is a foreign key linking to the parent configuration in IGS_PR_UL_MARK_CNFG. The CORE_INDICATOR_CODE (VARCHAR2(30)) classifies the unit attempt type. Configuration rules are set through several key columns: TOTAL_CREDITS (NUMBER) specifies the credit volume to select for the indicator type, while REQUIRED_FLAG (VARCHAR2) indicates if meeting this total is mandatory, defaulting to 'N'. The order and method of selection are controlled by PRIORITY_NUM (NUMBER) and UNIT_SELECTION_CODE (VARCHAR2(30)). Standard EBS "Who" columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) complete the record for auditing.

Common Use Cases and Queries

This table is central to backend processes that automate the compilation of student results. A common use case is generating a provisional or final grade by applying a specific mark configuration to a student's academic record. The system uses the priority and selection codes defined here to filter and order eligible unit attempts before applying calculation logic. For reporting and troubleshooting, administrators may query the active rules for a given configuration. A typical query to review all detail rules for a specific mark configuration ID would be:

  • SELECT CORE_INDICATOR_CODE, TOTAL_CREDITS, REQUIRED_FLAG, PRIORITY_NUM, UNIT_SELECTION_CODE FROM IGS.IGS_PR_UL_MARK_DTL WHERE MARK_CONFIG_ID = :config_id ORDER BY PRIORITY_NUM;

Another critical query involves validating configuration completeness, such as checking for any core indicator types where the REQUIRED_FLAG is 'Y' but TOTAL_CREDITS is NULL or zero, which could indicate a setup error.

Related Objects

The IGS_PR_UL_MARK_DTL table has a direct and essential relationship with its parent configuration header. It is referenced by the APPS synonym IGS_PR_UL_MARK_DTL, which facilitates access within the application layer.

  • Primary Key: IGS_PR_UL_MARK_DTL_PK on columns (MARK_CONFIG_ID, CORE_INDICATOR_CODE). This enforces uniqueness of rule definitions per indicator type within a configuration.
  • Foreign Key (Parent): The MARK_CONFIG_ID column references the TABLE: IGS.IGS_PR_UL_MARK_CNFG. This establishes that every detail record must belong to a valid, existing mark configuration header.

There are no documented dependencies where this table references other objects, positioning it as a terminal node in this specific configuration hierarchy, with data primarily driven by setup activities.