Search Results eng_attachment_changes_u1

Overview

ENG.ENG_ATTACHMENT_CHANGES is a transactional table in the Oracle E-Business Suite Engineering (ENG) schema that stores attachment-related changes associated with engineering change management activities. It functions as the audit and staging ledger for file attachments — documents, drawings, and reference material — attached to revised items within an Engineering Change Order (ECO) or similar change document. Each row captures a single attachment action (add, modify, or delete) and preserves both the source and destination states of the attachment, including media identifiers, version labels, paths, filenames, categories, and workflow status. This dual-state design allows the application to reconstruct the before-and-after condition of an attachment as it moves through the change workflow.

The table resides in the APPS_TS_TX_DATA tablespace with PCTFREE 10 and is indexed in APPS_TS_TX_IDX. Because it is classified as standalone from a Data Vault modeling perspective — having only two documented foreign key relationships and no downstream dependents — it is best modeled as a satellite-like record: a descriptive, event-oriented store keyed by its own surrogate identifier, with limited hub/link connectivity in the surrounding data model.

Key Information Stored

The table contains 36 documented columns. The most significant are summarized below.

• CHANGE_DOCUMENT_ID — The document internal identifier and the sole unique business key, enforced by unique index ENG_ATTACHMENT_CHANGES_U1. It is the candidate surrogate key for downstream joins and de-duplication.
• CHANGE_ID and REVISED_ITEM_SEQUENCE_ID — Identify the parent change and the specific revised item to which the attachment change belongs. Indexed together in ENG_ATTACHMENT_CHANGES_N1.
• ATTACHMENT_ID — The attachment's internal identifier (indexed by ENG_ATTACHMENT_CHANGES_N2 and N3 alongside repository/media keys).
• ACTION_TYPE — The action performed: add, modify, or delete.
• FILE_NAME, NEW_FILE_NAME, SOURCE_PATH, DEST_PATH — The original and revised filenames and storage paths.
• SOURCE_MEDIA_ID, DEST_MEDIA_ID, REPOSITORY_ID — Media and repository identifiers that locate the physical file in the attachment repository. Indexed by ENG_ATTACHMENT_CHANGES_N2.
• SOURCE_VERSION_LABEL and DEST_VERSION_LABEL — Version labels for the old and new attachment states.
• CATEGORY_ID and NEW_CATEGORY_ID — Attachment category classification before and after the change.
• PREVIOUS_STATUS — The prior workflow status of the attachment, useful for approval and audit trails.
• ATTACHED_USER_ID — The user associated with the attachment action.
• SOURCE_DOCUMENT_ID and DEST_DOCUMENT_ID — Document references on each side of the change; SOURCE_DOCUMENT_ID is indexed by ENG_ATTACHMENT_CHANGES_N4.
• Standard WHO columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN provide the standard audit and concurrency trail.

Common Use Cases and Queries

Typical reporting scenarios include auditing attachment modifications on a change, reconciling repository media moves, and confirming which attachments were introduced or removed for a given revised item.

• Change audit trail: SELECT CHANGE_ID, REVISED_ITEM_SEQUENCE_ID, ACTION_TYPE, FILE_NAME, CREATED_BY, CREATION_DATE FROM ENG.ENG_ATTACHMENT_CHANGES WHERE CHANGE_ID = :p_change_id ORDER BY CREATION_DATE;
• Attachment history for a specific attachment: SELECT ACTION_TYPE, SOURCE_VERSION_LABEL, DEST_VERSION_LABEL, SOURCE_PATH, DEST_PATH FROM ENG.ENG_ATTACHMENT_CHANGES WHERE ATTACHMENT_ID = :p_attachment_id;
• Repository movement report grouped by media: SELECT REPOSITORY_ID, SOURCE_MEDIA_ID, DEST_MEDIA_ID, COUNT(*) FROM ENG.ENG_ATTACHMENT_CHANGES GROUP BY REPOSITORY_ID, SOURCE_MEDIA_ID, DEST_MEDIA_ID;
• Deletes-only review: SELECT CHANGE_DOCUMENT_ID, CHANGE_ID, FILE_NAME, LAST_UPDATED_BY FROM ENG.ENG_ATTACHMENT_CHANGES WHERE ACTION_TYPE = 'DELETE';

Because ACTION_TYPE and timestamp columns are not indexed, high-volume audits should filter first by CHANGE_ID or ATTACHMENT_ID to leverage the existing non-unique indexes.

Related Objects

• ENG.ENG_REVISED_ITEMS — Joined on REVISED_ITEM_SEQUENCE_ID to link attachment changes to the revised item under ECO control.
• AS_CONTACT_FAMILY — Joined on FAMILY_ID for family-level attachment context.
• FND_ATTACHED_DOCUMENTS / FND_DOCUMENTS — Standard EBS attachment framework tables that resolve ATTACHMENT_ID references to the underlying document and datatype.
• FND_DOC_CATEGORIES — Resolves CATEGORY_ID and NEW_CATEGORY_ID to attachment category names.
• ENG_ECO_LINE_REVISED_ITEMS / ENG_CHANGE_ORDER_REVISED_ITEMS — Parent structures providing ECO context for the CHANGE_ID.
• FND_LOBS / FND_DOCUMENTS_TL — Storage and translated-name lookup for the physical media referenced by SOURCE_MEDIA_ID and DEST_MEDIA_ID.