Search Results copy_control_item

Overview

APPS.PA_COPY_CHANGE_DOC_PVT is a private PL/SQL package body in Oracle EBS Projects (PA) that supports the copying of control item change documentation — that is, the versioning, duplication, and comment management of project control items. Control items (rows in PA_CONTROL_ITEMS) represent change documents, budget/scope changes, and similar controlled project events, and each may carry a version number and associated comments. This package encapsulates the logic required to create a new version copy of an existing control item, propagate the related action rows, supplier details, impact/usage information, and object relationships, and maintain the comment history. It is classified as PVT (private), meaning it is an internal implementation package not intended to be called directly by external APIs; it is exposed to users through the Projects change-management UI and concurrent processes.

The user search term "copy_control_item" corresponds to the internal COPY_CONTROL_ITEM procedure that appears in the package body source (PACICCDB.pls). Although the ETRM-documented procedure list for 12.2.2 names COPY_CHANGE_DOC and UPDATE_COMMENTS, COPY_CONTROL_ITEM is the private helper that performs the core control-item duplication logic within the change-document copy operation.

Key Procedures and Functions

• COPY_CHANGE_DOC — The main documented entry point. It duplicates a change document (control item) into a new version, returning the new control item identifier, version number, and standard API return status/message outputs. It orchestrates the copy of dependent records such as actions, supplier details, impact/usage rows, and object relationships.
• UPDATE_COMMENTS — Updates comment records associated with a control item, writing to PA_CI_COMMENTS so that version comments and change-document remarks remain consistent across the source and copied versions.
• COPY_CONTROL_ITEM (private helper) — Declared in the package body to carry out the low-level copy: it reads the source row from PA_CONTROL_ITEMS by CI_ID, iterates the associated PA_CI_ACTIONS rows, resolves object relationships (relationship type 'CI_INCLUDED_ITEM'), and returns the new CI_ID and version number. It declares exceptions G_EXCEPTION_ERROR and G_EXCEPTION_UNEXPECTED_ERROR for controlled error handling.

Tables Accessed

• PA_CONTROL_ITEMS — The primary source and target of the copy; holds control item identity, CI number, version number, and version comments.
• PA_CI_ACTIONS — Action records tied to a control item, copied so the new version retains the original workflow/action history.
• PA_CI_COMMENTS — Comment records updated by UPDATE_COMMENTS.
• PA_CI_SUPPLIER_DETAILS — Supplier/detail rows associated with the control item, copied to the new version.
• PA_CI_IMPACT_TYPE_USAGE — Defines which impact types are used by the control item, propagated on copy.
• PA_OBJECT_RELATIONSHIPS — Stores the object relationship linking included items; read via the c_obj_id_to1 cursor and written for the new version.
• PA_BUDGET_VERSIONS — Referenced to associate budget version information with the copied control item.
• PA_PROJECT_STATUSES — Used to validate project status context during the copy.

Usage Notes

PA_COPY_CHANGE_DOC_PVT is a private package and is not documented as being referenced by any other package. It is normally invoked indirectly from Oracle Projects change-management forms and concurrent programs when a user copies or versions a change document/control item. Customizations should avoid calling it directly; the supported integration path is through the public change-document APIs and the standard Projects UI. Because it manipulates version numbers and relationship records directly, any custom invocation must respect the same commit and validation sequencing (returned via x_return_status, x_msg_count, and x_msg_data) to keep control item versions and included-item relationships consistent.