Search Results implement_attachment_change

Overview

ENG_ATTACHMENT_IMPLEMENTATION is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema and associated with Oracle Engineering (ENG) product functionality. Its primary business purpose is to manage the lifecycle of attachment changes and approvals that flow through the engineering change management process. In Oracle EBS, engineering attachments are stored using the common attachment framework (FND_ATTACHED_DOCUMENTS, FND_DOCUMENTS, and related tables), and this package provides the implementation layer that governs how those attachments are created, reviewed, approved, copied, migrated, and deleted in conjunction with engineering change orders and revised items.

The package encapsulates the workflow and approval status logic for attachments. It defines a comprehensive set of seeded constants representing approval statuses (for example, "Not submitted for approval," "Ready for approval," "Approval requested," "Approval rejected," "Approval approved," and process-error or time-out states), runtime workflow status codes such as TIME_OUT and ABORTED, and attachment statuses including SUBMITTED_FOR_APPROVAL, SUBMITTED_FOR_REVIEW, PENDING_CHANGE, APPROVED, REJECTED, and REVIEWED. These constants are referenced throughout the package to drive consistent state transitions. The header comment indicates the source file is ENGUATTB.pls, with a version identifier reflecting maintenance up to 2006.

Key Procedures and Functions

The package exposes eighteen documented procedures and functions. Debugging utilities — OPEN_DEBUG_SESSION, CLOSE_DEBUG_SESSION, and WRITE_DEBUG — support test and diagnostic tracing, writing to a debug log file (eng.chgmt.attachment.log) controlled by global flags. The core functional routines include:

• IMPLEMENT_ATTACHMENT_CHANGE — applies an attachment change, the central driver of the package.
• UPDATE_ATTACHMENT_STATUS — sets the approval/review status of a given attachment.
• GET_ATTACHMENT_STATUS — retrieves the current status of an attachment.
• CANCEL_REVIEW_APPROVAL — terminates an in-progress review or approval.
• COMPLETE_ATTACHMENT_APPROVAL — finalizes approval for an attachment.
• COPY_ATTACHMENT, COPY_ATTACHMENTS_AND_CHANGES, MIGRATE_ATTACHMENT_AND_CHANGE — replicate and migrate attachments and their associated change records.
• DELETE_ATTACHMENTS_AND_CHANGES, DELETE_ATTACHMENTS_FOR_CURR_CO, DELETE_ATTACHMENTS, DELETE_ATTACHMENT, DELETE_CHANGES — remove attachments or changes at varying scopes, including by current change order.
• PROJECT_DELIVERABLE_TRACKING — supports tracking of project deliverables associated with attachments.
• VALIDATE_FLOATING_VERSION — validates floating revision/version handling for attachments.

Tables Accessed

The package reads and writes through APPS synonyms across the attachment, engineering, and item frameworks. Attachment metadata resides in FND_ATTACHED_DOCUMENTS and FND_ATTACHED_DOCUMENTS_S (with FND_DOCUMENTS and FND_DOCUMENTS_TL for document definitions and translations). Engineering change context is provided by ENG_ATTACHMENT_CHANGES, ENG_ENGINEERING_CHANGES, ENG_CHANGE_ORDER_TYPES, and ENG_REVISED_ITEMS. Item and revision data derive from MTL_SYSTEM_ITEMS, MTL_ITEM_REVISIONS_B, and MTL_ITEM_CATALOG_GROUPS_B. Supporting configuration and security objects include DOM_REPOSITORIES, EGO_OBJ_TYPE_LIFECYCLES, FND_OBJECTS, and FND_RESPONSIBILITY. These tables collectively supply attachment storage, change-order linkage, revision validation, repository location, object-type lifecycle rules, and responsibility-based access.

Usage Notes

ENG_ATTACHMENT_IMPLEMENTATION is typically invoked from Oracle Engineering forms, concurrent programs, and workflow activities that manage engineering change orders and attachment approvals. It is also referenced by three other packages, indicating it serves as a shared implementation dependency rather than a standalone end-user API. Custom code integrating with engineering attachments should call these documented procedures rather than manipulating the underlying FND and ENG tables directly, to preserve status consistency and workflow integrity. In Oracle EBS 12.1.1 and 12.2.2 the package remains an internal implementation component; because it is not classified as a public API, callers should treat it as subject to change between releases.