Results for “eam_work_request_assoc_v”

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

Overview

EAM_WORK_REQUEST_ASSOC_V is a seeded Oracle E-Business Suite view owned by the APPS schema and validated in releases 12.1.1 and 12.2.2. Within the Enterprise Asset Management (EAM) module, it presents a consolidated list of all work requests and service requests that are associated with a given work order. The view is classified as a reporting and integration object: it does not store data itself, but projects the results of joins across the work request, asset instance, department, user, and service request entities into a single denormalized result set.

The view is deliberately constructed as a UNION-style compatibility layer. The first branch surfaces native EAM work request records from WIP_EAM_WORK_REQUESTS, while the service request branch joins CS_INCIDENTS_B_SEC, CS_INCIDENTS_VL_SEC, and EAM_WO_SERVICE_ASSOCIATION. To align both branches to a common projection, service request attributes are populated where present and substituted with typed NULL placeholders where the underlying request type has no equivalent. This design allows downstream forms, concurrent programs, and custom reports to query a single object for "all requests attached to a work order" without branching logic.

Underlying Base Objects

The documented base objects fall into four functional groups:

• Work request core: WIP_EAM_WORK_REQUESTS supplies the work request number, description, status, priority, type, expected resolution date, organization, and WIP entity reference.
• Asset and item context: CSI_ITEM_INSTANCES provides the asset instance number, while MTL_SYSTEM_ITEMS_B_KFV and MTL_SYSTEM_ITEMS_KFV supply concatenated segments and EAM item type used to derive the asset group and asset type descriptions.
• Organizational references: BOM_DEPARTMENTS resolves department code and ID, and FND_USER resolves the originator to a user name.
• Service request linkage: EAM_WO_SERVICE_ASSOCIATION links work orders to service requests, with CS_INCIDENTS_B_SEC, CS_INCIDENTS_VL_SEC, CS_INCIDENT_TYPES_VL_SEC, CS_INCIDENT_STATUSES_B, CS_INCIDENT_STATUSES_TL, CS_HZ_SR_CONTACT_POINTS, and HZ_PARTIES supplying the incident, status, type, customer, and contact attributes.

Codes and meanings are resolved against MFG_LOOKUPS using the lookup types EAM_REQUEST_TYPE, WIP_EAM_WORK_REQ_STATUS, and MTL_EAM_ASSET_TYPE.

Key Columns

• REQUEST_NUMBER, REQUEST_ID, REQUEST_TYPE, REQUEST_TYPE_CODE: Identification and classification of the request. REQUEST_TYPE_CODE returns the lookup code (1 for work requests).
• STATUS, WR_STATUS_ID: Human-readable and coded status of the underlying work request.
• ASSET_NUMBER, ASSET_GROUP, ASSET_TYPE, ASSET_TYPE_CODE: Asset instance, concatenated item segments, and asset classification.
• ORIGINATOR, REPORTED_DATE, EXP_RESOLUTION_DATE: Who created the request and the reported and expected completion dates.
• DEPARTMENT_CODE, DEPARTMENT_ID, ORGANIZATION_ID, WIP_ENTITY_ID: Organizational and work order linkage keys commonly used in joins.
• SR_* columns: SR_CREATED_BY, SR_STATUS_ID, SR_PRIORITY_ID, SR_TYPE_ID, SR_CUSTOMER_ID, SR_ACCOUNT_ID, and related contact columns expose service request attributes. SR_CLOSE_FLAG is hard-coded to 'Y'.

Common Use Cases and Queries

The view is typically used to list all requests against a work order, to reconcile EAM work requests with CRM service requests for the same asset, and to feed dashboards that track outstanding requests by department or asset group.

Reporting against a specific work order:

SELECT request_number, request_type, status, asset_number,
       originator, reported_date, exp_resolution_date
FROM   apps.eam_work_request_assoc_v
WHERE  wip_entity_id = :p_wip_entity_id;

Separating work requests from service requests by testing the SR_TYPE_ID placeholder — directly relevant to the search term sr_type_id:

SELECT request_number, request_type, status,
       CASE WHEN sr_type_id IS NULL
            THEN 'WORK REQUEST' ELSE 'SERVICE REQUEST' END AS request_origin
FROM   apps.eam_work_request_assoc_v
WHERE  organization_id = :p_org_id;

Because sr_type_id is substituted with TO_NUMBER(NULL) in the work request branch, an IS NULL test reliably distinguishes native work requests from associated service requests, while non-null values in the SR_* columns indicate an incident-based record joined through EAM_WO_SERVICE_ASSOCIATION.