Results for “igs_as_notify_be_pkg”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IGS_AS_NOTIFY_BE_PKG is a table-handler PL/SQL package that belongs to the Oracle Student System (formerly Oracle iLearning/Student Administration) application, deployed in the APPS schema. The suffix "AS" identifies it as part of the Academic Support or Assessment/Notification subsystem, while "NOTIFY_BE" refers to the underlying notification business entity it manages. In Oracle EBS 12.1.1 and 12.2.2, this package serves as the programmatic gateway for maintaining rows in the IGS_AS_NOTIFY_BE table, which stores notification records generated by student administration processes such as assessment due-date alerts, enrollment confirmations, and institutional correspondence.

The object is catalogued with an API classification of OTHER rather than a public or private API designation, indicating that it functions primarily as an internal persistence layer rather than a documented integration interface. Its status in ETRM is VALID, confirming the compiled body exists in the APPS schema without dependency errors.

Key Procedures and Functions

ETRM documents eight procedures and functions within this package body:

• INSERT_ROW — Inserts a new notification business-entity record into the underlying table, populating all mandatory and supplied columns.
• LOCK_ROW — Acquires a row-level lock on an existing notification record to prevent concurrent modification during a transaction.
• UPDATE_ROW — Modifies the attributes of an existing notification record identified by its primary key.
• ADD_ROW — Combines insert and update behaviour, adding a record when it does not already exist and applying updates otherwise.
• DELETE_ROW — Removes a notification record from the entity table.
• GET_PK_FOR_VALIDATION — Returns the primary-key components used to validate that a target row exists prior to DML operations.
• GET_UFK_IGS_PS_UNIT_OFR_OPT — Resolves the user foreign key referencing the unit offering option, retrieving the surrogate identifier from IGS_PS_UNIT_OFR_OPT_PKG for referential integrity.
• BEFORE_DML — Performs pre-DML housekeeping such as WHO-column stamping and standard validation checks before insert, update, or delete actions execute.

No parameter signatures are supplied in the ETRM excerpt; callers should inspect the specification in the database rather than assume argument order.

Tables Accessed

The only documented table accessed through APPS synonyms is IGS_AS_NOTIFY_BE. All eight procedures operate against this single business entity, which holds the notification master data. Reads and writes are performed exclusively through the DML wrappers described above, ensuring consistent enforcement of the entity's validation rules, WHO audit columns, and locking semantics. The foreign-key helper resolves related unit offering option data via IGS_PS_UNIT_OFR_OPT_PKG rather than direct table access, preserving encapsulation of that related entity.

Usage Notes

Because this package is not referenced by any other database object, it is not invoked from dependent PL/SQL units inside the database. Instead it is called from the client tier — typically Oracle Forms modules in the Student System responsibility — or from custom concurrent programs and extensions that need to create or maintain notification records. The BEFORE_DML procedure should always precede the DML wrappers, since it encapsulates the mandatory pre-processing that the entity requires.

The package depends on APP_EXCEPTION, FND_GLOBAL, FND_MESSAGE, and IGS_GE_MSG_STACK for error handling and message retrieval, and on IGS_AS_NOTIFY_BE_PKG itself for cross-referencing the specification. This dependency profile is characteristic of Oracle EBS table-handler packages that raise errors through the standard FND message stack. Custom code that calls these procedures must run within an APPS-initialised session so that FND_GLOBAL can resolve the current user and login context; otherwise the WHO-column population in BEFORE_DML will fail. Given its internal classification, Oracle does not guarantee backward compatibility across patches, so customers extending this package should re-verify signatures after applying Student System patches on either 12.1.1 or 12.2.2.