Search Results igs_ca_da_pkg




Overview

IGS_RE_S_RES_CAL_CON_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under the ETRM as an "OTHER" API type. It belongs to the Oracle Student System / Student Records (IGS) product family, specifically the Records and Enrollments (RE) module. The package name suggests its function relates to "Result Calendar Control" registration within the Student System. Its primary purpose is to provide the low-level DML (Data Manipulation Language) processing logic against the IGS_RE_S_RES_CAL_CON table, which stores result calendar control records used by institutions to govern how and when student results are calculated, released, or suppressed for a given calendar period.

Because it is classified as an OTHER API rather than a public or private API, it is generally not intended for direct use by external integrations or customers. Instead, it acts as an internal workhorse for the application's own concurrent processing, forms, and higher-level business logic packages.

Key Procedures and Functions

The package exposes nine documented procedures and functions that together implement the standard EBS table-handler pattern:

  • INSERT_ROW — Inserts a new record into the result calendar control table, populating the full set of columns from the calling context.
  • UPDATE_ROW — Modifies an existing record, used when calendar control attributes change.
  • DELETE_ROW — Removes a result calendar control record from the table.
  • ADD_ROW — A convenience routine that adds a row, typically preceded by a lock/validation check against the target key.
  • LOCK_ROW — Obtains a row-level lock (via SELECT ... FOR UPDATE) to prevent concurrent modification of the selected record.
  • GET_PK_FOR_VALIDATION — Resolves and validates the primary key of the target row, ensuring a valid record is being operated upon.
  • CHECK_CONSTRAINTS — Performs application-level constraint validation beyond simple database constraints, which is important because some EBS tables use surrogate keys and enforced-by-application integrity.
  • GET_FK_IGS_CA_DA — Retrieves the foreign key value linking the record to the IGS_CA_DA (calendar/date) entity, ensuring referential relationships are honored.
  • BEFORE_DML — A pre-DML hook that validates and prepares data (for example, standard WHO column defaults) before any insert, update, or delete is executed.

Note that parameter lists are not documented; each routine follows the standard EBS table-handler signature conventions used throughout the IGS schema.

Tables Accessed

The only documented table is IGS_RE_S_RES_CAL_CON, accessed via its APPS synonym. This table holds the result calendar control definitions. The package reads, inserts, updates, and deletes rows in this table and, through GET_FK_IGS_CA_DA, resolves the foreign key relationship to the calendar date entity. No other tables are listed as dependencies beyond SYS.STANDARD and the referenced internal package.

Usage Notes

IGS_RE_S_RES_CAL_CON_PKG is referenced by one other package: IGS_CA_DA_PKG. This is significant because the user's search term "igs_ca_da_pkg" matches that referencing package. In practice, IGS_CA_DA_PKG (the calendar/date package) invokes this result calendar control package when it needs to enforce or persist calendar-level control logic. The package is therefore typically invoked indirectly — through the higher-level calendar processing logic, Student System forms, or concurrent programs that manage result calendar setup. Direct custom invocation is discouraged, since the ETRM classifies it as an OTHER API and it is an internal implementation dependency rather than a public integration point.

Both IGS_RE_S_RES_CAL_CON_PKG and IGS_CA_DA_PKG report a VALID status in the ETRM, indicating the dependency chain is intact and callable in the supported 12.1.1 and 12.2.2 releases.