Search Results init_update_members

Overview

PA_RESOURCE_PUB is a public PL/SQL package in the Oracle Projects (PA) module of Oracle E-Business Suite. Its declared purpose, as reflected in the header annotation, is to allow customers to export resource lists and the individual resources those lists contain into Oracle Projects. In Oracle Projects terminology, a resource list is a named grouping of planning resources—people, organizations, jobs, or other resource types—used during project planning, budgeting, and forecasting.

The package is defined with AUTHID DEFINER and carries an API version constant of 1.0. Its display name in the repository is "Create Resources," and its compatibility is rated as "S" (supported), with a public scope and an active lifecycle. It is classified under the business entities PA_PROJ_PLANNING_RESOURCE and PA_BUDGET, and it is documented in the Oracle Projects API's, Client Extensions, and Open Interfaces Reference (120pjapi.pdf). The package follows the standard Oracle Projects interface pattern: header records are identified by the code 'LIST' and line records by the code 'MEMBER'. Missing values in the record structures are initialized with sentinel constants from PA_INTERFACE_UTILS_PUB.

Key Procedures and Functions

The package exposes 22 documented procedures and functions, organized around the create, update, and delete lifecycles of resource lists and their members.

• CREATE_RESOURCE_LIST — Creates a resource list, together with its descriptive attributes and membership, from the supplied interface data.
• EXEC_CREATE_RESOURCE_LIST — Executes the creation process for a resource list, typically acting as the entry point that drives the load and validation steps.
• INIT_CREATE_RESOURCE_LIST and CLEAR_CREATE_RESOURCE_LIST — Initialize and subsequently reset the package's global/interface state for a create operation.
• LOAD_RESOURCE_LIST and LOAD_MEMBERS — Load the resource list header and its member (line) records into the interface tables.
• PROCESS_MEMBERS — Validates and processes the resource list member records.
• FETCH_RESOURCE_LIST and FETCH_MEMBERS — Retrieve header and member information for a resource list.
• UPDATE_RESOURCE_LIST, INIT_UPDATE_MEMBERS, EXEC_UPDATE_RESOURCE_LIST, and CLEAR_UPDATE_MEMBERS — Support the update lifecycle for a resource list and its member set.
• DELETE_RESOURCE_LIST — Deletes a resource list.
• ADD_RESOURCE_LIST_MEMBER, UPDATE_RESOURCE_LIST_MEMBER, and DELETE_RESOURCE_LIST_MEMBER — Manage individual membership within a list.
• SORT_RESOURCE_LIST_MEMBERS — Orders the members of a resource list.
• CONVERT_LIST_NAME_TO_ID and CONVERT_ALIAS_TO_ID — Resolve a list name or an alias to its internal identifier.

Tables Accessed

The package operates through APPS synonyms against the core Oracle Projects resource tables. PA_RESOURCE_LISTS_ALL_BG stores the resource list header (name, group resource type, start and end dates, and related attributes). PA_RESOURCE_LIST_MEMBERS stores the individual member rows belonging to each list. PA_RESOURCES holds the underlying resource definitions referenced by list members, and PA_RESOURCE_TYPES provides the resource type classifications used when creating or validating lists. The package also references DBMS_SQL for dynamic SQL and PLITBLM for PL/SQL index-by table handling, which support bulk processing of member data.

Usage Notes

PA_RESOURCE_PUB is a public API typically invoked from custom PL/SQL integration code, data-conversion scripts, or Oracle Projects forms and concurrent programs that need to create or maintain resource lists programmatically. Because the packaged procedures handle header and line data through the 'LIST' and 'MEMBER' interface conventions, callers are expected to load and process resource list data in the prescribed sequence. The "exec_create_resource_list" search term corresponds directly to the EXEC_CREATE_RESOURCE_LIST procedure, which is the execution step of the create transaction. As a public, versioned package documented in the Oracle Projects open interfaces reference and referenced by three other packages, it is intended for supported extension use; developers should observe the standard initialize, load, execute, and clear pattern when building integrations.