Search Results activity_cause_disp




Overview
Explore in AI Chat

Overview

APPS.WIP_EAM_WORK_ORDERS_V is a reporting and integration view within the Work in Process (WIP) product of Oracle E-Business Suite, documented for releases 12.1.1 and 12.2.2. It exposes Maintenance Work Orders created and managed through Oracle Enterprise Asset Management (EAM), presenting a consolidated, denormalized projection of work order header data. Rather than requiring report authors and integration developers to join the discrete job table, the work order details view, asset instance data, lookup tables, and project accounting packages manually, the view performs this assembly in a single queryable object with STATUS = VALID in the APPS schema.

Its practical role is to serve as the primary read-only interface for EAM maintenance work order inquiries, custom concurrent programs, Oracle Reports and BI Publisher data models, and outbound interface extracts. Because it is a view rather than a table, all access is governed by the standard EBS security model applied to the underlying objects, and no DML should be issued against it.

Underlying Base Objects

The view draws from a documented set of base objects spanning several EAM and manufacturing schemas:

  • WIP_DISCRETE_JOBS and WIP_ENTITIES — synonym access providing the core work order identifier, work order name, entity type, organization, and scheduling attributes.
  • EAM_WORK_ORDER_DETAILS_V — the view supplying EAM-specific attributes such as asset group, activity type, priority, shutdown and tagout flags, and maintenance planning indicators.
  • CSI_ITEM_INSTANCES — source of asset instance number and instance description for serialized asset work orders.
  • BOM_DEPARTMENTS — resolving the owning department code.
  • MFG_LOOKUPS — referenced multiple times to translate stored lookup codes into display meanings for work order type, activity type, activity cause, priority, and shutdown type.
  • WIP_SCHEDULE_GROUPS — providing the schedule group name.
  • MTL_PARAMETERS — organization-level parameters.
  • EAM_COMMON_UTILITIES_PVT and PJM_PROJECT — PL/SQL packages invoked within the view definition to derive parent asset information and to convert internal project and task identifiers into their display numbers and names.

Key Columns

Common Use Cases and Queries

Typical scenarios include open work order listings, asset maintenance history, overdue work order exception reports, and project-charged maintenance extracts.

  • Listing open maintenance work orders for an organization.
  • Reporting on work orders by asset instance and activity type.
  • Identifying work orders past their due date.
SELECT wip_entity_name, asset_number, work_order_type_disp,
       priority_disp, scheduled_start_date, due_date
FROM   apps.wip_eam_work_orders_v
WHERE  organization_id = :p_org_id
AND    status_type IN ('RELEASED', 'UNRELEASED')
ORDER BY due_date;

SELECT wip_entity_name, asset_number, activity_type_disp,
       project_number, task_number
FROM   apps.wip_eam_work_orders_v
WHERE  due_date < SYSDATE
AND    date_completed IS NULL
ORDER BY due_date;

Because project and asset values are resolved through packaged function calls, queries should always constrain on indexed identifiers such as ORGANIZATION_ID or WIP_ENTITY_ID where possible to avoid unnecessary function execution across large result sets.