Search Results fm_form_mst_b




Overview

The FM_FORM_MST_B table is a core data object within Oracle E-Business Suite (EBS) Process Manufacturing (GMD) Product Development module. It functions as the primary base table for storing formula header information. A formula in Process Manufacturing defines the list of ingredients, their quantities, and the processing instructions required to manufacture a specific product or co-product. As the header table, FM_FORM_MST_B holds the master definition and control attributes for each formula, serving as the central reference point for all associated details like lines, steps, and text. Its integrity is critical for production planning, material requirement calculations, and product costing.

Key Information Stored

The table's structure is designed to uniquely identify and manage formula revisions. The primary key is FORMULA_ID, a unique system-generated identifier. A separate unique key constraint ensures the business key combination of FORMULA_NO (the formula number) and FORMULA_VERS (the formula version) is also unique, allowing for precise tracking of revisions. Other significant columns include FORMULA_CLASS, which categorizes the formula (e.g., by product type or process), and FMCONTROL_CLASS, which links to a control class defining quality and processing rules. The TEXT_CODE column provides a link to descriptive text and instructions stored in the FM_TEXT_HDR table. Additional columns typically store status, effective dates, owner, and other control attributes governing the formula's lifecycle and usage.

Common Use Cases and Queries

This table is central to formula inquiry, reporting, and integration. Common operational queries involve retrieving active formulas for a given item or product line, listing all versions of a specific formula, or identifying formulas pending approval. For reporting, it is frequently joined to item and inventory tables to analyze formula coverage or to costing tables for valuation. A typical pattern for fetching the latest approved version of a formula would be:

  • SELECT f.formula_no, f.formula_vers, f.description, c.formula_class_desc
  • FROM fm_form_mst_b f, gmd_formula_class_b c
  • WHERE f.formula_class = c.formula_class
  • AND f.formula_status = '700' -- Approved status
  • AND (f.formula_no, f.formula_vers) IN (
  • SELECT formula_no, MAX(formula_vers)
  • FROM fm_form_mst_b
  • WHERE formula_status = '700'
  • GROUP BY formula_no
  • );

Data fixes or mass updates, though rare, might target status or effective dates via the FORMULA_ID or the FORMULA_NO/FORMULA_VERS combination.

Related Objects

FM_FORM_MST_B has defined relationships with several key tables, as indicated by its foreign keys. It references GMD_FORMULA_CLASS_B for formula classification and FM_FMCT_CLS for control class details. The link to FM_TEXT_HDR provides access to associated long text descriptions. Crucially, FM_FORM_MST_B is the parent table for numerous detail tables, most importantly FM_FORM_MST_TL for translated descriptions and FM_MATL_DTL for the formula's ingredient lines. It is also referenced by tables storing routing and operational details. For application development, custom queries and integrations should use the FORMULA_ID for joins to ensure accuracy across all related data.