Search Results wip_eam_work_req_notes_u1

Overview

WIP.WIP_EAM_WORK_REQ_NOTES is a transactional table in the Oracle E-Business Suite Work in Process (WIP) schema that stores the change history and audit trail for individual Enterprise Asset Management (EAM) work requests. When a maintenance planner or technician creates a work request, a brief description of the problem is entered and persisted here. Subsequent updates that add detail or clarify the reported problem are also captured as additional rows, giving the table a chronological, append-style character rather than a single mutable record per request.

From a data-modeling perspective, the heuristic Data Vault classification for this object is satellite-leaning. The table does not carry its own independent business identity beyond the surrogate note identifier; instead it qualifies a parent work request with descriptive, time-stamped attributes. This makes it most naturally modeled as a satellite hanging off a work request hub, with WORK_REQUEST_ID acting as the link back to the driving business key.

The object is registered as VALID in both Oracle EBS 12.1.1 and 12.2.2, with FND Design Data entry WIP.WIP_EAM_WORK_REQ_NOTES. Storage defaults place it in the APPS_TS_TX_DATA tablespace with PCT FREE of 10.

Key Information Stored

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

• WORK_REQUEST_NOTE_ID — Surrogate primary key (NUMBER). This is the unique system-generated request note identifier and is the column underpinning the unique index WIP_EAM_WORK_REQ_NOTES_U1. It is the documented business-key candidate for uniqueness purposes.
• WORK_REQUEST_ID — Foreign key reference linking the note to its parent work request in WIP_EAM_WORK_REQUESTS. A single work request may accumulate many note rows.
• NOTES — VARCHAR2(2000) holding the detailed note text for the work request, including the original problem description and later clarifying updates.
• WORK_REQUEST_NOTE_TYPE — NUMBER indicating whether the note originated from a user entry or was generated by a workflow process.
• NOTIFICATION_ID — Identifier of the workflow process that created the note, populated when the note is system-generated.
• Standard Who columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN provide the audit stamps used for change-history reconstruction and row-level provenance.

Common Use Cases and Queries

The primary use case is auditing the progression of a work request from initial report through resolution. The non-unique index WIP_EAM_WORK_REQ_NOTES_N1 on (WORK_REQUEST_ID, CREATION_DATE) supports ordering notes chronologically within a request, which is the canonical retrieval pattern.

Typical reporting queries include extracting the full note history for a given request:

• SELECT WORK_REQUEST_ID, CREATION_DATE, NOTES FROM WIP.WIP_EAM_WORK_REQ_NOTES WHERE WORK_REQUEST_ID = :request_id ORDER BY CREATION_DATE;
• Joining to WIP_EAM_WORK_REQUESTS to correlate notes with work request attributes such as status, asset, and priority.
• Filtering on WORK_REQUEST_NOTE_TYPE to distinguish user-authored notes from workflow-generated notifications.
• Isolating notes linked to a specific NOTIFICATION_ID when tracing a workflow-driven update.

The table also supports operational dashboards showing note volume per request, aging of unresolved problems, and audit reports required for maintenance compliance.

Related Objects

The most significant relationship is to the parent work request:

• WIP.WIP_EAM_WORK_REQUESTS — Joined on WORK_REQUEST_ID = WORK_REQUEST_ID. This is the foreign key documented for this table and the principal parent in the relationship chain.
• WIP.WIP_EAM_WORK_REQ_NOTES# — The underlying base object referenced in the dependency listing.

The EAM work request family and its related maintenance objects — work orders, asset definitions, and workflow notification entities referenced through NOTIFICATION_ID — complete the surrounding model. Together these objects let implementers reconstruct the full lifecycle narrative of an asset maintenance request from first report to final disposition.