Search Results delete_rl_uses




Overview
Explore in AI Chat

Overview

PA_RES_LIST_ASSIGNMENTS is a stored PL/SQL package in the APPS schema that supports the Oracle E-Business Suite resource list assignment mechanism within Oracle Projects. Resource lists define groupings of people, organizations, or roles that can be referenced by planning, budgeting, and staffing processes. The package manages the association between a resource list and the projects or resource usages that consume it, providing the programmatic layer used when resource list assignments must be created, retrieved, or removed outside of direct form manipulation.

The package is classified as OTHER in the ETRM repository rather than as a formal public API, and its package and package body both carry a VALID status in the APPS schema. It exists primarily to encapsulate the insert, query, and delete logic against the resource list assignment tables so that multiple internal Oracle Projects components share consistent behavior. Dependency metadata confirms that it is referenced by PA_BUDGET_CORE, PA_FIN_PLAN_PUB, PA_FIN_PLAN_PVT, and GMS_BUDGET_CORE, indicating that budgeting and financial planning functionality within Projects, and budget processing within Grants Management, rely on this package when resolving resource list assignments.

Key Procedures and Functions

The documented interface exposes five procedures, which fall into two functional groups: assignment maintenance and usage maintenance.

  • CREATE_RL_ASSGMT — Creates a resource list assignment record, establishing the link between a resource list and the project or assignment context that will consume it.
  • GET_RL_ASSGMT — Retrieves an existing resource list assignment, typically returning the identifier or attributes needed by a calling process that must validate or reuse an assignment.
  • DELETE_RL_ASSGMT — Removes a resource list assignment, reversing the association created by CREATE_RL_ASSGMT.
  • CREATE_RL_USES — Creates resource list usage records, which capture where and how a resource list is applied.
  • DELETE_RL_USES — Deletes resource list usage records, supporting cleanup when a resource list is no longer applied in a given context.

The separation of assignment and usage operations allows callers to manage the top-level association independently from the finer-grained usage entries, which is consistent with the way resource lists are shared across planning and budgeting scenarios.

Tables Accessed

The package operates against the core resource list tables and supporting project data. PA_RESOURCE_LIST_ASSIGNMENTS and its companion table PA_RESOURCE_LIST_ASSIGNMENTS_S hold the assignment header and description or translation information respectively, and are the primary targets of the create, get, and delete assignment procedures. PA_RESOURCE_LIST_USES stores the usage records manipulated by CREATE_RL_USES and DELETE_RL_USES. PA_PROJECTS_ALL is referenced to validate or resolve the project context associated with an assignment or usage. DUAL is used for standard single-row PL/SQL constructs. All access is performed through APPS synonyms, consistent with the EBS shared schema model.

Usage Notes

PA_RES_LIST_ASSIGNMENTS is an internal utility package rather than a documented public API, and Oracle does not publish parameter signatures for it. It should not be called directly from custom code where a supported public API exists. Its documented consumers are other Oracle Projects and Grants Management packages — PA_BUDGET_CORE, PA_FIN_PLAN_PUB, PA_FIN_PLAN_PVT, and GMS_BUDGET_CORE — which invoke it during budget and financial plan processing. The package also appears in its own dependency list, indicating internal recursion or self-reference within its procedures. In practice, resource list assignments are created and maintained through the Oracle Projects staffing and planning forms; the package executes on behalf of those forms and the budgeting engines rather than being triggered by a standalone concurrent program. When custom extensions must manipulate resource list assignments, developers should prefer supported public APIs and treat this package as reference material for understanding the underlying table operations.