Search Results gmp_resource_device_messages_u

Overview

GMP.GMP_RESOURCE_DEVICE_MESSAGES is a transactional mapping table in the Oracle E-Business Suite Process Manufacturing (GMP) schema. Its documented purpose is to store resource parameter-to-device response message mappings. In practical terms, the table associates a manufacturing resource, a device, and a process parameter with the response value and unit of measure returned by that device. This allows Oracle EBS to interpret inbound device signals and correlate them to the correct process parameter configuration for a given resource.

The object resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10 and holds status VALID in both Oracle EBS 12.1.1 and 12.2.2. The ETRM relationship metadata classifies this object heuristically as standalone from a Data Vault modeling perspective. That classification suggests it behaves as an independent mapping construct rather than a strict hub, link, or satellite; however, its unique index on RESOURCE_ID, DEVICE_ID, and RESP_COMP_CODE_VALUE does imply a composite business key that could be modeled as a link between resource, device, and response code concepts if a Data Vault representation were required.

Key Information Stored

The table contains eleven documented columns. The most significant are the identifiers and response attributes that define the mapping:

• RESOURCE_ID — Unique identifier of the resource. Part of the unique business key.
• DEVICE_ID — Unique identifier of the device. Part of the unique business key.
• PROCESS_PARAM_ID — Unique identifier of the process parameter associated with the resource. This column carries a foreign key to GME_PROCESS_PARAMETERS, making it the primary relational anchor of the table.
• RESP_COMP_CODE_VALUE — The response value mapped to the process parameter of the resource. Part of the unique business key.
• RESP_COMP_CODE_UOM — The unit of measure for the response value, allowing numeric responses to be interpreted correctly.
• EVENT_ID — Identifier of the event associated with the mapping.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE — Standard EBS WHO columns recording audit and concurrency information.

The surrogate primary key is not separately enumerated in the metadata; the documented unique index GMP_RESOURCE_DEVICE_MESSAGES_U (RESOURCE_ID, DEVICE_ID, RESP_COMP_CODE_VALUE) is the business-key candidate. No additional unique index on a single numeric surrogate is shown in the ETRM extract.

Common Use Cases and Queries

Typical usage centers on resolving device responses to process parameters during shop-floor execution and on auditing the configured mappings. A common reporting query joins the table to GME_PROCESS_PARAMETERS to enrich parameter descriptions:

• Retrieve all mappings for a resource and device: SELECT * FROM GMP.GMP_RESOURCE_DEVICE_MESSAGES WHERE RESOURCE_ID = :resource_id AND DEVICE_ID = :device_id;
• Resolve a response value to its parameter and UOM: filter on RESP_COMP_CODE_VALUE and RESP_COMP_CODE_UOM.
• Audit recently changed mappings using LAST_UPDATE_DATE and LAST_UPDATED_BY.
• Validate configuration completeness by checking rows that lack a PROCESS_PARAM_ID match in GME_PROCESS_PARAMETERS.

Because the table is transactional and relatively narrow, it is well suited to extract-transform-load into integration or MES reporting layers that translate device telemetry into EBS process parameter values.

Related Objects

The documented relationship data identifies one foreign key and one dependent object:

• GME_PROCESS_PARAMETERS — referenced by PROCESS_PARAM_ID; provides parameter definitions for the mapping.
• APPS.GMP_RESOURCE_DEVICE_MESSAGES — the APPS synonym or view that exposes this table to application code.
• GMP_RESOURCE_DEVICE_MESSAGES_U — the unique index enforcing the composite business key on RESOURCE_ID, DEVICE_ID, and RESP_COMP_CODE_VALUE.

Additional joins to resource and device master tables are implied by RESOURCE_ID and DEVICE_ID, though the ETRM extract does not enumerate those foreign keys explicitly. Analysts should confirm those parent objects in the target instance before relying on them for reporting.