Results for “gmo_label_history”

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

Overview

GMO_LABEL_HISTORY is a table in the GMO schema of Oracle E-Business Suite, owned by the Manufacturing Execution System for Process Manufacturing (GMO) module. It stores the header-level record of every label that has been generated, requested, or printed within a process manufacturing environment, functioning as the audit and tracking backbone for label activity. Each row represents a single label instance identified by a unique LABEL_ID, with contextual information about the entity, transaction, requester, and lifecycle status of that label.

From a Data Vault modeling perspective, the mined foreign-key structure classifies this table heuristically as standalone. It can be modeled effectively as a hub with a business key, given that it carries a single-column surrogate primary key (LABEL_ID) and multiple dependent tables reference it directly. It does not exhibit a natural link structure to other hubs through its own foreign keys, which reinforces the standalone classification.

Key Information Stored

The table is documented with 15 columns in ETRM 12.2.2. The most significant are:

• LABEL_ID — The surrogate primary key, uniquely identifying each label history record. It is enforced by the GMO_LABEL_HISTORY_PK unique index and is the column referenced by all dependent tables.
• ENTITY_NAME and ENTITY_KEY — Identify the business object (for example, a batch, order, or inventory item) to which the label relates. These form a loose business-key candidate for locating label history by source entity.
• WMS_BUSINESSFLOW_CODE and WMS_BUSINESSFLOW_TRANS_ID — Link the label to a Warehouse Management business flow and its transaction instance, enabling cross-module traceability between GMO and WMS.
• TRANSACTION_TYPE — Classifies the nature of the label event, allowing filtering by operation type.
• REQUESTER and REQUESTED_DATE — Capture who requested the label and when, supporting accountability and turnaround reporting.
• ERECORD_ID — Associates the label with a related electronic record, useful for compliance and audit trails.
• STATUS — Tracks the lifecycle state of the label (for example, requested, printed, or completed), central to operational monitoring.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns recording row creation and modification metadata.

Common Use Cases and Queries

Typical reporting scenarios include auditing label output for a production batch, reconciling WMS label requests, and monitoring label status by requester or date range. A representative query retrieves recent label activity:

• SELECT label_id, entity_name, entity_key, status, requester, requested_date FROM gmo_label_history WHERE requested_date >= :start_date AND status = :status;
• SELECT h.label_id, d.* FROM gmo_label_history h JOIN gmo_label_history_dtl d ON h.label_id = d.label_id WHERE h.entity_key = :entity_key;
• SELECT h.*, r.* FROM gmo_label_history h JOIN wms_label_requests r ON h.label_id = r.label_id WHERE h.wms_businessflow_code = :flow_code;

These patterns support label reprint analysis, compliance audits, and integration troubleshooting between GMO and WMS.

Related Objects

Several documented tables reference GMO_LABEL_HISTORY through the LABEL_ID column, forming a dependent ecosystem:

• GMO_LABEL_HISTORY_DTL — Holds line-level detail for each label header, joined on LABEL_ID.
• GMO_LABEL_CONTEXT_T — Stores translated label context data, joined on LABEL_ID.
• WSH_REPORT_PRINTERS — References LABEL_ID for printer assignment on shipping reports.
• WMS_LABEL_REQUESTS — Links Warehouse Management label requests back to the GMO label history header.

Together these objects provide the full label lifecycle, from request through detailed content and printer routing, with GMO_LABEL_HISTORY serving as the central header record.