Search Results igs_ad_batc_def_det_s

Overview

The package body APPS.IGS_AD_BATC_DEF_DET_PKG is a database-tier PL/SQL module in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments. It belongs to the Oracle Student System / Student Information Management family of modules, indicated by the IGS_ prefix, which denotes components serving the higher-education and academic-institution feature set. The package encapsulates the data-manipulation logic and validation rules for the batch definition detail entity, exposed through the base table IGS_AD_BATC_DEF_DET_ALL and its associated sequence IGS_AD_BATC_DEF_DET_S. As a package body with API classification OTHER, it functions as an internal, generated-style data-access layer rather than a published public API. Its role is to centralize insert, update, delete, and locking operations against the batch definition detail table so that client-side forms, concurrent programs, and dependent packages do not issue direct DML against the base table.

Key Procedures and Functions

The ETRM documentation lists seven procedures within this package body. Their documented purposes are as follows:

• INSERT_ROW — Performs the physical insert of a new batch definition detail record, populating the attributable columns and retrieving the primary key value from the sequence.
• UPDATE_ROW — Applies modifications to an existing batch definition detail record, updating the attributable and who-columns for the target row.
• LOCK_ROW — Acquires a row-level lock on a specific batch definition detail record to enforce optimistic concurrency control prior to an update.
• ADD_ROW — Provides the higher-level entry point for adding a new record, typically orchestrating key generation, validation, and delegation to INSERT_ROW.
• GET_PK_FOR_VALIDATION — Returns the primary key of the target record so that validation logic can confirm the row's existence and identity before DML proceeds.
• DELETE_ROW — Removes a batch definition detail record from the base table.
• BEFORE_DML — A pre-DML hook that executes standard housekeeping, such as setting WHO audit columns and enforcing mandatory attribute defaults.

No parameter lists are documented, and none are inferred here.

Tables Accessed

The package operates on two documented database objects, both referenced through APPS synonyms:

• IGS_AD_BATC_DEF_DET_ALL — the base table holding batch definition detail rows. All INSERT, UPDATE, DELETE, and SELECT operations are directed here.
• IGS_AD_BATC_DEF_DET_S — the associated sequence used to generate surrogate primary keys for new records.

This pairing follows the standard EBS pattern in which a generated package body wraps a single entity table and its key-generation sequence. The sequence name matches the object name the user searched for (igs_ad_batc_def_det_s), confirming that this package is the primary DML interface for that table.

Usage Notes

The package body depends on several standard EBS utilities, including FND_GLOBAL for session and user context, FND_MESSAGE and APP_EXCEPTION for error signaling, IGS_GE_MSG_STACK for the message stack, and IGS_GE_GEN_003 for shared general routines. It is not referenced by any other database object, indicating it is invoked only from the presentation or application tier rather than from within other server-side code. Typical invocation sources include the associated Oracle Forms block for batch definition details and any custom PL/SQL that must create, amend, or delete batch definition detail records. Because the procedures are not documented as a public API, callers should invoke them in the intended sequence — validation and locking before DML, and ADD_ROW rather than INSERT_ROW for new records — to preserve the integrity of the batch definition detail data.