Results for “gme_batch_status”

22 results




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

Overview

APPS.GMP_EAM_JOBS_RESOURCES_V is a reporting and integration view within the Oracle E-Business Suite Process Manufacturing (OPM) module, documented under ETRM for releases 12.1.1 and 12.2.2. The view flattens the relationship between production batches, their step-level activities, and the resources consumed at each step, exposing that information in a single denormalized projection. Its name references both the EAM (Enterprise Asset Management) job concept and resource detail, reflecting its role in surfacing batch-to-resource associations for downstream reporting, integration, and scheduling analysis.

The view is owned by APPS and is intended for read-only consumption. Because it resolves numerous master-detail joins across the batch hierarchy, it isolates callers from the underlying normalization of GME batch and CR resource tables. When users search for "GEM VISTEX" in this context, this view is a common hit because its name shares the "GMP/GEM" prefix used by OPM objects and because it participates in batch/resource reporting frequently extracted for integration with external systems such as Vistex.

Underlying Base Objects

The view is defined over six referenced objects documented in the ETRM metadata:

  • GME_BATCH_HEADER (SYNONYM) — the batch master record supplying batch ID, batch number, planned start and completion dates, batch status, and batch type.
  • GME_BATCH_STEPS (SYNONYM) — the step-level definition belonging to a batch.
  • GME_BATCH_STEP_ACTIVITIES (SYNONYM) — the activities executed within each batch step.
  • GME_BATCH_STEP_RESOURCES (SYNONYM) — the resource usage lines attached to batch step activities, including the foreign key to CR_RSRC_DTL through the RESOURCES column.
  • CR_RSRC_DTL (SYNONYM) — the resource detail table providing RESOURCE_ID and ORGANIZATION_ID.
  • GEM_LOOKUPS (VIEW) — the lookup view used to decode batch status into a readable meaning, restricted to lookup_type = 'GME_BATCH_STATUS'.

The joins chain the hierarchy: GBSR to GBSA on batchstep_activity_id, batchstep_id, and batch_id; GBSA to GBS on batchstep_id and batch_id; GBS to GBH on batch_id; CRD to GBSR on RESOURCES with matching organization_id, and GEM to GBH on status code. A DISTINCT clause suppresses duplicates arising from these one-to-many relationships.

Key Columns

  • ROWID (GBH.ROWID) — passthrough row identifier from the batch header, used for row uniqueness.
  • RESOURCE_ID and ORGANIZATION_ID — from CR_RSRC_DTL, identifying the resource and its owning organization.
  • BATCH_ID and BATCH_NO — the batch identity; BATCH_NO is projected twice in the view text.
  • PLAN_START_DATE and PLAN_CMPLT_DATE — the planned schedule window for the batch.
  • BATCH_STATUS and MEANING — the status code and its decoded lookup meaning from GEM_LOOKUPS.
  • BATCH_TYPE — with a DECODE expression rendering type 10 as 'FPO' and all others as 'BATCH'.
  • Four placeholder expressions (TO_CHAR(NULL), TO_NUMBER(NULL), TO_NUMBER(NULL), TO_CHAR(NULL)) — positional null columns that preserve a fixed column signature for consuming applications.

Common Use Cases and Queries

Typical scenarios include reporting which resources a batch consumes, extracting batch schedules by resource for capacity planning, and feeding batch/resource data to external systems. A representative query:

  • SELECT batch_no, resource_id, organization_id, plan_start_date, batch_status, meaning FROM apps.gmp_eam_jobs_resources_v WHERE organization_id = :org AND batch_status = :status;
  • SELECT resource_id, COUNT(DISTINCT batch_id) FROM apps.gmp_eam_jobs_resources_v GROUP BY resource_id;
  • SELECT * FROM apps.gmp_eam_jobs_resources_v WHERE plan_start_date BETWEEN :from AND :to ORDER BY plan_start_date;

Because the view issues no DML and performs DISTINCT over a multi-table join, queries should be constrained by organization_id and date range to limit full-scan cost.