Search Results igs_en_cpd_ext_id




Overview
Explore in AI Chat

Overview

The IGS.IGS_EN_CPD_EXT_ALL table is a core setup and configuration table within the Oracle E-Business Suite (EBS) 12.1.1 / 12.2.2, specifically for the Oracle Student Management (OSM) product, under the IGS (iGrants) schema. Its primary role is to store enrollment eligibility setup information. This table defines the business rules and validation steps that determine whether a student is eligible to enroll in a specific course or program based on enrollment category, method type, and student commencement type. It acts as a rule engine configuration table, dictating the sequence of validation checks, the associated rule code to execute, and the consequence (warning or denial) if a validation fails. The inclusion of the *_ALL suffix and the ORG_ID column signifies it is a multi-organization access control (MOAC) enabled table, storing data partitioned by operating unit.

Key Information Stored

The table's columns are designed to capture the complete configuration for an eligibility validation workflow. The system-generated primary key, IGS_EN_CPD_EXT_ID, uniquely identifies each setup record. The core setup context is defined by the combination of ENROLMENT_CAT, ENR_METHOD_TYPE, S_STUDENT_COMM_TYPE, and ORG_ID. For each unique context, the STEP_ORDER_NUM dictates the sequence in which eligibility steps (S_ENROLMENT_STEP_TYPE) are processed. Each step is linked to a specific business rule via S_RULE_CALL_CD and RUL_SEQUENCE_NUMBER. The NOTIFICATION_FLAG column is critical, defining whether a rule failure results in a warning ('WARN') or a hard stop ('DENY'). Additional columns include STUD_AUDIT_LIM for audit unit limits and standard WHO columns for auditing.

Common Use Cases and Queries

This table is central to the enrollment engine's pre-validation logic. Common use cases include troubleshooting enrollment errors, auditing the configured eligibility rules for compliance, and implementing new enrollment policies. A typical query retrieves the complete validation sequence for a specific enrollment scenario. For example, to analyze the eligibility steps for a standard enrollment:

  • SELECT enrolment_cat, step_order_num, s_enrolment_step_type, notification_flag, s_rule_call_cd FROM igs.igs_en_cpd_ext_all WHERE enrolment_cat = 'STANDARD' AND org_id = :org_id ORDER BY step_order_num;

Another critical query pattern involves joining with rule engine tables using S_RULE_CALL_CD and RUL_SEQUENCE_NUMBER to review the actual rule logic. Reporting often focuses on summarizing the 'DENY' versus 'WARN' configurations across different enrollment categories to assess process strictness.

Related Objects

Based on the metadata, the table's primary relationships are defined by its unique indexes. The primary key relationship via IGS_EN_CPD_EXT_ID (index IGS_EN_CPD_EXT_ALL_U1) is likely referenced by foreign keys in child tables, though specific FKs are not listed. The unique composite key on ENROLMENT_CAT, ENR_METHOD_TYPE, ORG_ID, S_ENROLMENT_STEP_TYPE, and S_STUDENT_COMM_TYPE (index IGS_EN_CPD_EXT_ALL_U2) enforces business rule uniqueness and would be the natural join point for setup interfaces or validation logic. This table is a foundational configuration object for the enrollment engine; it is referenced by OSM's enrollment processing logic, likely within PL/SQL packages and forms that manage enrollment eligibility (e.g., IGS_EN_VALIDATE_ENRL), and its S_RULE_CALL_CD column points to the Oracle Rules Engine framework.