Search Results get_fk_igs_ca_da

Overview

IGS_CA_DA_PAIR_PKG is a table-handler PL/SQL package owned by the APPS schema in Oracle E-Business Suite. It belongs to the Student Systems / Campus Community product family, where the "IGS" prefix denotes the Oracle Student System modules and "CA" identifies the Calendar/Date Alias component. The package encapsulates the DML and validation logic for the IGS_CA_DA_PAIR entity, which models a relationship between two date aliases — a primary date alias and its related (paired) date alias. This pairing construct allows an institution to express scheduling or calendar rules such as "the date that falls N days after a given date alias," enabling derived date computations used throughout enrolment, teaching, and assessment calendars.

The package is declared AUTHID CURRENT_USER, and the header confirms a legacy Oracle Forms-generated table handler, as evidenced by the "$Header: IGSCI10S.pls 115.3 2002/11/28" comment. Such packages exist primarily to provide the Forms block-level DML, locking, and validation services for the underlying table and to expose reusable validation entry points to other server-side code.

Key Procedures and Functions

The package exposes seven documented program units:

• INSERT_ROW — Inserts a new date-alias pair row into the base table. It accepts the primary date alias, the related date alias, a rowid out parameter, and a mode flag used to signal the type of DML operation.
• LOCK_ROW — Acquires a row-level lock on an existing pair record identified by rowid, taking the alias columns to support optimistic locking consistent with Oracle Forms behaviour.
• DELETE_ROW — Removes a pair record identified by rowid.
• GET_PK_FOR_VALIDATION — A function returning a Boolean that confirms whether the supplied combination of primary and related date aliases constitutes a valid existing primary key, used to validate user input before DML.
• GET_FK_IGS_CA_DA — A validation procedure that verifies the primary date alias against the parent IGS_CA_DA (date alias) table, enforcing the foreign-key relationship. This is the routine most frequently searched by developers diagnosing date-alias integrity errors.
• CHECK_CONSTRAINTS — Performs column-level constraint validation, optionally scoped to a specific column name and value, applying the table's declarative constraint rules to the supplied data.
• BEFORE_DML — The central pre-DML hook that normalises and prepares the who-columns (creation date, created by, last update date, last updated by, last update login) and enforces mandatory-column and business rules before insert or update operations are applied.

Tables Accessed

The package operates against a single base table, IGS_CA_DA_PAIR, accessed through its APPS synonym. This table stores the parent-child relationship between a date alias and its related date alias. Reads are performed by GET_PK_FOR_VALIDATION, LOCK_ROW, and GET_FK_IGS_CA_DA; writes are performed by INSERT_ROW, DELETE_ROW, and the BEFORE_DML processing path. Validation of the foreign-key reference to the IGS_CA_DA date-alias entity is implicit in the GET_FK_IGS_CA_DA routine.

Usage Notes

IGS_CA_DA_PAIR_PKG is typically invoked from Oracle Forms date-alias maintenance screens in the Student System, where the block-level triggers call INSERT_ROW, LOCK_ROW, DELETE_ROW, and CHECK_CONSTRAINTS during normal user interaction. The package is also referenced by one other documented package, meaning server-side batch or concurrent processing relies on it for pair validation. In custom development it should not be called directly for logic that duplicates the standard date-alias maintenance path; instead, reuse GET_FK_IGS_CA_DA and GET_PK_FOR_VALIDATION when validating user-supplied alias pairs. Because the package is AUTHID CURRENT_USER, grants on IGS_CA_DA_PAIR must be present for any schema invoking it outside APPS. The package has no documented change history beyond the 2002 stamp, so its behaviour is stable across EBS 12.1.1 and 12.2.2.