Search Results gmo_cbr_xml_pk

Overview

The GMO_CBR_XML table belongs to the GMO schema and is part of the Oracle EBS Manufacturing Execution System for Process Manufacturing product family. Its documented purpose is to store the consolidated Control Batch Record (CBR) XML for process manufacturing operations. In regulated process industries — pharmaceuticals, food and beverage, specialty chemicals — a Control Batch Record is the authoritative, audit-ready record of how a batch was produced: which ingredients were consumed, which steps were executed, who performed them, and what the resulting quality outcomes were. GMO_CBR_XML persists the consolidated representation of that record as a single XML document keyed by batch.

The object is reported with a status of VALID and is documented in ETRM 12.2.2 with an owner of GMO and exactly two columns. A heuristic Data Vault classification, mined from the foreign-key structure, treats this object as standalone. In Data Vault modeling terms this suggests the table behaves as a self-contained satellite-like store rather than a hub or link: it holds descriptive, potentially large payload content attached to a batch identifier, with no documented outbound foreign keys to other hubs or links. Modelers should treat this as a suggestion only, since the classification is mined heuristically rather than declared.

Key Information Stored

The documented physical schema contains only two columns, which makes the storage model deliberately narrow and payload-centric:

• BATCH_ID — The single documented business identifier and the column that composes the primary key constraint GMO_CBR_XML_PK. It ties each stored XML document to exactly one production batch. BATCH_ID is also the column of the unique index GMO_CBR_XML_U1, confirming a strict one-to-one mapping between a batch and its consolidated CBR document — no batch may own more than one row.
• CBR_XML — A large object column holding the consolidated Control Batch Record serialized as XML. Because the table is described as storing the consolidated record, this column is expected to contain the fully assembled document rather than fragments. A system-managed LOB index, SYS_IL0000400894C00002$$, is documented on this column, which is consistent with CBR_XML being a CLOB or BLOB and with Oracle maintaining a separate LOB segment and index for it.

Because there is only one surrogate/business identifier (BATCH_ID) and one payload column, the table functions as a document cache or materialized record store rather than a normalized transactional table. The primary key is a single-column key; there is no composite business key and no documented alternate key beyond the unique index on BATCH_ID.

Common Use Cases and Queries

Typical usage centers on retrieving or validating the consolidated record for a given batch, or auditing coverage — finding batches that have no consolidated record yet.

• Point lookup of a batch's record:
  SELECT batch_id, DBMS_LOB.GETLENGTH(cbr_xml) len
FROM gmo.gmo_cbr_xml WHERE batch_id = :batch_id;
• Extracting a specific XML node with XMLQuery/XMLTable to report a batch attribute without retrieving the full document.
• Coverage/completeness reporting — batches present in execution tables but absent here:
  SELECT g.batch_id FROM gmo.gme_batch_header g
WHERE NOT EXISTS (SELECT 1 FROM gmo.gmo_cbr_xml x WHERE x.batch_id = g.batch_id);
• Size and growth monitoring of the LOB payload for storage planning, using DBMS_LOB.GETLENGTH.
• Regulatory or quality audit extraction, exporting the XML for archival or electronic batch record submission.

Queries should always predicate on BATCH_ID to leverage GMO_CBR_XML_U1; full-table scans over the LOB column are costly and should be avoided.

Related Objects

The heuristic relationship data classifies this object as standalone, and no foreign keys are documented on it. Relationships to surrounding GMO objects are therefore logical, via BATCH_ID, rather than enforced referential constraints:

• GME_BATCH_HEADER — the batch master; joins on BATCH_ID to identify the production batch and its plant, product, and status.
• GME_BATCH_STEPS and GME_BATCH_STEP_ACTIVITIES — execution detail consolidated into the XML payload.
• GME_MATERIAL_DETAILS — consumed material lines reflected in the record.
• GMO_CBR_XML_PK / GMO_CBR_XML_U1 — the primary key and unique index that enforce one record per batch.
• GMD_QUALITY_RESULTS (or equivalent quality tables) — quality outcomes typically embedded in the consolidated CBR content.
• GMO Execution APIs and concurrent programs that generate and write the consolidated XML.