Search Results work_request_id

Overview

WIP_EAM_WORK_REQUESTS is an Oracle Work in Process (WIP) table that stores work request header information within the Enterprise Asset Management (EAM) work request flow. A work request represents a maintenance need, repair notification, or service request raised against an asset or maintenance object before it is approved and converted into an actual EAM work order or discrete job. The table resides in the WIP schema and is valid across Oracle EBS 12.1.1 and 12.2.2.

The heuristic Data Vault classification mined from the foreign key structure is satellite-leaning. In Data Vault modeling terms, this suggests treating WIP_EAM_WORK_REQUESTS primarily as a descriptive satellite attached to a maintenance-object or work-entity hub, rather than as a pure transactional hub or a many-to-many link. The classification reflects its relatively low dependency depth and its role in holding descriptive and status attributes about a work request.

Key Information Stored

The table contains 45 documented columns. The most important are:

• WORK_REQUEST_ID — Surrogate primary key defined by WIP_EAM_WORK_REQUESTS_PK and reinforced by unique index WIP_EAM_WORK_REQUESTS_U2. It uniquely identifies each work request and is the internal join key to dependent tables.
• WORK_REQUEST_NUMBER — Business-key candidate, enforced by unique index WIP_EAM_WORK_REQUESTS_U1. This is the user-facing work request number.
• ASSET_NUMBER and ASSET_GROUP — Identify the asset against which the work request is raised; ASSET_NUMBER participates in a foreign key to MTL_SERIAL_NUMBERS.
• ORGANIZATION_ID — The inventory organization context for the work request.
• WIP_ENTITY_ID — Foreign key to WIP_DISCRETE_JOBS, linking the request to its resulting work order or discrete job once approved.
• WORK_REQUEST_STATUS_ID, WORK_REQUEST_PRIORITY_ID, WORK_REQUEST_TYPE_ID — Reference identifiers for status, priority, and type of the request.
• EXPECTED_RESOLUTION_DATE — Target date by which the maintenance is expected to be completed.
• WORK_REQUEST_OWNING_DEPT — The department that owns or is responsible for the request.
• MAINTENANCE_OBJECT_TYPE and MAINTENANCE_OBJECT_ID — Identify the maintenance object associated with the request.
• DESCRIPTION — Free-text description of the work requested.
• WORK_REQUEST_CREATED_BY, CREATED_FOR, E_MAIL, PHONE_NUMBER, CONTACT_PREFERENCE, NOTIFY_ORIGINATOR — Originator and contact attributes used for notification.
• WF_ITEM_TYPE and WF_ITEM_KEY — Workflow identifiers supporting the Oracle Workflow process tied to the request.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — The standard DFF flexfield columns.
• Standard Who columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical reports include open work requests by asset, aged work requests past the expected resolution date, and requests awaiting conversion to work orders.

• Join to WIP_DISCRETE_JOBS on WIP_ENTITY_ID to report which requests have been converted into discrete jobs.
• Join to MTL_SERIAL_NUMBERS via ASSET_NUMBER, ASSET_GROUP, and ORGANIZATION_ID to report asset details.
• Join to WIP_EAM_WORK_REQ_NOTES on WORK_REQUEST_ID to retrieve notes and multi-row descriptive details attached to a request.
• Filter by WORK_REQUEST_STATUS_ID to segregate open versus closed requests.

Sample pattern:

SELECT wr.WORK_REQUEST_NUMBER, wr.ASSET_NUMBER, wr.EXPECTED_RESOLUTION_DATE
FROM WIP.WIP_EAM_WORK_REQUESTS wr
WHERE wr.WORK_REQUEST_STATUS_ID = :status_id
AND wr.EXPECTED_RESOLUTION_DATE < SYSDATE;

Related Objects

• MTL_SERIAL_NUMBERS — Referenced by ASSET_NUMBER, ASSET_GROUP, and ORGANIZATION_ID.
• WIP_DISCRETE_JOBS — Referenced by WIP_ENTITY_ID; holds the resulting discrete job.
• WIP_EAM_WORK_REQ_NOTES — Child table referencing WIP_EAM_WORK_REQUESTS.WORK_REQUEST_ID.
• EAM_WORK_ORDER_BILLS — References WIP_EAM_WORK_REQUESTS.WORK_REQUEST_ID for material requirements.
• Oracle Workflow (WF_ITEM_TYPE, WF_ITEM_KEY) supports approval routing of work requests.