Search Results igf_ap_attend_map_pkg




Overview
Explore in AI Chat

Overview

IGF_AP_ATTEND_MAP_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite. It belongs to the Oracle Financials product family associated with the IGF module — the Grants/Funds Control and related financial aid processing area that integrates with Oracle Payables. The package implements the data-access layer for the IGF_AP_ATTEND_MAP entity, which records the mapping between attendance-related data and Oracle Payables transactions. In practice, this table and package support the association of attendance records (for example, student or participant attendance captured in Grants/Financial Aid processing) with the accounts payable distribution or invoice information that funds them.

The package is classified as OTHER under the ETRM API classification scheme, meaning it is not a formally published public API but rather an internal repository package generated in the Oracle Forms style. It follows the canonical pattern used throughout EBS for table-handling packages: it exposes DML wrapper procedures plus validation helpers, and it centralizes the derived column logic in a BEFORE_DML trigger-style procedure. The metadata confirms the object status as VALID, indicating the package compiles cleanly in the reference release.

Key Procedures and Functions

The ETRM metadata documents ten procedures and functions within the package:

  • INSERT_ROW — Performs a direct insert of a row into IGF_AP_ATTEND_MAP_ALL, populating the mapped attend/AP columns.
  • UPDATE_ROW — Updates an existing row in the table, keyed on its primary key.
  • DELETE_ROW — Deletes a row identified by its primary key.
  • LOCK_ROW — Issues a SELECT ... FOR UPDATE to serialize concurrent access to a specific row prior to modification.
  • ADD_ROW — A composite convenience routine that typically combines LOCK_ROW/handle derivation with INSERT_ROW for new records.
  • GET_PK_FOR_VALIDATION — Resolves and returns the primary key for a candidate row, used to confirm uniqueness during validation.
  • GET_UK_FOR_VALIDATION — Resolves the unique key columns, supporting duplicate checking on the business key.
  • GET_FK_IGS_CA_INST — Foreign-key helper returning the IGS_CA_INST reference used by the attend-map row.
  • GET_FK_IGS_EN_ATD_TYPE_ALL — Foreign-key helper returning the attendance type reference from IGS_EN_ATD_TYPE_ALL.
  • BEFORE_DML — Central pre-DML routine that derives WHO columns, surrogate keys, and any dependent/denormalized values before an insert or update is written.

Tables Accessed

The package operates against three objects, all reached through APPS synonyms:

  • IGF_AP_ATTEND_MAP_ALL — the base (multi-org) table holding the attendance-to-Payables mapping rows. Insert, update, delete, and lock operations target this table.
  • IGF_AP_ATTEND_MAP_S — the sequence-backed surrogate-key source; BEFORE_DML draws the next primary-key value from this object.
  • DUAL — used for single-row arithmetic and sysdate-style derivations inside BEFORE_DML and the validation helpers.

Usage Notes

Because IGF_AP_ATTEND_MAP_PKG is an OTHER-classified, Forms-generated package, its primary callers are the Oracle Forms user interface for the IGF_AP_ATTEND_MAP maintenance window. Standard EBS Forms trigger logic invokes ADD_ROW, UPDATE_ROW, DELETE_ROW, and LOCK_ROW on corresponding block operations, while GET_PK_FOR_VALIDATION, GET_UK_FOR_VALIDATION, and the two foreign-key functions support LOV and validation triggers. The metadata shows the package is referenced by zero other PL/SQL packages, confirming that it is a leaf-level data-access component rather than a shared business API.

For Oracle EBS 12.1.1 to 12.2.2 upgrades, the object is expected to remain VALID without remediation. Custom code should not call these procedures directly, since they bypass form-level validation and multi-org security handling; the supported integration path is through the Forms UI or through a formally published API in the same product family. Any direct DML should replicate BEFORE_DML derivations, including surrogate-key population from IGF_AP_ATTEND_MAP_S and standard WHO column stamping, to avoid data integrity gaps.