Search Results copy_attachments_and_changes

Overview

APPS.ENG_ATTACHMENT_IMPLEMENTATION is an Oracle E-Business Suite PL/SQL package that supports attachment handling within the Oracle Engineering (ENG) module, particularly in the context of engineering change orders and their associated attachment records. The package is declared with AUTHID CURRENT_USER and is owned by APPS, with its source header (ENGUATTS.pls, version 120.7.12010000.2, dated 2010/02/03) indicating it forms part of the Engineering attachment utility layer. Its core business purpose is to manage the lifecycle of attachments linked to engineering changes—creating, copying, migrating, deleting, and validating attachment and change records—while also exposing workflow-oriented status update and approval cancellation routines. The package is referenced by three other packages, confirming it occupies a shared utility role rather than being an isolated component.

Key Procedures and Functions

The package exposes eighteen documented procedures and functions, which can be grouped by purpose:

• Debugging utilities: OPEN_DEBUG_SESSION, CLOSE_DEBUG_SESSION, and WRITE_DEBUG provide test and diagnostic logging, writing to an optional output directory and file name.
• Approval and status handling: CANCEL_REVIEW_APPROVAL cancels a review approval for a given change; UPDATE_ATTACHMENT_STATUS updates attachment workflow and approval status; COMPLETE_ATTACHMENT_APPROVAL finalizes the approval flow; GET_ATTACHMENT_STATUS retrieves current attachment status.
• Migration and implementation: MIGRATE_ATTACHMENT_AND_CHANGE (the procedure associated with the user's search term) migrates attachment and change records; IMPLEMENT_ATTACHMENT_CHANGE applies a change to attachment data.
• Copy operations: COPY_ATTACHMENT copies a single attachment; COPY_ATTACHMENTS_AND_CHANGES copies attachments together with their related change records.
• Deletion operations: DELETE_ATTACHMENTS_AND_CHANGES, DELETE_ATTACHMENTS_FOR_CURR_CO, DELETE_ATTACHMENTS, DELETE_ATTACHMENT, and DELETE_CHANGES remove attachment and change data at varying scopes.
• Validation and tracking: PROJECT_DELIVERABLE_TRACKING and VALIDATE_FLOATING_VERSION support deliverable tracking and version validation for floating (non-fixed) revisions.

Several procedures follow the standard EBS API signature convention, accepting p_api_version, p_init_msg_list, p_commit, p_validation_level, and p_debug parameters and returning x_return_status, x_msg_count, and x_msg_data.

Tables Accessed

The package reads and writes through APPS synonyms across several functional areas. Attachment and document storage is handled via FND_ATTACHED_DOCUMENTS, FND_ATTACHED_DOCUMENTS_S, FND_DOCUMENTS, and FND_DOCUMENTS_TL, which hold the attachment-to-entity links and document metadata; DOM_REPOSITORIES provides underlying repository information. Engineering change data resides in ENG_ENGINEERING_CHANGES, ENG_ATTACHMENT_CHANGES, ENG_CHANGE_ORDER_TYPES, and ENG_REVISED_ITEMS. Item and revision context is drawn from MTL_SYSTEM_ITEMS, MTL_ITEM_REVISIONS_B, and MTL_ITEM_CATALOG_GROUPS_B. Supporting reference data includes FND_OBJECTS, FND_RESPONSIBILITY, and EGO_OBJ_TYPE_LIFECYCLES, the latter used for object-type lifecycle validation.

Usage Notes

ENG_ATTACHMENT_IMPLEMENTATION is typically invoked from Engineering-related forms and concurrent programs rather than called directly by end users. The presence of workflow user and login constants (G_ENG_WF_USER_ID, G_ENG_CP_USER_ID) indicates that both Oracle Workflow and concurrent-manager contexts are supported callers. Custom extensions and integrations that need to migrate or copy attachments alongside engineering changes should call the appropriate procedure through the standard API pattern, passing a valid p_api_version and checking x_return_status before committing. Because the package operates AUTHID CURRENT_USER, callers must ensure the necessary privileges on the referenced objects are granted to the invoking schema.