Results for “eam_manage_reqs_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

EAM_MANAGE_REQS_V is a seeded Oracle E-Business Suite view owned by the APPS schema and classified under the Enterprise Asset Management (EAM) product family. Its documented purpose is to consolidate all work requests and all service requests that are in an open status into a single, query-friendly result set. In release 12.1.1 and 12.2.2 the view carries a VALID status and is exposed through the ETRM repository as a reporting and integration surface rather than a transactional entity.

The view is designed as a union-style abstraction: the work request branch is populated from the EAM work request tables, while the service request branch is represented by typed NULL placeholders (for example SR_CREATED_BY, SR_STATUS_ID, SR_PRIORITY_ID, SR_TYPE_ID, SR_CUSTOMER_ID) so that both request categories share one uniform column layout. This makes the view suitable for maintenance dashboards, work request queues, and any integration that needs a single cursor over open EAM requests.

Underlying Base Objects

The documented metadata lists the base objects referenced by the view, including BOM_DEPARTMENTS, CSI_ITEM_INSTANCES, CS_HZ_SR_CONTACT_POINTS, CS_INCIDENTS_B_SEC, CS_INCIDENTS_VL_SEC, CS_INCIDENT_STATUSES_B, CS_INCIDENT_STATUSES_TL, CS_INCIDENT_TYPES_VL_SEC, FND_USER, HZ_PARTIES, MFG_LOOKUPS, MTL_SYSTEM_ITEMS_B_KFV, MTL_SYSTEM_ITEMS_KFV, and WIP_EAM_WORK_REQUESTS. Most are referenced through synonyms, with several implemented as secured views (the _SEC suffix) that enforce Oracle security policies at query time.

The work request side is rooted in WIP_EAM_WORK_REQUESTS (WR), which supplies the request number, status, asset number, department, priority, type, and expected resolution date. Descriptive values are resolved through MFG_LOOKUPS lookups: EAM_REQUEST_TYPE, WIP_EAM_WORK_REQ_STATUS, and MTL_EAM_ASSET_TYPE. Asset context is joined from CSI_ITEM_INSTANCES and the MTL_SYSTEM_ITEMS_KFV key flexfield views for concatenated segments, while FND_USER resolves the originator and BOM_DEPARTMENTS resolves department details. The service request branch relies on the CS_INCIDENTS and CS_INCIDENT_STATUSES objects, though in this view those columns are projected as NULL for the work request rows.

Key Columns

• REQUEST_NUMBER – WR.WORK_REQUEST_NUMBER, the human-readable identifier of the request.
• REQUEST_TYPE / REQUEST_TYPE_CODE – Lookup meaning and code from EAM_REQUEST_TYPE (code 1).
• STATUS – Resolved meaning for WR.WORK_REQUEST_STATUS_ID from WIP_EAM_WORK_REQ_STATUS.
• WR_STATUS_ID – The raw WIP_EAM_WORK_REQ_STATUS lookup code stored on the work request; the column most commonly searched as wr_status_id.
• ASSET_NUMBER, ASSET_GROUP, ASSET_TYPE, ASSET_TYPE_CODE – Asset instance and item attributes, with ASSET_TYPE derived from MTL_EAM_ASSET_TYPE.
• WR_PRIORITY_ID, WR_TYPE_ID, WR_CREATED_BY – Priority, type, and creator identifiers for the work request.
• DEPARTMENT_CODE, DEPARTMENT_ID, ORGANIZATION_ID – Owning department and inventory organization context.
• ORIGINATOR, REPORTED_DATE, EXP_RESOLUTION_DATE – FND_USER name, creation timestamp, and target resolution date.
• REQUEST_ID, WIP_ENTITY_ID – Surrogate keys linking back to the work request and its WIP entity.
• SR_CLOSE_FLAG, SR_* columns – Service request attributes; for work request rows these are NULL or the literal 'Y'.

Common Use Cases and Queries

Typical usage filters on WR_STATUS_ID or STATUS to isolate open requests, and joins back to WIP_EAM_WORK_REQUESTS on REQUEST_ID for detail. A representative query follows.

SELECT request_number, request_type, status, asset_number,
       asset_group, department_code, originator, reported_date
FROM   apps.eam_manage_reqs_v
WHERE  wr_status_id = :p_status_id
ORDER  BY reported_date DESC;

Because the view already resolves lookup meanings, it is convenient for OBIEE/XML Publisher reports and interface extracts that must not join MFG_LOOKUPS directly. Note that the CS_* secured views enforce instance-level security, so results can vary by responsibility and site configuration.