Search Results sys_il0000400894c00002

Overview

GMO.GMO_CBR_XML is a persistent table in the Oracle E-Business Suite GMO (Process Manufacturing / Oracle E-Records) schema whose sole purpose is to store the consolidated Control Batch Record (CBR) as an XML document. In regulated process manufacturing environments, a Control Batch Record aggregates the complete production history of a batch — material consumption, quality results, equipment events, and electronic signatures — into a single signed, auditable artifact. This table holds the serialized XML rendering of that record, one row per batch. It complements the relational batch data held in operational tables by providing an immutable, self-contained snapshot suitable for archival, inspection, and regulatory submission.

The table resides in the APPS_TS_TX_DATA tablespace with PCTFREE 10, and its LOB segment is stored in the same tablespace. From a Data Vault modeling perspective, the mined relationship data classifies this object as a standalone entity. Because it carries a single business key (BATCH_ID) and descriptive payload (the CBR_XML CLOB) with no foreign-key dependencies, it is best understood as a satellite-style attribute table keyed to the batch, rather than a hub or link. This is a modeling suggestion only; the physical schema does not enforce foreign keys.

Key Information Stored

The documented schema is deliberately narrow — two columns — which reflects its role as a document store rather than a normalized transactional table.

• BATCH_ID (NUMBER, mandatory) — The batch identifier. This is the primary key column of GMO_CBR_XML_PK and also the column of the unique index GMO_CBR_XML_U1 in APPS_TS_TX_IDX. It is therefore both the surrogate primary key and the business-key candidate for this table; there is no independent generated key.
• CBR_XML (CLOB, length 4000, nullable) — The generated Control Batch XML for the batch. Stored as a character large object so that arbitrarily long consolidated records can be persisted. Overflows are handled by the LOB segment backed by the index SYS_IL0000400894C00002$$, a unique LOB index in APPS_TS_TX_DATA. The presence of this LOB index in the metadata is an internal, system-generated artifact tied one-to-one with the CBR_XML column and is not a user-defined business key.

Because the table has no other columns, all batch-level descriptive attributes must be obtained by joining to the batch header tables on BATCH_ID. The CLOB is the substantive data payload.

Common Use Cases and Queries

Typical usage centers on retrieving, validating, or exporting the consolidated record for a given batch, and on administrative housekeeping. A straightforward retrieval mirrors the documented query text:

• Fetching the XML for a specific batch: SELECT CBR_XML FROM GMO.GMO_CBR_XML WHERE BATCH_ID = :batch_id;
• Checking which batches have a consolidated record versus those still pending generation (anti-join against the batch master).
• Extracting XML fragments with DBMS_LOB.SUBSTR(CBR_XML, 4000, 1) or XMLTYPE(CBR_XML) for reporting and inspector review.
• Measuring record size and growth with DBMS_LOB.GETLENGTH(CBR_XML) to plan archival and purge.
• Audit and compliance reporting via XMLTABLE to shred signature, quality, and material-consumption nodes into relational rows for trend analysis.

Because the CLOB is read-mostly, most operations are SELECTs; inserts and updates occur when a batch record is generated or regenerated.

Related Objects

The metadata records no outgoing foreign-key references from this table, and the only inbound reference is the internal LOB index GMO_CBR_XML# (referenced-by list). The following are the most significant associated objects, with joins on the batch key:

• GMO_CBR_XML_PK — primary key constraint/index on BATCH_ID.
• GMO_CBR_XML_U1 — unique index on BATCH_ID in APPS_TS_TX_IDX.
• SYS_IL0000400894C00002$$ — LOB index supporting the CBR_XML column.
• Batch header / GME batch master — join on BATCH_ID to obtain batch number, product, plant, and status context.
• GMO_CBR_XML# — the LOB-dependent object shown in dependencies.
• E-Records and electronic signature tables — relate through the batch key to reconcile signed records with the consolidated XML.
• Batch record generation concurrent programs and the GMO PL/SQL APIs — populate and regenerate the CBR_XML payload.

This object is specific to the GMO schema and is present in both 12.1.1 and 12.2.2; the documented physical schema above reflects the 12.2.2 ETRM catalog.