Results for “parent_node”

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

Overview

GMO_BATCH_PROGRESSION is a transactional table owned by the GMO schema within the Oracle E-Business Suite Process Manufacturing module, specifically the Manufacturing Execution System (MES) for process manufacturing. It records batch progression events, maintaining the sequence and state transitions that a production batch undergoes as it moves through its routing steps, activities, and resources. The table serves as a central audit and event-tracking repository, capturing both the physical progress of the batch and the associated electronic records, XML payloads, and deviation references required for regulatory compliance and process control.

In heuristic Data Vault terms, the FK structure mined from the metadata classifies this object as standalone — it has no other tables referencing it, and only one outbound FK (DISPENSE_ID to GMO_MATERIAL_DISPENSES). This suggests a modeling pattern closer to an event/transaction satellite or a standalone transactional record rather than a classic hub or link. Where a Data Vault model is considered, GMO_BATCH_PROGRESSION would most naturally map to a satellite-like structure keyed by BATCH_ID and BATCHSTEP_ID, with PROGRESSION_ID acting as the technical surrogate.

Key Information Stored

The table contains 31 documented columns. Its surrogate primary key is PROGRESSION_ID, defined by the constraint GMO_BATCH_PROGRESSION_PK. A unique index, GMO_BATCH_PROGRESSION_U1, is also defined on PROGRESSION_ID, confirming it as the business-key candidate for row identification. The most significant columns include:

• BATCH_ID — identifies the production batch whose progression is being recorded.
• BATCHSTEP_ID — the routing step within the batch at which the progression event occurred.
• BATCHACTIVITY_ID — the specific activity executed at that step.
• BATCHRSRC_ID — the resource instance associated with the progression.
• MATERIAL_LINE_ID and DISPENSE_ID — link the progression to material consumption and dispensing operations; DISPENSE_ID carries an FK to GMO_MATERIAL_DISPENSES.
• SAMPLE_ID and DEVIATION_ID — reference quality samples and recorded deviations.
• TRANSACTION_ID and ERECORD_ID — tie the record to inventory transactions and electronic batch records.
• EVENT, EVENT_KEY, EVENT_DATE, PLANED_START_DATE — describe the event type, its key, timestamp, and planned start.
• STATUS, INCLUDED_IN_CBR, INCLUDE_IN_CBR — control whether the event is included in the current batch record and its processing state.
• XML_EREC, XML_MAP_CODE, COMPARE_XML — hold the serialized e-record XML and the mapping/comparison metadata used by the MES engine.
• PARENT_NODE, PARENT_KEY_NODE, PARENT_KEY_VAL, CURR_NODE_KEY, CURR_KEY_VAL — describe the hierarchical navigation of progression nodes.

Common Use Cases and Queries

Typical use cases include batch genealogy reporting, electronic batch record assembly, deviation traceability, and progression timeline analysis. A common query pattern joins progression to batch and step definitions:

SELECT p.progression_id, p.batch_id, p.batchstep_id, p.event, p.event_date, p.status
FROM gmo.gmo_batch_progression p
WHERE p.batch_id = :batch_id
ORDER BY p.event_date;

For dispensing traceability, analysts join to GMO_MATERIAL_DISPENSES on DISPENSE_ID. For CBR extraction, rows are filtered on INCLUDED_IN_CBR = 'Y' and the XML_EREC column is exported.

Related Objects

• GMO_MATERIAL_DISPENSES — referenced via DISPENSE_ID (documented FK).
• GMO_BATCHES — parent batch master, joined on BATCH_ID.
• GMO_BATCH_STEPS — routing steps, joined on BATCHSTEP_ID.
• GMO_BATCH_ACTIVITIES — activities, joined on BATCHACTIVITY_ID.
• GMO_BATCH_RESOURCES — resource instances, joined on BATCHRSRC_ID.
• GMO_SAMPLES — quality samples, joined on SAMPLE_ID.
• GMO_DEVIATIONS — deviations, joined on DEVIATION_ID.
• GMO_ERECORDS — electronic records, joined on ERECORD_ID.
• MTL_MATERIAL_TRANSACTIONS — inventory transactions, joined on TRANSACTION_ID.