Search Results p_map_id

Overview

IGW_ORG_MAPS_ALL_PKG is a stored PL/SQL package owned by the APPS schema in Oracle E-Business Suite. Its name and signature identify it as the low-level table-handling package (often referred to informally as the "row handler" or "table API") for the IGW_ORG_MAPS_ALL table, which stores organization map definitions used within the Grants and Oracle Projects accounting/grant management family of applications. Organization maps relate a map identifier (map_id) to an organization_id, together with descriptive text and an effective date range (start_date_active and end_date_active). These records allow Oracle Grants/Projects to associate organizations with mapping constructs for costing, burdening, or organizational roll-up purposes.

The package is declared with AUTHID CURRENT_USER, meaning that its SQL statements execute under the privileges of the calling user rather than the package owner. This is a significant design characteristic: any caller must therefore hold the necessary object privileges on IGW_ORG_MAPS_ALL (typically through the APPS synonym) to invoke the procedures successfully. The package exposes a classic four-procedure Data Manipulation Language API set for a single table: insert, lock, update, and delete.

Key Procedures and Functions

The package documents four procedures. No functions and no additional procedures are present in the metadata. Each procedure maps directly to a standard CRUD operation:

• INSERT_ROW — Inserts a new row into the organization maps table. It accepts an OUT NOCOPY rowid parameter (x_rowid) that returns the ROWID of the newly created row, along with the business columns: map identifier (p_map_id), organization (p_organization_id), a descriptive text field (p_description), and the effective start and end dates (p_start_date_active, p_end_date_active).
• LOCK_ROW — Selects the target row FOR UPDATE to obtain a pessimistic lock, accepting the rowid and all business columns. This is typically called before an update to guarantee that the row has not been changed by another session since it was queried.
• UPDATE_ROW — Updates the mutable columns of an existing row identified by its rowid, using the same parameter set as LOCK_ROW (map identifier, organization, description, start and end dates).
• DELETE_ROW — Removes the row identified by the supplied rowid. It takes only x_rowid, since no attribute values are required to locate the target record.

The consistent parameter naming (p_ prefix for IN parameters, x_ prefix for the ROWID) and the lock/update/delete grouping are hallmarks of Oracle Forms-generated or Forms-supporting table handler packages.

Tables Accessed

The single documented table referenced by this package is IGW_ORG_MAPS_ALL, accessed through an APPS synonym. All four procedures operate against this one table:

• INSERT_ROW writes a new mapping record, populating the map identifier, organization, description, and active date range.
• LOCK_ROW reads and locks an existing record for subsequent update.
• UPDATE_ROW modifies the describable and date-range attributes of an existing mapping.
• DELETE_ROW physically removes a mapping record.

The effective-dated columns indicate that organization map records follow the standard Oracle date-tracked pattern, allowing historical and future-dated mappings to coexist for the same map identifier.

Usage Notes

Because this package is a table handler rather than a business-rule API, it is most commonly invoked by the Oracle Forms user interface that maintains organization maps, and potentially by concurrent programs or batch loads that need to create or maintain mapping definitions. The presence of a LOCK_ROW procedure strongly suggests a Forms framework in which the block-level lock, insert, update, and delete events delegate to these procedures. No other documented package references IGW_ORG_MAPS_ALL_PKG, so its callers are presumably Forms modules or external custom code rather than other PL/SQL packages.

Developers integrating with this object should note the AUTHID CURRENT_USER declaration and ensure any calling schema holds appropriate privileges on IGW_ORG_MAPS_ALL. Direct invocation from custom code should generally be limited to controlled data-migration or interface scenarios, since the package performs no validation beyond what the table constraints enforce and does not raise application-level business errors. For grant and project organization map maintenance, supported functionality should be reached through the standard application forms wherever possible.