Results for “qc_rslt_mst”

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

Overview

PM_BTCH_HDR is the batch and FPO (Firm Planned Order) header table within the Oracle EBS Process Manufacturing Process Execution module (GME). It serves as the central repository for batch master records, holding the identifying attributes and planning references that define a manufactured batch from creation through execution. Every batch, whether a production batch or a firm planned order, is anchored by a single row in this table, making it one of the foundational objects in the process manufacturing data model.

Based on the foreign key structure documented in ETRM metadata, PM_BTCH_HDR exhibits a satellite-leaning classification under heuristic Data Vault modeling. This reflects its role as a dependent, descriptive entity: it references master data such as formulas, routings, and organizations, while a wide array of downstream tables—material details, routing details, quality results, and history headers—reference it via BATCH_ID. It is best modeled as a satellite (or hub with satellite characteristics) whose natural business identity is governed by the unique index PM_BTCH_HDR_U1.

Key Information Stored

The table is anchored by a surrogate primary key and a composite business-key unique index, distinguishing internal identity from externally meaningful batch identification.

• BATCH_ID — The surrogate primary key (PM_BTCH_HDR_PK). Used as the join column by virtually all dependent tables, including PM_MATL_DTL, PM_ROUT_DTL, and QC_RSLT_MST.
• PLANT_CODE — The organization/plant in which the batch is defined. Part of the unique index PM_BTCH_HDR_U1 and a foreign key to SY_ORGN_MST and SY_ORGN_MST_B.
• BATCH_NO — The user-facing batch number. Along with PLANT_CODE and BATCH_TYPE, it forms the unique index PM_BTCH_HDR_U1, making it the principal business-key candidate.
• BATCH_TYPE — Classifies the batch record and completes the composite unique business key. Distinguishes batch variants within a plant.
• FORMULA_ID — References FM_FORM_MST, tying the batch to the formula used for its composition.
• FMEFF_ID — References FM_FORM_EFF, identifying the specific formula effectiveness/version applicable to the batch.
• ROUTING_ID — References the routing (FM_ROUT_HDR and GMD_ROUTINGS_B) that governs the batch's processing steps.
• WIP_WHSE_CODE — The warehouse in which the batch is executed, a foreign key to IC_WHSE_MST.
• PARENTLINE_ID — Self-referencing link to PM_MATL_DTL, used for parent/child batch relationships arising from bulk and packaged batch structures.
• TEXT_CODE — References PM_TEXT_HDR, associating descriptive text with the batch header.

Common Use Cases and Queries

Because batch identity is resolved through PLANT_CODE, BATCH_NO, and BATCH_TYPE, the most common access pattern retrieves the surrogate key for downstream processing. A typical lookup takes the form:

• SELECT batch_id FROM pm_btch_hdr WHERE plant_code = :plant AND batch_no = :batch_no AND batch_type = :type; — resolves the business key to the surrogate for joins against material, routing, and quality tables.
• Batch genealogy and material consumption reporting joins PM_BTCH_HDR to PM_MATL_DTL on BATCH_ID to enumerate ingredients for a given batch.
• Work-in-process reporting joins PM_BTCH_HDR to PM_ROUT_DTL on BATCH_ID to track routing step progress.
• Quality reporting joins QC_RSLT_MST, QC_SMPL_MST, and QC_SPEC_MST on BATCH_ID to consolidate results, samples, and specifications per batch.
• Formula and routing compliance queries join out to FM_FORM_MST, FM_FORM_EFF, FM_ROUT_HDR, and GMD_ROUTINGS_B to verify which recipe and routing definitions a batch used.

Related Objects

The following represent the most significant dependencies documented in the ETRM metadata, using their actual join columns:

• PM_MATL_DTL — joined on BATCH_ID; holds batch material lines and also supplies PARENTLINE_ID.
• PM_ROUT_DTL — joined on BATCH_ID; holds batch routing detail steps.
• PM_HIST_HDR — joined on BATCH_ID; stores historical batch header information.
• PM_BTCH_PKG — linked via BULK_BATCH_ID and PKG_BATCH_ID; defines bulk-to-package batch relationships.
• QC_RSLT_MST / QC_SMPL_MST / QC_SPEC_MST — joined on BATCH_ID; provide quality results, samples, and specifications.
• FM_FORM_MST and FM_FORM_EFF — referenced through FORMULA_ID and FMEFF_ID for formula definition and effectiveness.
• GMD_ROUTINGS_B and FM_ROUT_HDR — referenced through ROUTING_ID for routing definitions.
• SY_ORGN_MST / SY_ORGN_MST_B — referenced through PLANT_CODE for organization validation.
• IC_WHSE_MST — referenced through WIP_WHSE_CODE for warehouse context.
• RH_MORD_IMP — references BATCH_ID, indicating batch linkage to process order import data.