Results for “resource_name”

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

Overview

PA_ALLOC_UTILS is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite, classified under the Other (non-API) category. It provides the internal utility layer that supports the Oracle Projects allocation engine. Its business function is to answer eligibility and validation questions about the allocation configuration: whether a given resource, resource list, project, task, budget type, burden expenditure type, or resource breakdown structure (RBS) element participates in a defined allocation rule or allocation run. In addition, it supplies name-resolution helpers that convert surrogate identifiers into user-readable names for display in allocation setup and inquiry screens. Because it is a supporting utility package rather than a public API, it is invoked by the higher-level allocation packages, concurrent programs, and forms that implement resource allocation across Oracle Projects in releases 12.1.1 and 12.2.2.

Key Procedures and Functions

The package exposes fifteen documented procedures and functions, subdivided by purpose.

• Eligibility predicates. IS_RESOURCE_IN_RULES and IS_RESOURCE_LIST_IN_RULES determine whether a resource or a resource list is referenced by the allocation rules supplied to them. IS_PROJECT_IN_ALLOCATIONS, IS_TASK_IN_ALLOCATIONS, IS_TASK_LOWEST_IN_ALLOCATIONS, IS_BUDGET_TYPE_IN_ALLOCATIONS, and IS_BEM_IN_ALLOCATIONS test whether a project, task, lowest task, budget type, or burden expenditure type (BEM) participates in an allocation definition; the lowest-task variant supports the task hierarchy checks required for task-level allocation.
• RBS validation. IS_RBS_IN_RULES and IS_RBS_ELEMENT_IN_RULES verify whether an RBS structure or a specific RBS element is used by the allocation rules.
• Name resolution. RESOURCE_NAME, RESOURCE_LIST_NAME, GET_CONCATENATED_NAME, GET_RBS_VERSION_NAME, and GET_RESOURCE_NAME_TL return descriptive names and concatenated descriptors for resources, resource lists, and RBS versions, with GET_RESOURCE_NAME_TL retrieving the translated resource name.
• Configuration maintenance. ASSOCIATE_RBS_TO_ALLOC_RULE performs the association of an RBS structure with an allocation rule.

Tables Accessed

The package reads and writes the core tables of the Oracle Projects allocation model. Rule and configuration definitions reside in PA_ALLOC_RULES and PA_ALLOC_RULES_ALL, while the resources eligible for allocation are stored in PA_ALLOC_RESOURCES and the constituent members of named lists in PA_RESOURCE_LIST_MEMBERS. The execution-time tables PA_ALLOC_RUNS_ALL, PA_ALLOC_RUN_BASIS_DET, PA_ALLOC_RUN_SOURCES, PA_ALLOC_RUN_SOURCE_DET, PA_ALLOC_RUN_TARGETS, PA_ALLOC_SOURCE_LINES, PA_ALLOC_TARGET_LINES, and PA_ALLOC_TXN_DETAILS hold run headers, basis detail, source and target definitions, and the generated source, target, and transaction lines produced by an allocation run. RBS structures are read through PA_RBS_ELEMENTS, PA_RBS_ELEMENT_NAMES_TL, and the views PA_RBS_HEADERS_V, PA_RBS_VERSIONS_V, PA_RESOURCE_LISTS_V, and PA_TASKS. FND_API provides the standard API support routines, and DUAL and STANDARD are referenced for scalar operations.

Usage Notes

PA_ALLOC_UTILS is invoked indirectly during allocation setup and execution rather than being called directly by end users. Allocation definition forms use its predicate functions to validate entries on rule, resource, RBS, project, and task fields before saving, and its name functions to render descriptive values in list-of-values and inquiry windows. The allocation generation and run concurrent programs call the same predicates to confirm that each resource, task, and RBS qualifies under the active rule set before processing source and target lines. Custom extensions and client-side code that must replicate allocation eligibility logic may call these functions, but because the package is not a public API, its signatures are not guaranteed across patches and should be treated as internal. Oracle documentation indicates it is referenced by numerous other packages within the allocation subsystem and does not itself appear in the dependency lists of unrelated modules.