Search Results get_rowid

Overview

APPS.GMS_OVERRIDE_SCHEDULES_PKG is a table-handler PL/SQL package that encapsulates DML operations for the GMS_OVERRIDE_SCHEDULES table in Oracle EBS Grants Management (GMS). The package provides a controlled API surface for maintaining override schedule records associated with awards, projects, and tasks, including the indirect cost schedule and the cost indicator schedule fixed date. It follows the Oracle Forms-generated table-handler pattern, combining an INSERT cursor with the standard WHO column management (creation_date, created_by, last_update_date, last_updated_by, last_update_login) and FND_GLOBAL session context. Its header comment ($Header: gmsicovb.pls 115.8) confirms it is a seeded Oracle file shipped with the GMS product, classified in the ETRM as an API of type "OTHER."

Key Procedures and Functions

The package exposes four documented procedures:

• INSERT_ROW — Inserts a new override schedule row. The source listing shows it accepts the award, project, task, IDC schedule, and cost indicator schedule fixed date values, along with a mode flag (default 'R'). The private cursor get_rowid selects the ROWID of the newly inserted row from GMS_OVERRIDE_SCHEDULES, matching on award_id, project_id, and task_id (with NULL-safe comparison for task_id), and returns it through the OUT NOCOPY p_rowid parameter. If no row is found, the procedure raises NO_DATA_FOUND. Mode 'I' assigns the seeded user (1) and login (0); mode 'R' (default) resolves the runtime user and login via FND_GLOBAL, defaulting to -1 when null; any other mode raises the FND 'SYSTEM-INVALID ARGS' exception.
• UPDATE_ROW — Updates an existing override schedule record, taking the ROWID as input and accepting the project, task, IDC schedule, and cost indicator schedule fixed date attributes.
• DELETE_ROW — Deletes an override schedule row, referencing the target row by ROWID.
• LOCK_ROW — Acquires a row-level lock on an override schedule record, typically used to serialize concurrent modifications.

Tables Accessed

All four procedures operate against a single table, GMS_OVERRIDE_SCHEDULES, which is referenced through the APPS synonym. This table stores the override relationships between an award or project (optionally a specific task) and the applicable indirect cost (IDC) schedule, together with the fixed date on which the cost indicator schedule takes effect. INSERT_ROW writes to the table and then reads it back to retrieve the generated ROWID; UPDATE_ROW, DELETE_ROW, and LOCK_ROW manipulate the same table by ROWID.

Usage Notes

Because this is a Forms-generated table handler, it is normally invoked indirectly by Oracle Forms modules in the Grants Management responsibility rather than called directly by end users. The ROWID-based signature of UPDATE_ROW, DELETE_ROW, and LOCK_ROW reflects the standard Oracle Forms "block" pattern, where the form holds the ROWID of the current record and passes it to the database package. The p_mode convention allows the package to distinguish between setup/conversion loads ('I') and interactive runtime sessions ('R'), ensuring audit columns reflect the correct user identity. Custom integrations or interfaces that need to maintain override schedules should invoke these procedures through the APPS schema and should supply a valid ROWID for update, delete, and lock operations. No other package in the ETRM metadata references this package, indicating a narrow usage footprint tied primarily to the originating form.