Results for “igf_db_awd_disb_dtl_pkg”

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

Overview

The APPS.IGF_DB_AWD_DISB_DTL_PKG package body is a database-side PL/SQL component belonging to the Oracle E-Business Suite (EBS) Financial Aid / Student Systems family of modules (the IGF schema prefix, referencing award and disbursement functionality). It provides the procedural layer that governs the detail records of award disbursements — the individual scheduled payments that make up a disbursement plan for a student award. Classified in the ETRM dictionary under API classification OTHER and carrying a VALID status, this package is a table-handler style package rather than a public business API. It encapsulates the standard row-level DML operations for the award disbursement detail entity, ensuring that inserts, updates, deletions, and lock operations are performed consistently and that the referential relationships between the detail table and its parent award disbursement header are preserved. The package body is owned by APPS and its dependencies confirm reliance on EBS infrastructure utilities such as FND_GLOBAL, FND_MESSAGE, APP_EXCEPTION, IGS_GE_MSG_STACK, and the award-side packages IGF_AW_AWD_DISB_PKG and IGF_AW_GEN.

Key Procedures and Functions

The documented package exposes eight procedures and functions. Descriptions of purpose follow; parameter lists are not part of the available metadata and are therefore not enumerated.

• INSERT_ROW — Performs the core insertion of a new award disbursement detail record, populating mandatory columns and audit fields as defined by the table handler pattern.
• LOCK_ROW — Acquires a row-level lock on an existing detail record to prevent concurrent modification during a transactional sequence.
• UPDATE_ROW — Applies changes to an existing disbursement detail record while maintaining conformity with the table's constraints.
• ADD_ROW — A higher-level convenience routine that coordinates the addition of a detail row, typically validating context before delegating to the insertion logic.
• DELETE_ROW — Removes a disbursement detail record, respecting referential and integrity rules before deletion.
• GET_PK_FOR_VALIDATION — Retrieves the primary key of the detail record, used during validation routines to confirm row identity prior to processing.
• GET_FK_IGF_AW_AWD_DISB — Returns the foreign key linking the detail row to its parent award disbursement record, supporting the parent-child association central to the disbursement model.
• BEFORE_DML — A pre-DML hook that prepares and standardises row data and audit information prior to any insert, update, or delete operation.

Tables Accessed

The package operates against IGF_DB_AWD_DISB_DTL_ALL, the award disbursement detail table, accessed through its APPS synonym. Dependency metadata also references IGF_DB_AWD_DISB_DTL and IGF_DB_AWD_DISB_DTL_PKG itself. The _ALL suffix indicates a multi-organisation (multi-org) enabled table, meaning row-level access is filtered by the operating unit context established through FND_GLOBAL. This table stores the individual disbursement line records that decompose an award disbursement schedule, and the package reads and writes it to manage those lines within the correct organisational and security context.

Usage Notes

As a table-handler package rather than a public API, IGF_DB_AWD_DISB_DTL_PKG is typically invoked indirectly. It is called by Oracle Forms-based maintenance screens for award disbursements, by other IGF packages, and by the award disbursement processing logic in IGF_AW_AWD_DISB_PKG and IGF_AW_GEN. The metadata records that the package is referenced by eight other database objects, confirming its role as an internal utility serving the disbursement subsystem. Custom code should generally avoid calling these procedures directly and should instead use documented public APIs, since the internal routines assume the calling context already has the correct organisation and audit state initialised. Because it depends on FND_GLOBAL and FND_MESSAGE, correct session initialisation and message-stack handling are prerequisites for reliable execution under both EBS 12.1.1 and 12.2.x.