Search Results wip_eam_work_req_status

Overview

APPS.WIP_EAM_WORK_REQUESTS_V is a reporting and integration view in Oracle E-Business Suite Release 12.1.1 and 12.2.2 that exposes Enterprise Asset Management (EAM) work request header information in a denormalized, user-readable form. The base transaction table, WIP_EAM_WORK_REQUESTS, stores work requests using internal foreign keys such as WORK_REQUEST_STATUS_ID, WORK_REQUEST_PRIORITY_ID, WORK_REQUEST_TYPE_ID, and WORK_REQUEST_OWNING_DEPT. The view resolves each of these identifiers into descriptive values by joining to MFG_LOOKUPS, BOM_DEPARTMENTS, and related master data, so that reports, Oracle Discoverer workbooks, OBIEE extracts, and custom concurrent programs can present status, priority, type, and department descriptions without repeating the decode logic.

The view also enriches the work request with maintenance object context from CSI_ITEM_INSTANCES and organizational EAM maintenance defaults from EAM_ORG_MAINT_DEFAULTS and MTL_EAM_LOCATIONS, and links to the associated WIP job through WIP_ENTITIES. The search term "wip_eam_work_req_status" corresponds directly to the WORK_REQUEST_STATUS column, which is derived from MFG_LOOKUPS using lookup type WIP_EAM_WORK_REQ_STATUS.

Underlying Base Objects

The view is defined over the following documented base objects:

• WIP_EAM_WORK_REQUESTS (synonym) — the driving table, aliased wr; supplies work request header attributes and the primary key WORK_REQUEST_ID.
• CSI_ITEM_INSTANCES (synonym) — outer-joined on maintenance_object_id to instance_id; supplies instance_number, instance_description, inventory_item_id, and category_id.
• WIP_ENTITIES (synonym) — outer-joined on wip_entity_id and organization_id; supplies the WIP_ENTITY_NAME of the linked work order.
• BOM_DEPARTMENTS (synonym) — outer-joined on department_id to work_request_owning_dept; supplies DEPARTMENT_CODE.
• MFG_LOOKUPS (view) — outer-joined three times (aliases lv1, lv2, lv3) against lookup types WIP_EAM_WORK_REQ_STATUS, WIP_EAM_ACTIVITY_PRIORITY, and WIP_EAM_WORK_REQ_TYPE.
• EAM_ORG_MAINT_DEFAULTS (synonym) — outer-joined on object_id with object_type = 50; supplies area_id, constrained by organization.
• MTL_EAM_LOCATIONS (synonym) — outer-joined on location_id to area_id; supplies location_codes.

All joins to these objects are outer joins, which ensures a work request row is returned even when the linked maintenance object, WIP job, department, location, or lookup value is missing.

Key Columns

• WORK_REQUEST_ID / WORK_REQUEST_NUMBER — primary key and the user-visible work request identifier.
• WORK_REQUEST_STATUS_ID / WORK_REQUEST_STATUS — status code and its lookup meaning; the WORK_REQUEST_STATUS column is the resolved value for search term "wip_eam_work_req_status".
• WORK_REQUEST_PRIORITY_ID / WORK_REQUEST_PRIORITY — priority code and its meaning from lookup type WIP_EAM_ACTIVITY_PRIORITY.
• WORK_REQUEST_TYPE_ID / WORK_REQUEST_TYPE — type code and meaning from lookup type WIP_EAM_WORK_REQ_TYPE.
• WORK_REQUEST_OWNING_DEPT / DEPARTMENT_CODE — owning department identifier and its department code.
• MAINTENANCE OBJECT CONTEXT — instance_number, instance_description, inventory_item_id, category_id from CSI_ITEM_INSTANCES.
• WIP_ENTITY_ID / WIP_ENTITY_NAME — linked WIP job for the work request.
• EXPECTED_RESOLUTION_DATE — planned completion date.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield columns.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical uses include operational work request status reports, backlog aging analysis, maintenance object history, and integration extracts feeding external CMMS or dashboard tools.

List open work requests with status and priority:

SELECT work_request_number, description, work_request_status,
       work_request_priority, expected_resolution_date
FROM   apps.wip_eam_work_requests_v
WHERE  work_request_status NOT IN ('CLOSED','CANCELLED');

Work requests by maintenance object instance:

SELECT instance_number, instance_description,
       work_request_number, work_request_status
FROM   apps.wip_eam_work_requests_v
WHERE  instance_number = :instance_number;

Filter by resolved status meaning (the wip_eam_work_req_status lookup) for a specific organization:

SELECT work_request_number, work_request_status,
       department_code, wip_entity_name
FROM   apps.wip_eam_work_requests_v
WHERE  organization_id = :org_id
AND    work_request_status = :status;  -- e.g. 'APPROVED'

Because the view already performs the MFG_LOOKUPS decodes and outer joins, querying it directly avoids redundant joins and produces results consistent with EAM work request forms and standard Oracle reports. Custom reports should join on WORK_REQUEST_ID and ORGANIZATION_ID to other EAM tables when additional detail is required.