Search Results gmp_resource_device_messages




Overview
Explore in AI Chat

Overview

GMP_RESOURCE_DEVICE_MESSAGES is a table owned by the GMP schema within the Oracle E-Business Suite Process Manufacturing Process Planning module. Its documented purpose is to serve as the mapping between resource parameters and device response messages. In practical terms, it records which process parameter, associated with a manufacturing resource, is responsible for generating a given response message emitted by a device (such as an operator terminal, weigh scale, or automated equipment controller). This mapping supports the flow of instructions and feedback between the planning engine and shop-floor equipment during process execution.

The table is classified heuristically, via the mined foreign-key structure, as standalone in a Data Vault sense. This classification carries no functional impact; it simply reflects that no foreign keys reference this table from dependent child tables. The single documented outbound relationship is a foreign key on PROCESS_PARAM_ID referencing GME_PROCESS_PARAMETERS, which anchors the table's parameter dimension. The modeling suggestion implied by the standalone classification is that this object behaves more like a reference or association table than a hub or satellite in its own right, though implementations vary.

Key Information Stored

The table contains 11 documented columns. The most significant are:

  • RESOURCE_ID — Identifies the manufacturing resource whose parameter-to-message mapping is defined. This is part of the composite unique business key.
  • DEVICE_ID — Identifies the device that produces or receives the response message. Part of the composite unique business key.
  • PROCESS_PARAM_ID — The process parameter driving the message; documented as a foreign key to GME_PROCESS_PARAMETERS.
  • RESP_COMP_CODE_VALUE — The response component code value, completing the composite unique business key. The combination (RESOURCE_ID, DEVICE_ID, RESP_COMP_CODE_VALUE) forms the unique index GMP_RESOURCE_DEVICE_MESSAGES_U, the primary business-key candidate.
  • RESP_COMP_CODE_UOM — Unit of measure associated with the response component code value.
  • EVENT_ID — Correlates the mapping with an event, allowing conditional or event-driven message handling.
  • Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, and LAST_UPDATE_DATE capture standard Oracle EBS who/when auditing.

No separate single-column surrogate primary key is documented beyond the audit columns; the unique index acts as the logical identifier. Any downstream integration should treat the three-column unique key as the natural identity for deduplication.

Common Use Cases and Queries

Typical scenarios include diagnosing missing or misrouted device messages, validating that all parameters on a resource are wired to the correct response components, and reporting on message configuration ahead of a shop-floor deployment. A representative query to retrieve the mapping for a resource joins the table to GME_PROCESS_PARAMETERS:

  • SELECT m.RESOURCE_ID, m.DEVICE_ID, m.PROCESS_PARAM_ID, p.PARAMETER_NAME, m.RESP_COMP_CODE_VALUE, m.RESP_COMP_CODE_UOM FROM GMP.GMP_RESOURCE_DEVICE_MESSAGES m, GME.GME_PROCESS_PARAMETERS p WHERE m.PROCESS_PARAM_ID = p.PROCESS_PARAM_ID AND m.RESOURCE_ID = :resource_id;
  • A validation query checks for parameters lacking a device mapping by outer-joining from GME_PROCESS_PARAMETERS to this table and filtering where DEVICE_ID IS NULL.
  • Audit reporting can extract rows where LAST_UPDATE_DATE falls within a given window to trace configuration changes.

Related Objects

  • GME_PROCESS_PARAMETERS — joined on PROCESS_PARAM_ID; the authoritative source of process parameter definitions.
  • GMP_RESOURCES (or equivalent resource master) — the likely parent of RESOURCE_ID, supplying resource attributes.
  • Device/terminal configuration tables in GMP — the parent of DEVICE_ID, defining shop-floor equipment.
  • Event definition tables — referenced by EVENT_ID to interpret event-driven messaging.
  • Process planning and execution APIs that read this mapping when dispatching resource parameters to devices during production.

Because the table is standalone with respect to inbound foreign keys, its dependence is one-directional: it references master data but is not itself referenced by dependent transactional records.