Search Results job_type_meaning




Overview
Explore in AI Chat

Overview

MTL_EAM_JOBS_RESOURCES_V is a PL/SQL view owned by the APPS schema in Oracle E-Business Suite, delivered under the INV (Inventory) product. It consolidates work order job information with the resources assigned to operations, exposing a flattened result set purpose-built for Enterprise Asset Management (EAM) reporting and integration. The view is defined as the union of two underlying queries: an EAM work order query sourced from WIP_OPERATION_RESOURCES, WIP_OPERATIONS, WIP_ENTITIES, WIP_DISCRETE_JOBS and MFG_LOOKUPS, and a second branch pulled from GMP_EAM_JOBS_RESOURCES_V, the process manufacturing equivalent. Because resources are unioned across discrete and process work orders, callers can query a single object for resource-level job data regardless of the manufacturing method used.

In ETRM releases 12.1.1 and 12.2.2 the view is documented with status VALID and is used primarily by Oracle EAM and maintenance dashboards, resource-loading inquiries, and custom reports that need to correlate a work order with the resources assigned to it and the scheduled dates for those resources.

Underlying Base Objects

The documented base objects are WIP_DISCRETE_JOBS, WIP_ENTITIES, WIP_OPERATIONS, WIP_OPERATION_RESOURCES, MFG_LOOKUPS and GMP_EAM_JOBS_RESOURCES_V. The first four are synonyms resolving to their application tables, while MFG_LOOKUPS and GMP_EAM_JOBS_RESOURCES_V are views.

  • WIP_DISCRETE_JOBS supplies the job header: job type, class code, status type, scheduled start and completion dates, and the rebuild item.
  • WIP_ENTITIES supplies the work order identity and entity type.
  • WIP_OPERATIONS and WIP_OPERATION_RESOURCES supply operation-level resource assignments and department information.
  • MFG_LOOKUPS is joined twice to translate the numeric STATUS_TYPE against lookup type WIP_JOB_STATUS and the numeric job type against lookup type WIP_ENTITY into their display meanings.
  • GMP_EAM_JOBS_RESOURCES_V provides the process manufacturing branch, with JOB_TYPE repurposed as ENTITY_TYPE in the union.

Key Columns

Common Use Cases and Queries

Typical uses include maintenance reports listing resources on currently active jobs, and integration extracts feeding scheduling or capacity systems.

  • Filter by job type using the decoded meaning rather than the numeric code.
  • Restrict by scheduled date window or by WIP_ENTITY_NAME for a specific work order.
  • Aggregate resource counts per department or per work order.

Sample query:

SELECT WIP_ENTITY_NAME, JOB_TYPE_MEANING, RESOURCE_ID, DEPARTMENT_ID, STATUS_TYPE_MEANING FROM APPS.MTL_EAM_JOBS_RESOURCES_V WHERE JOB_TYPE_MEANING = 'Rebuild' AND SYSDATE BETWEEN SCHEDULED_START_DATE AND SCHEDULED_COMPLETION_DATE ORDER BY WIP_ENTITY_NAME;

Note that the view is already constrained to records where SYSDATE falls inside the scheduled window and where STATUS_TYPE is 1, 3 or 6, so callers cannot retrieve unreleased or completed jobs through this object and should query the base WIP tables when a broader status range is required.