Search Results create_resource_list_member




Overview
Explore in AI Chat

Overview

PA_CREATE_RESOURCE is a public PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified as an "OTHER" API in the ETRM repository. It provides the canonical programmatic interface for creating and maintaining resource definitions and resource lists used by Oracle Projects. A "resource list" in Oracle Projects is the mechanism by which planners, project managers, and administrators constrain which people, organizations, jobs, or non-labor resources may be assigned to a project or used during planning. The package declares AUTHID CURRENT_USER and pre-populates the standard WHO audit columns (g_last_updated_by, g_last_update_date, g_creation_date, g_created_by, g_last_update_login) from FND_GLOBAL, ensuring that every row it inserts or updates carries consistent audit and login context inherited from the calling session.

The header shows a long maintenance history; the source excerpt reflects version 120.6 dated January 2012, which is the shipping version for both the 12.1.1 and 12.2.2 code lines. Several procedures carry annotations tying them to specific bug fixes (for example, bug 4440895 introduced the NOCOPY hint on OUT parameters, and CBS references 13535688 and 13546557 added the resource class flag and default expenditure type parameters), documenting the package's evolution as the underlying data model expanded.

Key Procedures and Functions

The documented 16 procedures address the full lifecycle of resource lists and their members:

  • CREATE_RESOURCE_LIST — creates a resource list header, including name, description, public flag, group resource type, effective dates, business group, job group, and the resource-list-related flags and defaults noted above. The parameters added by later bug fixes are optional with defaults, preserving backward compatibility for existing callers.
  • CREATE_RESOURCE_GROUP — inserts a member row into a resource list, taking a resource list identifier, group, name, alias, sort order, and display/enabled flags, and optionally returning the generated resource ID, member ID, and a labor-tracking flag.
  • CREATE_RESOURCE_LIST_MEMBER — the lower-level member creation routine used to attach an individual resource to a list.
  • ADD_RESOUCE_LIST_MEMBER (spelled as documented in the metadata) — an alternate member-insertion entry point.
  • CREATE_RESOURCE and CREATE_RESOURCE_TXN_ATTRIBUTE — create the resource row itself and the transaction attributes that determine how the resource behaves on project transactions.
  • CREATE_DEFAULT_RES_LIST and CREATE_PROJ_RESOURCE_LIST — generate default or project-specific resource lists, typically for standard setup and project creation flows.
  • UPDATE_RESOURCE_LIST — modifies an existing list header.
  • DELETE_PLAN_RES_LIST — removes a planning resource list and its associated defaults.
  • CHECK_PL_ALIAS_UNIQUE — validation routine that verifies resource-list alias uniqueness.
  • COPY_RESOURCE_LIST and COPY_RESOURCE_LISTS — duplicate one or many lists, supporting template-driven setup.
  • TRANSLATE_ROW, ADD_LANGUAGE, and LOAD_ROW — multilingual and multiloader support, enabling translated resource-list content and bulk loading from external sources.

Tables Accessed

The package reads and writes the core Projects resource model through APPS synonyms. Header data is stored in PA_RESOURCE_LISTS_S (and its translated table PA_RESOURCE_LISTS_TL, with FND_LANGUAGES used for language validation), while member rows reside in PA_RESOURCE_LIST_MEMBERS and PA_RESOURCE_LIST_MEMBERS_S. Resource definitions are maintained in PA_RESOURCES and PA_RESOURCES_S, with classification supported by PA_RESOURCE_CLASSES_B. Format and planning defaults are held in PA_RESOURCE_FORMATS, PA_PLAN_RL_FORMATS, PA_PLAN_RL_FORMATS_S, and PA_PLAN_RES_DEFAULTS, the latter used principally by the delete and default-list procedures. Transaction attribute behavior is persisted in PA_RESOURCE_TXN_ATTRIBUTES, and a temporary work area, PA_RBS_ELEMENTS_TEMP, supports validation of RBS elements during resource creation.

Usage Notes

The package is invoked primarily from the Oracle Projects resource-list maintenance forms and from concurrent programs that load or copy resource lists across business groups. In custom development it is the supported entry point for programmatic creation of resource lists and their members, and it is referenced by seven other packages, indicating extensive internal reuse by Oracle's own code. Callers should populate the mandatory context (user, login, and responsibility) before invocation so that the WHO columns are written correctly, and must inspect the OUT error code, stage, and stack parameters to detect validation failures.