Search Results insert_row1

Overview

APPS.PA_RESOURCE_PKG is a PL/SQL package body within the Oracle E-Business Suite Projects (PA) module whose header identifies it by the RCS revision string PARCTBHB.pls 120.1. The package encapsulates the low-level maintenance of project resource definitions, notably the physical insertion of rows into the PA_RESOURCES base table and its associated dependent tables. In the Oracle Projects data model, a "resource" represents an entity that can perform work and against which project transactions, assignments, and budgets can be recorded — for example labor resources, organizations, and non-labor or miscellaneous resources. Because PA_RESOURCES is referenced extensively by transaction, budgeting, and assignment logic, direct DML against it from forms or custom code is undesirable. PA_RESOURCE_PKG provides the sanctioned insertion path, preserving the integrity of the resource definition model across the ETRM 12.1.1 and 12.2.2 code lines. The ETRM repository classifies the package with an API classification of OTHER, indicating that it is an internal implementation utility rather than a formally published public API.

Key Procedures and Functions

Two procedures are documented in the ETRM repository for this package body, and the embedded source comments describe a third companion routine. All three are oriented toward inserting resource-related rows on behalf of the calling layer.

• INSERT_ROW1 — This is the object of the user's search and the primary documented procedure. Per the in-source comment, INSERT_ROW1 inserts a new row into the PA_RESOURCES table, effectively creating the resource definition itself. Its parameter signature, visible in the excerpt, includes the resource identifier and name, the resource type, an associated JTF resource identifier, active date range columns, standard Oracle Applications WHO/audit columns (request ID, program ID, program update date, program application ID, last update and creation audit fields), and two feature-gated flags added by later bug fixes: unit of measure (bug 2599790), and ROLLUP_QUANTITY_FLAG plus TRACK_AS_LABOR_FLAG (bug 3921534). The procedure returns the inserted row's ROWID through an OUT NOCOPY parameter and signals outcome through an OUT NOCOPY RETURN_STATUS parameter initialized to FND_API.G_RET_STS_SUCCESS. It also declares a private cursor to retrieve the ROWID for the newly inserted RESOURCE_ID.
• INSERT_ROW2 — Documented in the ETRM repository as the second procedure of the package. According to the source comment header, INSERT_ROW2 inserts into the PA_RESOURCE_TXN_ATTRIBUTES table, which holds transaction-related attribute configuration for a resource.

The source comment additionally references INSERT_ROW3, which inserts into PA_RESOURCE_OU to associate a resource with an operating unit. INSERT_ROW3 is not enumerated in the documented procedure list provided by ETRM, so it should be treated as an internal or undocumented companion routine.

Tables Accessed

The ETRM metadata records two tables referenced through APPS synonyms: PA_RESOURCES and PA_RESOURCE_TXN_ATTRIBUTES.

• PA_RESOURCES — The master resource definition table. INSERT_ROW1 writes a new resource row here, supplying the resource ID, name, description (added for bug 4318765), resource type, JTF resource reference, active dates, unit of measure, rollup quantity and track-as-labor flags, and audit columns. The procedure also reads PA_RESOURCES through its private cursor to obtain the generated ROWID.
• PA_RESOURCE_TXN_ATTRIBUTES — The dependent table holding resource-level transaction attributes. INSERT_ROW2 populates this table to complete the resource setup.

The source comment header names PA_RESOURCE_OU as a third target, populated by INSERT_ROW3 for operating unit association. This table is not listed in the ETRM table metadata but is clearly part of the same write pattern.

Usage Notes

PA_RESOURCE_PKG is invoked as an internal insert handler rather than through a published interface. Its structure — a ROWID OUT parameter, an FND_API return status, and an explicit duplicate-ID check variable — is characteristic of a Forms-generated or Forms-supporting PL/SQL package, where the Oracle Forms transaction layer requires the ROWID of a newly inserted record to maintain block state. This pattern explains the OUT NOCOPY conventions and the File.Sql.39 annotation (bug 4440895) that governs them.

In practice the package is called when a resource definition is created or extended: from Oracle Projects setup or administration forms covering resource and resource type maintenance, from concurrent programs performing bulk resource loading, and from custom code that must insert PA_RESOURCES rows without violating the model's dependent-table expectations. Callers must supply the full audit parameter set and should insert the base row through INSERT_ROW1 before populating PA_RESOURCE_TXN_ATTRIBUTES via INSERT_ROW2 and the operating unit mapping via INSERT_ROW3. Because ETRM classifies the package as OTHER and lists only INSERT_ROW1 and INSERT_ROW2, the package should be regarded as a restricted internal API: customizations should prefer it over direct DML against PA_RESOURCES, but should not assume the same backward-compatibility guarantees extended to formally published Oracle Projects APIs. Only one other package references this unit, underscoring its narrow, implementation-level role.