Search Results eng_attachment_changes

Overview

ENG_ATTACHMENT_CHANGES is an Engineering (ENG) module table in the Oracle E-Business Suite 12.1.1 and 12.2.2 environments that stores attachment-related changes recorded against revised engineering items. It functions as the transactional log for attachment operations on Engineering Change Orders (ECOs) and revised items, capturing actions such as adding, replacing, deleting, or modifying file attachments and their associated metadata (file names, descriptions, categories, and repository attributes).

The table resides in the ENG schema and is documented as VALID in ETRM 12.2.2 with 36 physical columns and a single unique index, ENG_ATTACHMENT_CHANGES_U1, on CHANGE_DOCUMENT_ID. The ETRM Data Vault classification heuristic returns "standalone," meaning the FK structure does not strongly bind this table into a dimensional hub/link/satellite topology; it behaves as an independent change-audit table. Where a Data Vault model is desired, this object is best treated as a satellite-like change log keyed by its own surrogate, with CHANGE_DOCUMENT_ID as the natural business key candidate.

Key Information Stored

Notable columns include the following:

• CHANGE_ID — Surrogate identifier for the attachment change record; the primary key of the underlying table.
• CHANGE_DOCUMENT_ID — Business-key candidate, enforced by unique index ENG_ATTACHMENT_CHANGES_U1; identifies the change document associated with the attachment revision.
• REVISED_ITEM_SEQUENCE_ID — FK to ENG_REVISED_ITEMS; links the attachment change to the specific revised item sequence of the ECO.
• ATTACHMENT_ID — Identifier of the attachment entity affected by the change.
• ACTION_TYPE — Code indicating the nature of the change (e.g., add, replace, delete).
• FILE_NAME / NEW_FILE_NAME — Original and updated file names, capturing rename or file-swap operations.
• SOURCE_PATH / DEST_PATH — Source and destination file paths, documenting movement of the attached file.
• CATEGORY_ID / NEW_CATEGORY_ID — Original and revised attachment category, tracking reclassification.
• DESCRIPTION / NEW_DESCRIPTION — Original and revised attachment descriptions.
• ATTACHED_USER_ID — User who performed or owns the attachment change.
• PREVIOUS_STATUS — Prior status of the attachment before the change.
• FAMILY_ID — FK to AS_CONTACT_FAMILY; associates the change with a contact family record.
• REPOSITORY_ID, DM_TYPE, ENTITY_NAME — Metadata linking the attachment to its document repository, document-management type, and entity.
• PK1_VALUE through PK5_VALUE — Generic key values used to associate the attachment with the owning entity in the document repository.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical usage is auditing and reporting on attachment activity within engineering change workflows. Example queries include:

• Listing all attachment changes for a given revised item:
  SELECT change_id, action_type, file_name, new_file_name, attached_user_id, creation_date FROM eng.eng_attachment_changes WHERE revised_item_sequence_id = :seq_id ORDER BY creation_date;
• Auditing renames and reclassifications:
  SELECT change_document_id, file_name, new_file_name, category_id, new_category_id FROM eng.eng_attachment_changes WHERE file_name <> new_file_name OR category_id <> new_category_id;
• User activity reporting:
  SELECT attached_user_id, COUNT(*) FROM eng.eng_attachment_changes GROUP BY attached_user_id;
• Joining to ENG_REVISED_ITEMS to enrich with ECO context.

Related Objects

• ENG_REVISED_ITEMS — joined on ENG_ATTACHMENT_CHANGES.REVISED_ITEM_SEQUENCE_ID = ENG_REVISED_ITEMS.SEQUENCE_ID.
• AS_CONTACT_FAMILY — joined on ENG_ATTACHMENT_CHANGES.FAMILY_ID = AS_CONTACT_FAMILY.FAMILY_ID.
• FND_ATTACHED_DOCUMENTS / FND_DOCUMENTS — attachment framework tables linked via ATTACHMENT_ID.
• ENG_ECO_DEFINITIONS / ENG_CHANGE_ORDERS — ECO context for the associated change document.
• FND_USER — references ATTACHED_USER_ID, CREATED_BY, and LAST_UPDATED_BY for user attribution.