Results for “job_type_meaning”

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

Overview

GMP_EAM_JOBS_RESOURCES_V is an Oracle E-Business Suite view owned by the APPS schema and defined in the Process Manufacturing Process Planning (GMP) product. Its documented purpose is to expose enterprise asset management (eAM) job information associated with Oracle Process Manufacturing (OPM) resources. Functionally, the view presents a flattened, reporting-ready projection of OPM batch step resource assignments aligned with the corresponding eAM job identifiers, so that maintenance and production planning activities can be correlated within a single query surface.

The view is most commonly referenced in reporting and integration scenarios where OPM batch execution data must be reconciled with eAM work orders, or where a unified listing of resource-level jobs is required. Because it is a view rather than a base table, it carries no independent storage; all data is resolved at runtime from the underlying batch and resource tables. The STATUS_TYPE_MEANING column, which is the element most frequently associated with user searches for this object, surfaces the decoded description of the batch status lookup code.

Underlying Base Objects

The view is defined over six referenced base objects: GME_BATCH_STEP_RESOURCES, GME_BATCH_STEP_ACTIVITIES, GME_BATCH_STEPS, GME_BATCH_HEADER, CR_RSRC_DTL, and GEM_LOOKUPS. The first four are OPM batch structures resolved through APPS synonyms, and CR_RSRC_DTL is likewise an APPS synonym (the OPM/eAM resource detail table). GEM_LOOKUPS is a lookup view supplying decoded meanings.

Joins are constructed along the OPM batch hierarchy. CR_RSRC_DTL.RESOURCES is equated to GME_BATCH_STEP_RESOURCES.RESOURCES, and CR_RSRC_DTL.ORGANIZATION_ID is matched to GME_BATCH_HEADER.ORGANIZATION_ID to enforce organization-level segmentation. The batch step resources are joined to batch step activities on BATCHSTEP_ACTIVITY_ID, BATCHSTEP_ID, and BATCH_ID, then to batch steps on BATCHSTEP_ID and BATCH_ID, and finally to the batch header on BATCH_ID. GEM_LOOKUPS is joined with LOOKUP_TYPE = 'GME_BATCH_STATUS' and LOOKUP_CODE = GME_BATCH_HEADER.BATCH_STATUS, producing the decoded status meaning. A SELECT DISTINCT clause suppresses duplicate rows arising from the multi-table join.

Key Columns

• ROW_ID — Row identifier derived from GME_BATCH_HEADER.ROWID.
• RESOURCE_ID and ORGANIZATION_ID — From CR_RSRC_DTL; identify the OPM resource and its owning organization.
• BATCH_ID, BATCH_NO, BATCH_TYPE — Core OPM batch header identifiers. BATCH_TYPE is decoded so that value 10 renders as 'FPO' and all other values as 'BATCH'.
• PLAN_START_DATE and PLAN_CMPLT_DATE — Planned start and completion dates for the batch.
• BATCH_STATUS — The raw status lookup code from GME_BATCH_HEADER.
• STATUS_TYPE_MEANING — The decoded meaning of the batch status, sourced from GEM_LOOKUPS.MEANING via the GME_BATCH_STATUS lookup type. This is the column most often queried by users searching for status descriptions.
• JOB_TYPE and JOB_TYPE_MEANING — Job classification and its decoded meaning, supporting eAM job identification.
• Additional columns include DEPARTMENT_ID, WIP_ENTITY_ID, WIP_ENTITY_NAME, DESCRIPTION, SCHEDULED_START_DATE, SCHEDULED_COMPLETION_DATE, STATUS_TYPE, CLASS_CODE, REBUILD_ITEM_ID, ENTITY_TYPE, and ENTITY_TYPE_CODE. Several of these are populated with TO_CHAR(NULL) or TO_NUMBER(NULL) placeholders in the view text, reflecting positional compatibility rather than active data.

Common Use Cases and Queries

A typical reporting requirement is to list OPM batch resources with their readable status and planned dates, filtered by organization and status meaning. For example:

• SELECT batch_no, resource_id, status_type_meaning, plan_start_date, plan_cmplt_date FROM apps.gmp_eam_jobs_resources_v WHERE organization_id = :org_id AND status_type_meaning = 'Released';
• SELECT batch_no, job_type_meaning, scheduled_start_date FROM apps.gmp_eam_jobs_resources_v WHERE batch_type = 'FPO';
• SELECT resource_id, COUNT(*) FROM apps.gmp_eam_jobs_resources_v WHERE status_type_meaning <> 'Closed' GROUP BY resource_id;

Because the view joins the full batch step hierarchy, queries should always constrain on ORGANIZATION_ID or BATCH_ID to limit result sets. Users filtering on status_type_meaning should note that the meaning is resolved dynamically from GEM_LOOKUPS, so any change to the GME_BATCH_STATUS lookup description will be reflected immediately in the view's output.