Results for “fm_form_mst_b_pk”

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

Overview

GMD.FM_FORM_MST_B is the formula header base table within the Oracle EBS Process Manufacturing Product Development (GMD) module. It stores the master definition of every formula (recipe) used in process manufacturing, including identification, classification, versioning, scaling, status, and ownership attributes. In Oracle EBS 12.1.1 and 12.2.2, this table serves as the central anchor for formula management, feeding downstream objects such as formula details, formula effectivity, routing, and batch execution. The _B suffix denotes the base table in a multi-table entity that typically pairs with a _TL (translation) table in EBS conventions, though this object itself carries the operative header data.

From a Data Vault modeling perspective, the metadata’s heuristic classification identifies this object as a link, since it primarily connects formulas to their control classes, text headers, and formula classes via foreign keys. Modeling-wise, it may be beneficial to treat the descriptive columns as satellite content attached to that link hub.

Key Information Stored

The table carries 60 documented columns, of which the following are most significant:

• FORMULA_ID — Surrogate primary key (FM_FORM_MST_B_PK), uniquely identifying each formula record.
• FORMULA_NO and FORMULA_VERS — Together forming the business unique key (FM_FORM_MST_B_UK), representing the formula number and its version.
• FORMULA_TYPE and SCALE_TYPE — Define the formula’s category and scaling behavior.
• FORMULA_DESC1 and FORMULA_DESC2 — Descriptive text for the formula.
• FORMULA_CLASS — Foreign key to GMD_FORMULA_CLASS_B, grouping formulas by class.
• FMCONTROL_CLASS — Foreign key to FM_FMCT_CLS, controlling formula behavior.
• TEXT_CODE — Foreign key to FM_TEXT_HDR, linking to standard text headers.
• FORMULA_STATUS — Lifecycle status of the formula.
• FORMULA_UOM and YIELD_UOM — Units of measure for formula quantities and yield.
• TOTAL_INPUT_QTY and TOTAL_OUTPUT_QTY — Aggregate quantities for the formula.
• IN_USE and INACTIVE_IND — Flags governing availability and activity.
• OWNER_ORGANIZATION_ID, ORGN_CODE, MASTER_FORMULA_ID — Organizational ownership and master-formula lineage.
• DELETE_MARK — Soft-delete indicator used throughout GMD tables.

Common Use Cases and Queries

Typical scenarios include formula master reporting, version history review, and integration with batch or costing processes. A common pattern joins the base table to its class and control lookups:

• Listing all active formulas: SELECT FORMULA_NO, FORMULA_VERS, FORMULA_STATUS FROM GMD.FM_FORM_MST_B WHERE INACTIVE_IND = 0 AND DELETE_MARK = 0;
• Resolving classification: join to GMD_FORMULA_CLASS_B on FORMULA_CLASS and to FM_FMCT_CLS on FMCONTROL_CLASS.
• Identifying the latest version per formula number using FORMULA_NO grouping and FORMULA_VERS ordering.
• Reporting totals by UOM using TOTAL_INPUT_QTY and TOTAL_OUTPUT_QTY.

Related Objects

• GMD_FORMULA_CLASS_B — referenced via FORMULA_CLASS.
• FM_FMCT_CLS — referenced via FMCONTROL_CLASS.
• FM_TEXT_HDR — referenced via TEXT_CODE.
• FM_FORM_MST_B child detail tables (formula lines/ingredients) — linked by FORMULA_ID.
• Formula effectivity and routing tables within GMD — dependent on FORMULA_ID.