Search Results wip_eam_work_requests_u2

Overview

WIP.WIP_EAM_WORK_REQUESTS is a core transactional table within the Oracle E-Business Suite Enterprise Asset Management (EAM) module. It stores header-level work request information generated in a maintenance organization, capturing the attributes that describe an incoming maintenance demand — priority, requesting party, owning department, expected resolution date, and the asset against which the request is raised. The table sits at the front end of the EAM maintenance lifecycle: work requests are reviewed, approved, and subsequently converted into work orders (discrete jobs) that drive execution. Detailed narrative text associated with each request — the actual problem description and supporting notes — is not held here but in WIP_EAM_WORK_REQ_NOTES, which keeps the header table narrow and the notes table unbounded in size.

In Data Vault terms, the documented FK topology suggests this object behaves as a satellite-leaning entity. Its unique keys (WIP_EAM_WORK_REQUESTS_U1 and U2) and multiple descriptive, mutable attributes make it a natural candidate for a satellite hanging off a work request hub, with foreign-key references to assets and work orders modeled as links. This classification is a modeling suggestion derived from the constraint structure, not a physical design fact.

Key Information Stored

The table is physically owned by WIP, resides in the APPS_TS_TX_DATA tablespace with PCTFREE 10, and contains 45 documented columns in the 12.2.2 schema. The most significant are:

• WORK_REQUEST_ID — surrogate primary key (WIP_EAM_WORK_REQUESTS_PK) and the target of unique index U2; a system-generated sequence number.
• WORK_REQUEST_NUMBER — the business-facing identifier protected by unique index U1. Currently populated with the same value as WORK_REQUEST_ID, but it remains the human-readable key and the correct join predicate for external reporting.
• ASSET_NUMBER and ASSET_GROUP — the asset against which the request is raised and the group to which that asset belongs; ASSET_NUMBER carries a foreign key to MTL_SERIAL_NUMBERS.
• ORGANIZATION_ID — the maintenance organization that owns the request; a mandatory filtering column for multi-org reporting.
• WORK_REQUEST_STATUS_ID and WORK_REQUEST_PRIORITY_ID — lookups driven by status and priority codes; these determine approval routing and scheduling urgency.
• WORK_REQUEST_OWNING_DEPT — the department accountable for resolving the request.
• WIP_ENTITY_ID — populated when the request is converted to a work order; foreign key to WIP_DISCRETE_JOBS.
• EXPECTED_RESOLUTION_DATE — the committed completion date against which service levels are measured.
• MAINTENANCE_OBJECT_TYPE and MAINTENANCE_OBJECT_ID — the generalized pointer to the maintained object (asset or rebuild item).
• DESCRIPTION, CREATED_FOR, PHONE_NUMBER, E_MAIL, CONTACT_PREFERENCE — the requester contact block used by notification workflows.
• WF_ITEM_TYPE and WF_ITEM_KEY — the Oracle Workflow linkage used to track approval and notification progress.
• Standard Who columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and the fifteen ATTRIBUTE flex columns support auditing and customer extensions.

Common Use Cases and Queries

Typical reporting includes open work request aging, priority and department workload distribution, and conversion-rate analysis (requests that have acquired a WIP_ENTITY_ID versus those still pending). A representative query joins the header to its notes table and filters by organization and status:

SELECT wr.work_request_number, wr.asset_number, wr.expected_resolution_date
FROM wip.wip_eam_work_requests wr
WHERE wr.organization_id = :org_id
AND wr.work_request_status_id = :status_id
AND wr.last_update_date >= :since_date;

Because nonunique index N3 covers ORGANIZATION_ID and WORK_REQUEST_STATUS_ID, and N4 covers LAST_UPDATE_DATE, the above predicates are served efficiently from the index rather than a full table scan. Index N1 supports asset-oriented searches across ORGANIZATION_ID, ASSET_GROUP, and ASSET_NUMBER. Incremental extracts should always key off LAST_UPDATE_DATE and WORK_REQUEST_ID to remain restartable.

Related Objects

The following objects are the most significant dependencies for joining and integration purposes:

• WIP_EAM_WORK_REQ_NOTES — child table joined on WORK_REQUEST_ID; holds the free-text details of the request.
• EAM_WORK_ORDER_BILLS — references the work request via WORK_REQUEST_ID when the request is converted to execution.
• MTL_SERIAL_NUMBERS — source of asset attributes via ASSET_NUMBER.
• WIP_DISCRETE_JOBS — the resulting work order once WIP_ENTITY_ID is populated.
• Standard status, priority, and department lookup views (for example WIP_EAM_WORK_REQUEST_STATUSES_VL, WIP_EAM_WORK_REQUEST_PRIORITIES_VL, and HR department views) supply the descriptive values behind the ID columns.