Results for “priority_meaning”

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

Overview

The APPS.EAM_OUTSTANDING_WORK_ORDERS_V view is a reporting construct within the Oracle Enterprise Asset Management (EAM) module. It consolidates forecasted preventive maintenance (PM) work orders together with any corresponding discrete jobs that have already been released into Work in Process. Its documented purpose in Oracle E-Business Suite 12.1.1 and 12.2.2 is to present work orders that have been forecasted by the Preventive Maintenance scheduling process, enabling planners and maintenance supervisors to review upcoming PM-driven workload before it is firmed into executable jobs.

The view is owned by the APPS schema and is valid in both releases. It is not a transactional entity; it exists purely to project forecasted PM demand alongside the status and attributes of related work order records. The inclusion of STATUS_TYPE and its associated lookup meaning column makes the view particularly relevant when users search on status_type_meaning, since it allows the raw status code to be joined to a human-readable description from the manufacturing lookups.

Underlying Base Objects

The view is defined over a mixture of EAM-specific tables, WIP entities, and standard lookup and item masters. The documented base objects include:

• EAM_FORECASTED_WORK_ORDERS — the driving table (aliased FW), holding PM-forecasted work order rows filtered by PROCESS_FLAG <> 'Y'.
• WIP_DISCRETE_JOBS (WDJ) — outer-joined on WIP_ENTITY_ID, supplying PM schedule linkage, status, and work order type.
• WIP_ENTITIES (WE) — outer-joined to resolve the work order name for entity type 6.
• MTL_EAM_ASSET_ACTIVITIES (MEAA) — outer-joined via ACTIVITY_ASSOCIATION_ID, providing asset activity, serial number, priority, and cause codes.
• MFG_LOOKUPS (ML1 through ML8) — eight lookup aliases that decode numeric codes into MEANING values for status, work order type, activity type, cause, shutdown type, and forecast type.
• BOM_DEPARTMENTS (BD) — outer-joined to resolve the owning department code.
• MTL_SYSTEM_ITEMS (MSI) — supplies the item description when no WIP entity exists.

Folder metadata further notes dependencies on EAM_WORK_ORDER_DETAILS_V, EAM_WO_STATUSES_V, MTL_EAM_ASSET_ACTIVITIES_V, and the FND_MESSAGE package, reflecting the layered EAM reporting stack.

Key Columns

• WORK_ORDER_PM_TYPE — derived via DECODE: value 1 indicates a forecast-only row, 2 a released PM job, and 3 an action-type 1 (manual/ad-hoc) forecast.
• STATUS_TYPE / STATUS_TYPE_MEANING — the discrete job status code and its decoded meaning from ML7, the primary column involved in the status_type_meaning search.
• WIP_ENTITY_NAME — the work order number planners reference.
• ACTION_TYPE and its meaning (ML6) — classifies the forecast action.
• DESCRIPTION — resolved from the discrete job or, where absent, from the item master.
• SCHEDULED_START_DATE / SCHEDULED_COMPLETION_DATE — both forecast (FW) and job (WDJ) dates for variance analysis.
• FIRM_PLANNED_FLAG, NOTIFICATION_REQUIRED, TAGOUT_REQUIRED, PLAN_MAINTENANCE — operational control indicators.
• PRIORITY_CODE, ACTIVITY_TYPE_CODE, ACTIVITY_CAUSE_CODE, SHUTDOWN_TYPE_CODE — each accompanied by a decoded meaning from the lookup aliases.
• OWNING_DEPARTMENT_ID / DEPARTMENT_CODE — organizational responsibility for the work.
• ATTRIBUTE1 through ATTRIBUTE15 — the standard DFF flex segment set carried from the forecast row.

Common Use Cases and Queries

The principal scenario is a maintenance dashboard listing all outstanding PM forecasted work orders with their status descriptions, enabling schedulers to distinguish forecast rows from firmed jobs. A representative query follows:

SELECT work_order_pm_type,
       wip_entity_name,
       status_type,
       ml7_meaning AS status_type_meaning,
       description,
       scheduled_start_date,
       scheduled_completion_date
FROM   apps.eam_outstanding_work_orders_v
WHERE  work_order_pm_type = 2
ORDER  BY scheduled_start_date;

A second common requirement is grouping outstanding workload by department or status to support capacity planning:

SELECT department_code,
       ml7_meaning AS status_type_meaning,
       COUNT(*) AS wo_count
FROM   apps.eam_outstanding_work_orders_v
GROUP  BY department_code, ml7_meaning;

The view is also used as a source for concurrent program extracts and Oracle Discoverer or BI Publisher reports feeding asset maintenance key performance indicators. Because all joins to WIP and asset activity tables are outer joins, forecast rows without a released job are preserved, which is essential when reporting on the forecast pipeline prior to firming.