Search Results pm_btch_hdr_u1




Overview
Explore in AI Chat

Overview

The PM_BTCH_HDR table is the central header table for batches and Firm Planned Orders (FPOs) within the Oracle Process Manufacturing (OPM) Process Execution (GME) module in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It serves as the master record for a production batch, storing high-level control and definition information that governs the manufacturing process. As a header table, it establishes the foundational link to associated master data, such as formulas and routings, and connects to all detailed transactional data for materials, resources, and steps related to the batch. Its role is critical for the execution, tracking, and costing of process manufacturing operations.

Key Information Stored

While the provided metadata does not list specific columns beyond the keys, the primary and foreign key structure defines its core data relationships. The table's primary identifier is BATCH_ID (primary key PM_BTCH_HDR_PK). A unique constraint (PM_BTCH_HDR_U1) enforces business key integrity using PLANT_CODE (organization), BATCH_NO, and BATCH_TYPE. Key foreign key columns link the batch to its defining master data: FORMULA_ID (link to FM_FORM_MST), ROUTING_ID (link to FM_ROUT_HDR/GMD_ROUTINGS_B), and FMEFF_ID (link to FM_FORM_EFF for formula effectivity). Other significant foreign keys include WIP_WHSE_CODE (warehouse from IC_WHSE_MST), PARENTLINE_ID (link to parent material detail in PM_MATL_DTL), and TEXT_CODE (link to PM_TEXT_HDR for instructions).

Common Use Cases and Queries

This table is fundamental for batch inquiry, traceability, and reporting. Common operational queries involve joining to related detail tables to get a complete batch snapshot. For example, to retrieve basic batch header information along with its formula and routing details, a query would join to SY_ORGN_MST_B for the plant name and to the formula and routing master tables. Performance reporting often aggregates data from PM_BTCH_HDR with cost or yield information from other tables. A critical use case is batch genealogy and traceability, where PM_BTCH_HDR is linked via BATCH_ID to its components in PM_MATL_DTL and its outputs, or to quality results in QC_RSLT_MST and QC_SMPL_MST to track quality events associated with the batch.

Related Objects

PM_BTCH_HDR has extensive relationships within the GME and broader OPM landscape. It is directly referenced by numerous key transactional tables, including:

  • PM_MATL_DTL and PM_ROUT_DTL: Store the material requirements and routing operation steps for the batch.
  • PM_HIST_HDR: Holds historical records for completed or closed batches.
  • QC_RSLT_MST, QC_SMPL_MST, QC_SPEC_MST: Link quality samples, specifications, and results to the batch.
  • PM_BTCH_PKG: References it for bulk and packaged batch relationships.
  • RH_MORD_IMP: Used for manufacturing order import interfaces.
Furthermore, it depends on master data tables like FM_FORM_MST (formula), GMD_ROUTINGS_B (routing), SY_ORGN_MST_B (organization), and IC_WHSE_MST (warehouse).