Search Results status_type_meaning




Overview
Explore in AI Chat

Overview

APPS.MTL_EAM_JOBS_RESOURCES_V is a reporting and integration view in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 that exposes Enterprise Asset Management (EAM) work order job operations together with their assigned resources. The view presents discrete job header information from WIP_DISCRETE_JOBS and WIP_ENTITIES alongside operation-level resource assignments from WIP_OPERATION_RESOURCES and WIP_OPERATIONS, joining lookup tables to translate raw coded values into user-readable meanings. Its principal role is to give EAM and maintenance reporting a single denormalized source that resolves the resource-to-job relationship without requiring report authors to reconstruct the WIP entity, operation, and resource join paths themselves.

A defining characteristic of the view is its use of a UNION: the primary branch returns current discrete jobs whose scheduled window includes the current system date, while a second branch returns the same column shape from GMP_EAM_JOBS_RESOURCES_V. This design allows consumers to query EAM jobs and their resources through a consistent column list, regardless of which underlying process maintenance regime produced the record. The user search term status_type_meaning refers directly to one of the decoded columns the view provides, making this object a common entry point for status-driven reporting.

Underlying Base Objects

The documented referenced objects are GMP_EAM_JOBS_RESOURCES_V (VIEW), MFG_LOOKUPS (VIEW), WIP_DISCRETE_JOBS (SYNONYM), WIP_ENTITIES (SYNONYM), WIP_OPERATIONS (SYNONYM), and WIP_OPERATION_RESOURCES (SYNONYM). The WIP objects resolve to the core Work in Process tables that store job headers, entities, routing operations, and operation resource assignments; MFG_LOOKUPS supplies the meaning values used to decode WIP_JOB_STATUS and WIP_ENTITY lookup codes.

The join path enforces consistency across organizations and entities: WIP_OPERATION_RESOURCES is matched to WIP_OPERATIONS on organization, WIP entity, and operation sequence number; WIP_OPERATIONS is matched to WIP_ENTITIES and WIP_DISCRETE_JOBS on the WIP entity; and organization identifiers are carried through to prevent cross-organization mixing. Two independent lookup joins decode the status type and the entity/job type. The predicate restricting WIP_DISCRETE_JOBS.STATUS_TYPE to 1, 3, or 6 limits the primary branch to selected job statuses, and the date predicate SYSDATE BETWEEN scheduled_start_date AND scheduled_completion_date ensures only jobs within their active scheduled window are returned.

Key Columns

Common Use Cases and Queries

Typical uses include listing active EAM jobs by status meaning, reporting resource loading per department, and driving integrations that need decoded rather than coded values.

SELECT wip_entity_name,
       status_type,
       status_type_meaning,
       resource_id,
       department_id,
       scheduled_start_date,
       scheduled_completion_date
FROM   apps.mtl_eam_jobs_resources_v
WHERE  status_type_meaning = 'Released'
ORDER  BY scheduled_start_date;

A second common pattern aggregates resource assignments per job to support capacity and scheduling analysis:

SELECT wip_entity_name,
       status_type_meaning,
       COUNT(DISTINCT resource_id) resource_count
FROM   apps.mtl_eam_jobs_resources_v
GROUP  BY wip_entity_name, status_type_meaning;

Because the view is restricted to jobs whose scheduled window contains the current date and to selected status types in its primary branch, queries seeking historical or completed jobs should not rely on this object alone; the GMP_EAM_JOBS_RESOURCES_V union branch covers the maintenance-specific records excluded by those predicates.