Results for “pa_r_project_resources_pub”

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

Overview

PA_R_PROJECT_RESOURCES_PUB is a public PL/SQL package owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the Oracle Projects (PA) family of modules and provides the application programming interface through which project resources are created and registered inside the Projects resource repository. A "resource" in this context is an entity — typically an employee, contingent worker, or other organizational resource defined in Oracle Human Resources or Oracle Resource Manager — that can be assigned to project work, used within project planning, or recorded against project transactions.

The package follows the standard Oracle EBS public/private (PUB/PVT) design pattern. PA_R_PROJECT_RESOURCES_PUB exposes the supported, externally callable entry points, while the companion package PA_R_PROJECT_RESOURCES_PVT encapsulates the private implementation logic and performs the actual DML against the underlying base tables. The PUB package therefore forms the sanctioned boundary that other Oracle Projects components, and customer extensions, are expected to call rather than touching resource tables directly. Keeping all resource creation behind this API preserves the integrity of project resource records, enforces validations and defaults, and ensures consistent audited behavior across integrated modules.

Key Procedures and Functions

The documented ETRM metadata identifies a single public program unit on this package:

• CREATE_RESOURCE — The public procedure used to create a project resource record. It accepts the caller-supplied attributes describing the resource and inserts the corresponding row into the Projects resource repository, coordinating the related extension and transaction-attribute details. Because the ETRM extract does not publish the formal parameter list, consult the package specification in the target instance for the authoritative signature before coding against it.

All additional resource-related logic resides in PA_R_PROJECT_RESOURCES_PVT. The PUB package should be treated as the only supported interface; direct invocation of the PVT layer is not recommended for customer use.

Tables Accessed

The package references the following tables through APPS synonyms:

• PA_RESOURCES — The core Projects resource table. CREATE_RESOURCE writes the master resource record here.
• PA_RESOURCE_TXN_ATTRIBUTES — Stores transaction-level attributes associated with a resource. The package maintains these attributes so the resource behaves correctly when used on project transactions.
• JTF_RS_RESOURCE_EXTNS — The Resource Manager extension table holding resource definitions shared across CRM and other resource-aware applications. The package reads from it to validate or derive resource identity when creating the Projects-side record.

These three tables reflect the resource creation path: the resource must already exist in the shared resource repository (JTF_RS_RESOURCE_EXTNS), and the package establishes the corresponding Projects resource entry (PA_RESOURCES) together with its required transaction attributes (PA_RESOURCE_TXN_ATTRIBUTES).

Usage Notes

PA_R_PROJECT_RESOURCES_PUB is an internal Oracle Projects API rather than a user-facing program. It is not exposed through a concurrent program or a form's underlying block by itself; instead it is invoked programmatically by other project components. The documented reverse dependencies show it is referenced by PA_CANDIDATE_PUB, PA_HR_UPDATE_API, PA_HR_UPDATE_PA_ENTITIES, PA_PARCPRJR_XMLP_PKG, PA_PROJECT_PARTIES_PVT, and the PVT companion package, indicating that candidate assignment, HR-driven resource updates, and project party processing all rely on it. Typical invocation patterns include HR or resource synchronization processes that propagate new or changed resources into Projects, and custom extensions that must register a resource before assigning it to a project. Because the package performs inserts and enforces business rules, custom callers should invoke CREATE_RESOURCE inside a properly scoped transaction, handle the raised exceptions, and commit only after the surrounding business process completes successfully. Developers should verify the current specification in the target instance, as parameter details are not published in the ETRM extract.