Results for “igf_ap_attend_map_s”

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

Overview

The APPS.IGF_AP_ATTEND_MAP_PKG package body is a server-side PL/SQL component within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 releases. It belongs to the Oracle iGrants / Financial Aid (IGF) application family, which supports the administration of student financial assistance and grant disbursement processes. The package is classified as an OTHER API, meaning it is not a formally published open interface but a supporting data-access layer invoked internally by other iGrants components. Its primary business function is to manage the association, or "mapping," between attendance records and the underlying award or disbursement entities within the Oracle iGrants schema.

The object status is VALID in the APPS schema. The package encapsulates the database operations required to insert, lock, update, delete, and validate rows in the attendance mapping tables, providing the procedural logic that guarantees consistency of the mapping data across the application.

Key Procedures and Functions

The package body exposes ten documented procedures and functions, each serving a distinct data-manipulation or validation role:

• INSERT_ROW — Inserts a new attendance mapping record into the underlying table.
• LOCK_ROW — Acquires a row-level lock to prevent concurrent modification during a transaction.
• UPDATE_ROW — Modifies an existing attendance mapping record.
• ADD_ROW — Adds a row, typically coordinating surrogate key generation through the sequence.
• DELETE_ROW — Removes an attendance mapping record from the table.
• GET_PK_FOR_VALIDATION — Retrieves the primary key value used during validation checks.
• GET_UK_FOR_VALIDATION — Retrieves the unique key value used to enforce uniqueness during validation.
• GET_FK_IGS_CA_INST — Returns the foreign key reference to the institution/calendar instance entity (IGS_CA_INST_PKG).
• GET_FK_IGS_EN_ATD_TYPE_ALL — Returns the foreign key reference to the attendance type entity (IGS_EN_ATD_TYPE_PKG).
• BEFORE_DML — A pre-DML trigger-style procedure that performs validation and defaulting logic prior to insert, update, or delete operations.

The naming conventions conform to the standard Oracle Forms-generated table-handler pattern, confirming the package supports the iGrants attendance mapping maintenance screen.

Tables Accessed

The package accesses two primary base tables through APPS synonyms:

• IGF_AP_ATTEND_MAP_ALL — The multi-organization (ALL) table holding the attendance mapping records across all business units. Insert, update, delete, and lock operations are directed here.
• IGF_AP_ATTEND_MAP_S — The sequence or single-organization shadow object associated with the mapping table; this corresponds directly to the user's search term and is referenced for surrogate key generation and single-set access.
• DUAL — Used for validation queries returning scalar values or sequences.

It also depends on IGF_AP_ATTEND_MAP_PKG (the specification) and related utility packages including APP_EXCEPTION, FND_GLOBAL, FND_MESSAGE, IGF_AW_GEN, IGS_CA_INST_PKG, IGS_EN_ATD_TYPE_PKG, IGS_GE_GEN_003, and IGS_GE_MSG_STACK for error handling, message resolution, and foreign-key lookups.

Usage Notes

This package is not referenced by any other database object, indicating it is invoked directly from the Oracle Forms-based iGrants attendance mapping user interface rather than through a public PL/SQL API. Typical invocation occurs when a user creates, modifies, or deletes an attendance-to-award mapping within the application. The BEFORE_DML routine enforces validation before the DML is committed, while the foreign-key getters supply the List of Values (LOV) and validation logic for the institution and attendance type fields.

Custom code should not call these procedures directly unless it fully replicates the locking and validation sequence; doing so risks data integrity violations. Developers integrating with this functionality should treat the package as an internal implementation detail and prefer supported iGrants APIs where available.