Search Results eam_pending_text

Overview

APPS.EAM_WORK_ORDER_DETAILS_V is a reporting and integration view in Oracle Enterprise Asset Management (EAM) that consolidates work order header information together with status, material shortage, workflow, and warranty context. It is documented internally as FND Design Data EAM.EAM_WORK_ORDER_DETAILS_V with a status of VALID, and is classified as an internal view type. The view exposes work order identifiers, organization context, user-defined status values, pending approval flags, material shortage indicators, and standard Who columns. Its principal value lies in presenting a single denormalized row per work order that downstream reports, Oracle Applications programs, and integration extracts can consume without joining EAM base tables directly.

The view carries the standard Oracle warning that it is for internal use only and is not supported for direct customer access except through standard Oracle Applications programs. Consultants should therefore treat it as a read-only reporting aid rather than a supported extension point, and should rely on the documented 12.1.1 and 12.2.2 behavior when building any dependent logic.

Underlying Base Objects

The documented ETRM metadata for 12.2.2 lists the referenced base objects as EAM_CONSTRUCTION_ESTIMATES, EAM_WORK_ORDER_DETAILS, EAM_WO_STATUSES_V, FND_MESSAGE, and MFG_LOOKUPS. The primary driver is EAM_WORK_ORDER_DETAILS, which supplies the work order header, organization, and Enhanced Who columns. EAM_WO_STATUSES_V contributes the user-defined status description used to derive the displayed status text. MFG_LOOKUPS is referenced for the workflow type lookup (EAM_WORKFLOW_TYPE), and FND_MESSAGE is used to resolve display text. EAM_CONSTRUCTION_ESTIMATES is referenced for construction-related work order associations. Each referenced object is presented through a synonym in the APPS schema, consistent with standard EBS naming.

Key Columns

• WIP_ENTITY_ID — primary work order identifier, key for joining to WIP and EAM entities.
• ORGANIZATION_ID — inventory/asset organization that owns the work order.
• USER_DEFINED_STATUS_ID — numeric identifier for the user-defined work order status; joins to EAM_WO_STATUSES_V.
• WORK_ORDER_STATUS — VARCHAR2(80) display of the user-defined status.
• WORK_ORDER_STATUS_PENDING — VARCHAR2(4000) that concatenates the pending flag with the user defined status when the work order is pending, otherwise shows only the user-defined status.
• PENDING_FLAG — "Y" indicates a status change is pending approval; "N" or null indicates not pending. This is the column most relevant to the search term "work_order_status_pending".
• MATERIAL_SHORTAGE_CHECK_DATE and MATERIAL_SHORTAGE_FLAG / MATERIAL_SHORTAGE_DISP — material availability check results.
• WORKFLOW_TYPE — maps to lookup_code for the EAM_WORKFLOW_TYPE lookup.
• WARRANTY_CLAIM_STATUS — lookup-driven warranty claim state.
• DS_SCHEDULED_FLAG — indicates whether the Detailed Scheduler has scheduled the work order.
• CYCLE_ID and SEQ_ID — used by Multiple Asset Activity PM.
• Standard Who and Enhanced Who columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID).

Common Use Cases and Queries

Typical scenarios include work order status reporting, pending approval monitoring, material shortage dashboards, and integration extracts for maintenance systems. To locate work orders whose status change is awaiting approval:

• SELECT WIP_ENTITY_ID, ORGANIZATION_ID, WORK_ORDER_STATUS, WORK_ORDER_STATUS_PENDING FROM APPS.EAM_WORK_ORDER_DETAILS_V WHERE PENDING_FLAG = 'Y';
• SELECT WIP_ENTITY_ID, WORK_ORDER_STATUS_PENDING FROM APPS.EAM_WORK_ORDER_DETAILS_V WHERE UPPER(WORK_ORDER_STATUS_PENDING) LIKE '%PENDING%';
• SELECT WIP_ENTITY_ID, MATERIAL_SHORTAGE_DISP, MATERIAL_SHORTAGE_CHECK_DATE FROM APPS.EAM_WORK_ORDER_DETAILS_V WHERE MATERIAL_SHORTAGE_FLAG = 1;

Because the object is documented as an internal, unsupported view, queries should be limited to read-only reporting, and any dependency should be validated against the target release (12.1.1 or 12.2.2) before deployment.