Results for “igs_ge_invalid_value”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The APPS.IGS_AS_ENTRY_CONF_PKG package body belongs to the Oracle E-Business Suite Student Systems (Advanced Studies / Assessment) module. Its purpose is to encapsulate the configuration rules governing assessment mark entry, grade derivation, and validation behavior for a given assessment control record. The package centralizes the logic by which the IGS_AS_ENTRY_CONF table is maintained, providing a controlled API layer over a table that stores the operational flags and thresholds used when marks and grades are entered, uploaded, or finalized.
Among the configuration columns governed by this package is KEY_ALLOW_INVALID_IND, the flag referenced in the SET_COLUMN_VALUES procedure signature. This indicator determines whether invalid mark or grade values are permitted during entry for the associated control number, and it is one of several parallel indicators (for example KEY_AI_ALLOW_INVALID_FLAG) that drive validation outcomes elsewhere in the assessment subsystem. The package is classified as an OTHER API within ETRM and is not referenced by any other database package, indicating that it is primarily consumed by the Oracle Forms layer rather than through inter-package calls.
The header comment identifies the source file as IGSDI46B.pls, version 115.11, last updated 2003/12/05. The body declares package-level variables l_rowid, old_references, and new_references typed against the igs_as_entry_conf row type, which is the standard Oracle Forms-generated pattern for maintaining old and new column images during insert and update processing.
Key Procedures and Functions
The package exposes eight documented procedures. None of the parameter lists are reproduced here; the descriptions reflect their documented purpose within the generated API pattern.
- INSERT_ROW — Inserts a new configuration record into
IGS_AS_ENTRY_CONF, populating the columns from the supplied arguments and standard WHO audit columns. - LOCK_ROW — Obtains a row-level lock on the target configuration record, typically used when a form enters update mode to prevent concurrent modification.
- UPDATE_ROW — Applies changes to an existing configuration record identified by rowid, including the
KEY_ALLOW_INVALID_INDindicator and related validation flags. - ADD_ROW — Provides an insert-or-update entry point used by the form layer to create a record when none exists or to modify an existing one.
- DELETE_ROW — Removes the configuration record associated with the supplied identifier.
- GET_PK_FOR_VALIDATION — Returns the primary key value for a record so that the form can perform validation against the correct row.
- CHECK_CONSTRAINTS — Validates that referential and business constraints on the configuration record are satisfied before DML is committed.
- BEFORE_DML — Sets up the old and new reference row structures and performs the pre-DML processing common to insert and update operations.
The private helper SET_COLUMN_VALUES assigns action, rowid, and column values to the old_references and new_references structures. It opens the cur_old_ref_values cursor to fetch the current row image and, if the row is not found for a non-insert action, raises the standard FND_MESSAGE text FORM_RECORD_DELETED and adds it to the message stack via IGS_GE_MSG_STACK.ADD.
Tables Accessed
The package operates against a single documented table, IGS_AS_ENTRY_CONF, accessible through its APPS synonym. This table stores the assessment entry control configuration, including the invalid-value allowance indicator (KEY_ALLOW_INVALID_IND), mark collection and grade derivation flags, mandatory mark indicators, upload-related validation flags for person, enrollment, unit, and grade conditions, and mark-entry decimal precision settings. The package reads the table to populate the old reference image and writes to it for insert, update, and delete operations.
Usage Notes
Because ETRM lists no dependent packages, IGS_AS_ENTRY_CONF_PKG is expected to be invoked from the Oracle Forms maintenance interface for assessment entry configuration rather than from other PL/SQL APIs. The procedures follow the conventional generated-API contract: BEFORE_DML and SET_COLUMN_VALUES prepare the row images, CHECK_CONSTRAINTS enforces integrity, and the DML procedures commit changes. Custom code that must alter configuration values, including KEY_ALLOW_INVALID_IND, should call UPDATE_ROW or ADD_ROW rather than issuing direct DML, so that the standard validation and message-stack handling are preserved. Direct updates also risk bypassing the row-not-found detection implemented in the old-reference cursor.