Results for “exploded_by”

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

Overview

The FM_IBOM_HDR table resides in the GMD schema and belongs to the Process Manufacturing Product Development module in Oracle E-Business Suite 12.1.1 and 12.2.2. It functions as a header table that stores the driving parameters and runtime state for the Indented Bill Of Materials report, a process-manufacturing reporting utility that explodes a formula structure into its component ingredients and outputs a hierarchical BOM view. Rather than holding the formula definition itself, the table persists the user-selected formula, the run-time explosion options, and the result-state flags that the report relies on when reconstructing the indented hierarchy.

The primary key is FM_IBOM_HDR_PK, defined on the single column TOP_FORMULA_ID, which uniquely identifies each header record for a top-level (parent) formula. Because the table stores the header context of a report execution rather than a durable business entity with rich descriptive attributes, it carries no documented foreign-key relationships and is classified under the heuristic Data Vault model as a standalone object. In Data Vault terms this suggests treating it as a candidate satellite whose hub key is the formula identity (TOP_FORMULA_ID) rather than a true hub of its own, since it holds attributes describing a specific reporting context.

Key Information Stored

The documented physical schema for release 12.2.2 lists 25 columns. The columns most relevant to functionality and reporting are:

• TOP_FORMULA_ID — the surrogate primary key and the sole unique business-key candidate (via FM_IBOM_HDR_PK); identifies the top formula being exploded.
• ITEM_ID and INVENTORY_ITEM_ID — the item associated with the top formula; these link the header back to the inventory item master.
• FORMULA_QTY, REPORT_QTY, and DISPLAY_QTY — quantity values governing how the formula is scaled for reporting and how much is shown.
• REPORT_UOM — the unit of measure used for the reported quantity.
• SCALE_PERCENT and SCALE_ALLOWED — control whether and by what percentage the formula may be scaled during explosion.
• FORMULA_USE — the usage context of the formula (for example, production versus costing).
• EFFECTIVITY_DATE — the date from which the formula is effective.
• MAX_EXPLODE_LEVELS — the maximum depth to which the indented BOM is exploded.
• EXPLODE_IND — flag indicating whether explosion is enabled for the run.
• USE_INACTIVE_FLAG — controls whether inactive components are included.
• EXPLODED_BY and EXPLODED_DATE — capture who ran the explosion and when.
• STATUS_CODE — the processing or result status of the header record.
• ORGN_CODE, ORGANIZATION_ID, and VALIDITY_ORGANIZATION_TYPE — the organization context and validity scope for the explosion.
• Standard audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN provide who/when tracking.

The surrogate key TOP_FORMULA_ID is the only documented unique index, so it doubles as the business-key candidate in the absence of a wider composite unique constraint.

Common Use Cases and Queries

Typical scenarios include retrieving the report parameters for a completed indented BOM run, auditing which formulas were exploded by which users, and feeding downstream cost or ingredient-reconciliation reports. A representative query to inspect recent explosions for an organization is:

SELECT h.top_formula_id, h.item_id, h.formula_qty,
       h.report_qty, h.report_uom, h.exploded_by, h.exploded_date, h.status_code
  FROM   gmd.fm_ibom_hdr h
 WHERE  h.organization_id = :org_id
   AND  h.exploded_date  >= :from_date
 ORDER BY h.exploded_date DESC;

A join back to formula and item masters confirms the top formula being expanded:

SELECT h.top_formula_id, f.formula_no, h.effectivity_date, h.max_explode_levels
  FROM   gmd.fm_ibom_hdr h, gmd.fm_form_mst f
 WHERE  h.top_formula_id = f.formula_id;

Reporting teams also use EFFECTIVITY_DATE, USE_INACTIVE_FLAG, and SCALE_ALLOWED to reconstruct the exact option set that produced a historical BOM report, ensuring reproducibility.

Related Objects

Although the metadata classifies FM_IBOM_HDR as standalone with no documented foreign keys, functionally it participates with the following process-manufacturing objects:

• FM_FORM_MST — the formula master, joined on FORMULA_ID = TOP_FORMULA_ID, supplying the formula header.
• FM_MATL_DTL — formula material detail, linked through the formula identity to enumerate components.
• FM_FORM_EFF — formula effectivity records that qualify which formula version applies.
• MTL_SYSTEM_ITEMS_B — inventory item master, joined on INVENTORY_ITEM_ID or ITEM_ID.
• MTL_UNITS_OF_MEASURE — resolves REPORT_UOM for display.
• HR_ALL_ORGANIZATION_UNITS / ORG_ORGANIZATION_DEFINITIONS — resolve ORGANIZATION_ID and ORGN_CODE.
• FND_USER — resolves EXPLODED_BY and audit columns to user names.

These joins are inferred from functional dependency rather than declared constraints, reflecting the table's role as a report-support object within Process Manufacturing Product Development.