Results for “pa_resources_s”

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

Overview

PA_CREATE_RESOURCE is an Oracle EBS Projects (PA) schema package body owned by APPS. It provides the core server-side logic for creating and maintaining resource definitions used throughout the Projects suite: resources, resource lists, resource list members, resource groups, resource transaction attributes, and their translatable and language-installation data. The package functions as an internal workhorse rather than a public application programming interface; its API classification recorded in ETRM is OTHER, and it is not referenced by any other database object, though it is itself dependent on a broad set of Projects and Application Object Library components including FND_API, FND_MSG_PUB, FND_PROFILE, PA_GET_RESOURCE, PA_JOB_UTILS, PA_INTERFACE_UTILS_PUB, PA_PLAN_RL_FORMATS_PVT, and PA_RESOURCE_LIST_TBL_PKG.

The immediate relevance to a search on PA_RESOURCE_LIST_MEMBERS_S is that PA_CREATE_RESOURCE is one of the principal packages that writes to the resource list member tables, and it therefore drives the surrogate key generation and the member sequencing that populate PA_RESOURCE_LIST_MEMBERS and its _S (sequence/primary key) companion table. Understanding this package is essential when diagnosing duplicate member rows, gaps in member IDs, or mismatches between a resource list header and its members.

Key Procedures and Functions

ETRM documents sixteen procedures and functions within the package body. These group naturally into four functional areas.

• Resource creation: CREATE_RESOURCE inserts a new resource definition into PA_RESOURCES and its associated transaction attribute rows.
• Resource transaction attributes: CREATE_RESOURCE_TXN_ATTRIBUTE establishes the resource-level transaction attributes required for cost, billing, and cross-charge processing.
• Resource lists: CREATE_RESOURCE_LIST, UPDATE_RESOURCE_LIST, CREATE_DEFAULT_RES_LIST, CREATE_PROJ_RESOURCE_LIST, COPY_RESOURCE_LIST, COPY_RESOURCE_LISTS, and DELETE_PLAN_RES_LIST create, maintain, duplicate, and remove resource list headers, including the planning resource list defaults held in PA_PLAN_RES_DEFAULTS and the plan resource list format rows in PA_PLAN_RL_FORMATS and PA_PLAN_RL_FORMATS_S.
• Resource list members: CREATE_RESOURCE_LIST_MEMBER and ADD_RESOUCE_LIST_MEMBER (the internal spelling retains the documented typographical error) insert member rows into PA_RESOURCE_LIST_MEMBERS and its surrogate key table PA_RESOURCE_LIST_MEMBERS_S. The distinction between the two procedures reflects different calling contexts, such as direct member creation versus addition of a member to an existing list during copy or default generation.
• Resource groups: CREATE_RESOURCE_GROUP builds a resource group definition used for grouping and reporting.
• Validation and utility: CHECK_PL_ALIAS_UNIQUE validates that a planning resource list alias is unique before insertion.
• Language and seed data: ADD_LANGUAGE, TRANSLATE_ROW, and LOAD_ROW support multi-language installation, translation of resource list names and descriptions, and bulk loading of seed resource list data during implementation or patching.

Tables Accessed

The package reads and writes a wide set of Projects tables through APPS synonyms. Core resource tables include PA_RESOURCES and PA_RESOURCES_S (resource definitions and their surrogate keys), PA_RESOURCE_CLASSES_B, PA_RESOURCE_TYPES, and PA_RESOURCE_FORMATS, which define the classification and format attributes of a resource. Resource list structures are held in PA_RESOURCE_LISTS_S, PA_RESOURCE_LISTS_TL (translatable names and descriptions), and PA_RESOURCE_LISTS_ALL_BG, the multi-organization background table. Member-level data resides in PA_RESOURCE_LIST_MEMBERS and PA_RESOURCE_LIST_MEMBERS_S; the latter supplies the sequence-generated primary key for each member row, which is the object referenced in the user's search. Planning list formats and defaults are stored in PA_PLAN_RL_FORMATS, PA_PLAN_RL_FORMATS_S, and PA_PLAN_RES_DEFAULTS. Transaction attributes are written to PA_RESOURCE_TXN_ATTRIBUTES and PA_RESOURCE_TXN_ATTRIBUTES_S. Reference and validation data are read from PA_RESOURCE_GROUPS_VALID_V, PA_RESOURCE_LIST_ASSIGNMENTS_V, PA_EVENT_TYPES_RES_V, PA_EXPENDITURE_TYPES_RES_V, PA_ORGANIZATIONS_RES_V, PA_RESOURCE_TYPES_ACTIVE_V, PA_REVENUE_CATEGORIES_V, and PA_JOBS_V. Language support uses FND_LANGUAGES.

Usage Notes

PA_CREATE_RESOURCE is invoked indirectly by the Projects forms and by concurrent programs that create resources, generate default planning resource lists, or copy resource lists between projects and organizations. Because the package body is not referenced by other database objects, external callers reach it through form-level triggers, workflow, or custom PL/SQL that calls the package directly. When troubleshooting PA_RESOURCE_LIST_MEMBERS_S, verify that member inserts originate from CREATE_RESOURCE_LIST_MEMBER or ADD_RESOUCE_LIST_MEMBER and that the sequence-backed key in the _S table is committed transactionally with the base member row. Copy operations through COPY_RESOURCE_LIST and COPY_RESOURCE_LISTS should be checked for orphaned members if a copy terminates mid-transaction. Language-related procedures, ADD_LANGUAGE, TRANSLATE_ROW, and LOAD_ROW, are normally executed during installation, patching, or translation maintenance, not during routine production use.