Search Results add_control_item

Overview

PA_CONTROL_ITEMS_PUB is the public PL/SQL API for Oracle Projects control items. Control items represent tracked project issues, action items, change requests, and similar project control entities that are managed against a project and, in many cases, against a specific project object such as a task or a top task. The package provides a consistent, FND_API-compliant interface for creating, modifying, deleting, and managing the lifecycle of these records within the PA_CONTROL_ITEMS table.

The package is classified as a public (PUB) API, meaning it is intended for external invocation by Oracle EBS forms, concurrent programs, and customer-written extensions rather than being restricted to internal package-to-package calls. Because control items are heavily used throughout Project Management and Project Status Reporting, the API enforces validation through FND_API semantics (message list management, validation-only modes, and controlled commit behavior) so that callers can compose multi-step transactions safely.

The user interest in delete_control_item reflects one of the most common administrative operations performed against project control items, typically when a control item has been entered in error or is superseded by another record.

Key Procedures and Functions

The package exposes seven documented procedures and functions:

• ADD_CONTROL_ITEM — Creates a new control item record. It accepts a broad set of attributes covering the control item type, summary, status, owner, classification, reason, associated project and object, dates, description, resolution details, source information, currency and price, and descriptive flexfield attributes.
• UPDATE_CONTROL_ITEM — Modifies an existing control item, allowing the same attribute set to be adjusted after creation.
• DELETE_CONTROL_ITEM — Removes a control item. This is the procedure most frequently sought by users administering project control data.
• INCLUDE_CONTROL_ITEM — Associates or exposes a control item within a particular context, supporting the inclusion of existing control items in a project or reporting scope.
• COPY_CONTROL_ITEM — Duplicates an existing control item, providing a basis for creating similar items without re-entering all attributes.
• GET_OBJECT_NAME — Retrieves the name of the project object associated with a control item, supporting display and reporting needs.
• LOCK_CONTROL_ITEM — Obtains a lock on a control item record, typically used to serialize concurrent updates in interactive or batch processing.

Tables Accessed

The package operates on the following tables through APPS synonyms:

• PA_CONTROL_ITEMS — The primary table storing control item records; all create, update, and delete operations target this table.
• PA_PROJECT_PARTIES — Used to validate and resolve project party relationships, particularly for owner and responsibility assignments.
• PER_ALL_PEOPLE_F — Used to resolve person identifiers for owners, including the owner name derived from the owner identifier.
• HZ_PARTIES — Used to resolve party information for owners and related entities, supporting party-based identification of control item participants.

Usage Notes

PA_CONTROL_ITEMS_PUB is normally invoked from the Project Management and Project Status Reporting forms within Oracle Projects, from concurrent programs that manage project control data, and from custom PL/SQL extensions that need to automate control item maintenance. The package is referenced by two other Oracle packages, confirming its role as a shared service layer.

Callers should observe the standard FND_API conventions: pass a valid API version, control message list initialization through p_init_msg_list, use p_validate_only to perform validation without committing, and set p_commit only when the calling transaction intends to persist. Because the API manipulates PA_CONTROL_ITEMS and related party tables, deletion performed through DELETE_CONTROL_ITEM should be treated as a committed business action and used cautiously in production environments. Custom code should avoid direct DML against the underlying tables and instead route all control item maintenance through this public API to preserve validation and audit integrity.