Search Results get_ufk_igs_ps_unit_ofr_opt

Overview

IGS_AS_NOTIFY_BE_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Oracle Student System (formerly Oracle iLearning / Student Systems) module family identified by the IGS prefix. It is a Business Entity (BE) support package, declared with AUTHID CURRENT_USER, whose purpose is to encapsulate the DML operations, concurrency control, and primary key validation logic for the IGS_AS_NOTIFY_BE database table. In the Oracle EBS architecture, BE packages of this type form the procedural backbone behind the generated Forms and the Table-API style programmatic interface, ensuring that inserts, updates, deletes, and locks against the underlying entity table follow consistent, centralized business rules. The package is classified as OTHER in the ETRM repository, reflecting that it is not a public, externally supported API but an internal implementation object used by Oracle Forms and by other application modules within the same product family. The package carries the standard header revision marker $Header: IGSDI65S.pls 115.1, indicating that the current version has been stable since 2002 and is equally applicable to Oracle EBS 12.1.1 and 12.2.2, where the IGS schema objects retain backward compatibility.

Key Procedures and Functions

The package exposes eight documented procedures and functions covering the complete lifecycle of a record in the entity table:

• INSERT_ROW — Inserts a new row into IGS_AS_NOTIFY_BE, populating the primary key identifier and the internal name attribute.
• LOCK_ROW — Acquires a row-level lock on an existing record to support optimistic concurrency control during form-based edits.
• UPDATE_ROW — Modifies an existing record identified by its rowid and unique key values.
• ADD_ROW — A convenience wrapper that combines the insert path with rowid return, used when a new entity must be created and immediately referenced.
• DELETE_ROW — Removes a record from the entity table, addressed by its rowid.
• GET_PK_FOR_VALIDATION — Returns a Boolean indicating whether a given combination of unique key values exists, validating the primary/unique key before DML.
• GET_UFK_IGS_PS_UNIT_OFR_OPT — Resolves and returns the unique foreign key relationship associated with IGS_PS_UNIT_OFR_OPT (Unit Offering Option), making the descriptive value available to the notification entity for display or downstream processing.
• BEFORE_DML — A shared pre-DML hook invoked by the other DML routines to apply the standard WHO columns (creation date, created by, last update date, last updated by, last update login) and any entity-specific defaults before writing to the table.

Tables Accessed

The package operates against a single documented entity table, IGS_AS_NOTIFY_BE, accessed through an APPS synonym. This table stores notification business entity records that link the notification framework to student-system entities such as unit offering options. All DML in the package is directed at this table; the IGS_PS_UNIT_OFR_OPT reference is resolved through GET_UFK_IGS_PS_UNIT_OFR_OPT rather than being written directly, indicating that the unit offering option is a parent/reference entity whose unique key is carried as a foreign key within IGS_AS_NOTIFY_BE.

Usage Notes

IGS_AS_NOTIFY_BE_PKG is not intended to be called directly by end users or external integrations. It is invoked in three typical scenarios. First, Oracle Forms in the Student System module call INSERT_ROW, LOCK_ROW, UPDATE_ROW, DELETE_ROW, and ADD_ROW to implement the standard block-level DML behavior for the notification entity. Second, the BEFORE_DML routine is called internally by the other DML procedures to populate audit columns, so custom code should not bypass it. Third, GET_PK_FOR_VALIDATION and GET_UFK_IGS_PS_UNIT_OFR_OPT are called during validation and reference-resolution events, for example when the form must confirm a unique key or translate a unit offering option foreign key into a displayable value. Because the package is documented as referenced by one other package, developers should treat it as an internal dependency and prefer the supported public APIs of the IGS product when extending functionality. As with all AUTHID CURRENT_USER packages in EBS 12.1.1 and 12.2.2, privileges are resolved against the calling schema, which reinforces the need to invoke the package from within the APPS context.