Results for “lock_control_item”

8 results




Overview
Explore in AI Chat

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

Overview

PA_CONTROL_ITEMS_PUB is a public PL/SQL package in the Oracle E-Business Suite Projects (PA) module that exposes the business logic governing project control items. Control items represent billable or cost-related line definitions associated with a project, and they participate in revenue generation, invoicing, and project costing. The package encapsulates the create, read, update, delete, and lifecycle operations for these records so that forms, concurrent programs, and external integrations do not manipulate the underlying PA_CONTROL_ITEMS table directly. Because it is classified as a PUB (public) API, it is the supported entry point for customers and partners extending or integrating with project control item functionality. The header comment in the package body references version 120.9.12020000.2, indicating a build shipped for the 12.1.1 and 12.2.2 release streams. The user search term lock_control_item corresponds to the LOCK_CONTROL_ITEM procedure, which is the documented routine that manages record-level locking semantics on control items.

Key Procedures and Functions

  • ADD_CONTROL_ITEM — Creates a new control item record for a project, validating the input and inserting into PA_CONTROL_ITEMS.
  • UPDATE_CONTROL_ITEM — Modifies an existing control item, applying changes to the persisted record while enforcing validation rules.
  • DELETE_CONTROL_ITEM — Removes a control item, typically subject to referential and status checks before the physical or logical deletion is performed.
  • INCLUDE_CONTROL_ITEM — Associates or includes a control item within the relevant project context, making it available for downstream billing and costing activity.
  • COPY_CONTROL_ITEM — Duplicates an existing control item onto a target project or structure, supporting template-based setup and mass replication.
  • GET_OBJECT_NAME — Resolves and returns the identifying name of the referenced object, most likely the project or control item description used in messages and forms.
  • LOCK_CONTROL_ITEM — Acquires the locking state for a control item, preventing concurrent modification by other sessions or users until the operation completes. This procedure is the subject of the lock_control_item search and is central to concurrency control.

The package body additionally contains internal helper logic, including getPartyIdFromName, which resolves an owner name to a party identifier by querying HZ_PARTIES and PA_PROJECT_PARTIES for person-type resources, then falling back to PER_ALL_PEOPLE_F for employees.

Tables Accessed

  • PA_CONTROL_ITEMS — The primary transactional table; all add, update, delete, include, copy, and lock operations act on this entity.
  • PA_PROJECT_PARTIES — Supplies project-to-party associations, used to validate owners and project team membership during name resolution.
  • HZ_PARTIES — The Trading Community Architecture (TCA) party registry, queried to match a supplied person name to a party identifier.
  • PER_ALL_PEOPLE_F — The HR employees table, used as a fallback source for owner identification when the TCA lookup returns no rows.

Usage Notes

The package is invoked primarily from the Project Control Items and related Projects forms, where end users add, update, delete, include, and copy control items. Concurrent programs and batch interfaces may call the same procedures to process control item data in bulk. Custom code and integrations should call PA_CONTROL_ITEMS_PUB rather than the base tables, because the procedures apply validation, generate messages through PA_UTILS.Add_Message, and set the standard x_return_status, x_msg_count, and x_msg_data OUT parameters that callers use for error handling. Two other packages reference this API, confirming it is a shared dependency within the Projects suite. Callers should always honor the return status convention and inspect the message stack on failure before proceeding with dependent transactions.