Search Results bulk_line_id

Overview

The PM_BTCH_PKG table is a data object within the Oracle E-Business Suite Process Manufacturing (GME) module, specifically under the Process Execution product family. According to the official ETRM documentation, its described purpose is explicitly marked as "* NOT USED *". This indicates that while the table structure exists in the application's database schema, it is not actively populated or utilized by standard application logic in the documented releases (12.1.1 and 12.2.2). Its intended historical or conceptual role was likely to manage relationships between bulk batches and their associated package batches within the manufacturing process flow. As a non-operational table, its primary relevance for consultants and DBAs is structural awareness during data analysis or system investigations.

Key Information Stored

The table's structure defines a composite primary key designed to link batch entities. The key columns are BULK_BATCH_ID, BULK_LINE_ID, and PKG_BATCH_ID. This suggests a design where a specific line item (BULK_LINE_ID) within a bulk batch (BULK_BATCH_ID) is associated with a packaged batch (PKG_BATCH_ID). Given the "not used" status, these columns are not populated by standard application processes. The table's existence is primarily for referential integrity, as defined by its foreign key constraints, rather than for storing active transactional data.

Common Use Cases and Queries

Direct interaction with PM_BTCH_PKG for business reporting or transaction processing is not a standard use case due to its inactive status. However, it may be referenced in specific technical scenarios. A primary use is during data integrity audits or troubleshooting exercises to understand the complete schema of the GME module. Sample queries would typically be investigative, such as checking for any anomalous data that may have been inserted outside of standard application flows. An example SQL pattern would be a simple record count verification:

• SELECT COUNT(*) FROM GME.PM_BTCH_PKG;

A result greater than zero would warrant further investigation into non-standard system modifications. Another query might examine its defined constraints in relation to active tables:

• SELECT * FROM USER_CONSTRAINTS WHERE TABLE_NAME = 'PM_BTCH_PKG';

Related Objects

The ETRM metadata specifies foreign key relationships from PM_BTCH_PKG to other core Process Manufacturing tables, which are operational. These relationships are crucial for understanding its intended logical model:

• PM_BTCH_HDR: The table has two foreign keys to PM_BTCH_HDR (Batch Header), linking via BULK_BATCH_ID and PKG_BATCH_ID. This shows the intended relationship was between two batch header records.
• PM_MATL_DTL: A foreign key exists to PM_MATL_DTL (Material Detail) using the composite of BULK_BATCH_ID and BULK_LINE_ID. This indicates the association was meant to be at the detailed material line level within a bulk batch.

The primary key constraint is named PM_BTCH_PKG_PK. These related objects are active components of the GME module, and their existence confirms PM_BTCH_PKG was designed as a junction table within the batch management structure before being deprecated from active use.