Search Results gmp_resource_equipments




Overview
Explore in AI Chat

Overview

The GMP.GMP_RESOURCE_EQUIPMENTS table is a Process Manufacturing Process Planning (GMP) object that maintains the association between process resources and the equipment items assigned to them. In Oracle EBS 12.1.1 and 12.2.2, it functions as a definition table that supports resource capacity modeling, shop-floor execution, and equipment-level planning for batch and process manufacturing environments. The table is owned by the GMP schema and carries a VALID status in the ETRM repository.

Under the heuristic Data Vault classification derived from its foreign-key structure, the table is characterized as standalone. This is a modeling suggestion rather than a delivered attribute: because the documented metadata exposes no outgoing FK dependencies, the object is best treated as a reference or link-style association between two business entities (a resource and an equipment item), rather than as a dependent satellite or a multi-parent transaction link.

Key Information Stored

The physical schema documents seven columns. The substantive business content is concentrated in the composite primary key, supplemented by standard Oracle EBS audit columns.

  • RESOURCE_ID — Identifier of the process resource. This is the leading component of the composite primary key and the primary join column to the resource definition tables.
  • EQUIPMENT_ITEM_ID — Identifier of the equipment item associated with the resource. This is the trailing component of the composite primary key.
  • CREATION_DATE — Timestamp recording when the resource-to-equipment association row was created.
  • CREATED_BY — User identifier of the person or process that inserted the association.
  • LAST_UPDATE_DATE — Timestamp of the most recent modification to the row.
  • LAST_UPDATED_BY — User identifier responsible for the most recent update.
  • LAST_UPDATE_LOGIN — Login identifier associated with the updating session, used for audit traceability.

The surrogate vs. business-key distinction is explicit in the metadata: the unique index GMP_RESOURCE_EQUIPMENTS_PK is defined on the pair (RESOURCE_ID, EQUIPMENT_ITEM_ID), making that combination the business-key candidate. There is no separate single-column surrogate key; the composite of the two business identifiers serves as both primary key and uniqueness constraint, which prevents duplicate resource-to-equipment assignments at the database level.

Common Use Cases and Queries

Typical scenarios include identifying all equipment tied to a given resource for capacity and routing analysis, determining which resources depend on a particular equipment item prior to maintenance or decommissioning, and auditing changes to resource-equipment assignments using the audit columns.

  • List equipment for a resource: SELECT RESOURCE_ID, EQUIPMENT_ITEM_ID FROM GMP.GMP_RESOURCE_EQUIPMENTS WHERE RESOURCE_ID = :resource_id;
  • Find resources using an equipment item: SELECT RESOURCE_ID FROM GMP.GMP_RESOURCE_EQUIPMENTS WHERE EQUIPMENT_ITEM_ID = :item_id;
  • Audit recent changes: SELECT RESOURCE_ID, EQUIPMENT_ITEM_ID, LAST_UPDATED_BY, LAST_UPDATE_DATE FROM GMP.GMP_RESOURCE_EQUIPMENTS WHERE LAST_UPDATE_DATE >= :from_date ORDER BY LAST_UPDATE_DATE DESC;
  • Detect duplicate assignments prior to load: query the composite key columns and compare against the GMP_RESOURCE_EQUIPMENTS_PK uniqueness rule.

Reporting commonly joins this table to resource headers and item master views to present resource capacity versus assigned equipment in process planning dashboards.

Related Objects

The documented metadata exposes no explicit FK relationships, but the composite key columns imply the following meaningful join partners and dependent objects in the GMP and adjacent schemas:

  • Resource definition tables (via RESOURCE_ID) — the parent resource entity supplying resource name, type, and capacity attributes.
  • Item master / equipment item tables (via EQUIPMENT_ITEM_ID) — the parent definition supplying equipment description and item attributes.
  • GMP routing and operation tables — reference resources to derive associated equipment during process planning.
  • Resource capacity and availability views — consume the assignments to compute effective capacity.
  • Open Interfaces / APIs for GMP resource maintenance — load and validate resource-equipment assignments.
  • Concurrent program and audit reports — use the CREATED_BY and LAST_UPDATED_BY columns for change tracking.

The table should therefore be modeled as a standalone association between resource and equipment masters, with the composite primary key enforcing business uniqueness.