Results for “bulk_batch_id”

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

Overview

PM_BTCH_PKG is a table in the GME schema (Process Manufacturing Process Execution) within Oracle EBS 12.1.1 and 12.2.2. Despite the misleading "_PKG" suffix, which in Oracle naming conventions typically denotes a PL/SQL package, the ETRM metadata explicitly classifies this object as a TABLE with a status of VALID. The official product documentation carries the terse annotation "* NOT USED *", meaning Oracle does not publish a functional description of this table in the standard ETRM reference for this release. This is characteristic of certain internal or legacy Process Manufacturing batch structures retained in the schema for referential integrity and backward compatibility with dependent concurrent programs, forms, and APIs, even where the current application layer no longer surfaces the table directly to end users.

From a heuristic Data Vault modeling perspective, the mined foreign key structure suggests a link classification. A link table resolves many-to-many relationships between hubs by holding the composite business keys of the participating entities. Here, the table carries three foreign key columns referencing batch-header and material-detail entities, making a link interpretation reasonable as a modeling suggestion rather than an authoritative Oracle design statement.

Key Information Stored

The physical schema in 12.2.2 documents 8 columns. The most significant are the three business-relevant key columns that collectively form the primary key PM_BTCH_PKG_PK (BULK_BATCH_ID, BULK_LINE_ID, PKG_BATCH_ID):

• BULK_BATCH_ID — identifier of the bulk batch, with foreign keys to PM_BTCH_HDR and PM_MATL_DTL; the primary association to the bulk-side batch header.
• BULK_LINE_ID — the bulk material detail line that participates in the packaging linkage; part of the composite primary key.
• PKG_BATCH_ID — identifier of the packaging batch, referencing PM_BTCH_HDR; the packaging-side counterpart to the bulk batch.
• CREATED_BY — the user ID that created the row.
• CREATION_DATE — timestamp of row creation.
• LAST_UPDATED_BY — the user ID of the most recent update.
• LAST_UPDATE_DATE — timestamp of the most recent update.
• LAST_UPDATE_LOGIN — login identifier associated with the last update, used for audit trail continuity.

Only the three composite key columns act as business-key candidates; no separate surrogate (sequence-generated) key is documented. The four WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE) plus LAST_UPDATE_LOGIN provide the standard Oracle Applications audit footprint.

Common Use Cases and Queries

The table's principal use is establishing the parent-child association between bulk and packaging batches in process manufacturing flows. Reporting on which packaging batch consumed a given bulk batch relies on joining through these keys.

• Traceability reporting: list all packaging batches linked to a bulk batch.
• Data migration validation: confirm referential integrity between PM_BTCH_HDR and the linkage rows.
• Audit review: identify rows updated after a given date using LAST_UPDATE_DATE.

SELECT pkg_batch_id, bulk_batch_id, bulk_line_id
FROM   gme.pm_btch_pkg
WHERE  bulk_batch_id = :bulk_batch_id;

Because the object is annotated "* NOT USED *", queries should be validated against the actual seeded data volume before being relied upon for operational reporting.

Related Objects

The documented foreign key relationships tie PM_BTCH_PKG to the following objects:

• PM_BTCH_HDR — joined on PM_BTCH_PKG.BULK_BATCH_ID = PM_BTCH_HDR.BATCH_ID for the bulk side.
• PM_BTCH_HDR — joined on PM_BTCH_PKG.PKG_BATCH_ID = PM_BTCH_HDR.BATCH_ID for the packaging side.
• PM_MATL_DTL — joined on BULK_BATCH_ID and BULK_LINE_ID for material detail consistency.

These three dependencies define the table's role as the connective layer between batch headers and their material detail lines, reinforcing the link-table classification derived from the FK structure.