Results for “tpformula_id”

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

Overview

LM_FORM_DTL is a table in the GMD schema (Process Manufacturing Product Development) within Oracle E-Business Suite 12.1.1 and 12.2.2. The ETRM documentation marks the object as OBSOLETE as of 11.5.6 (OPM PF.G), meaning it is a legacy construct retained in the schema for backward compatibility rather than an actively maintained transactional table in current releases. Historically it served as the formula detail line table — the child entity that stored the individual component lines (items, quantities, units of measure, scaling and cost-allocation attributes) belonging to a formula header.

Functionally, the table played the role of a dependent detail table sitting beneath a formula master record, carrying one row per formula line. From a dimensional-modeling perspective, the FK topology (multiple parent references from this table outward, and a downstream child table pointing back to it) suggests a satellite-leaning classification: the surrogate key identifies the line, while descriptive and quantitative attributes describe the state of that line at a point in time. This classification is offered as a heuristic modeling suggestion, not a documented Oracle designation.

Key Information Stored

The table is documented with 51 columns. The most significant are:

• FORMULALINE_ID — the surrogate primary key, backed by the unique index LM_FORM_DTL_PK. This is the single-column business/technical key for a formula line.
• FORMULA_ID — foreign key to LM_FORM_MST, identifying the parent formula header.
• TPFORMULA_ID — a second reference to LM_FORM_MST, typically linking a "text/placeholder" or alternate formula representation.
• LINE_NO — the ordinal position of the line within the formula, a common alternate (business) key candidate alongside FORMULA_ID.
• LINE_TYPE — distinguishes the nature of the line (for example, ingredient, by-product, or text line).
• ITEM_ID — foreign key to IC_ITEM_MST, the inventory item consumed or produced.
• QTY and ITEM_UM — the required quantity and its unit of measure, with ITEM_UM referencing SY_UOMS_MST.
• SCALE_TYPE and SCALE_FACTOR (SCRAP_FACTOR and related scaling attributes such as PHANTOM_TYPE, REWORK_TYPE, RELEASE_TYPE) — control how the line scales, scraps, or releases during formula explosion.
• COST_ALLOC — allocation percentage used in cost rollup.
• TEXT_CODE — foreign key to LM_TEXT_HDR, linking narrative text to the line.
• Standard audit columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, plus ATTRIBUTE1–ATTRIBUTE30 and ATTRIBUTE_CATEGORY for descriptive flexfield storage.

Common Use Cases and Queries

Because the table is obsolete, current development should avoid new dependencies. Where legacy reporting or migration is required, the typical pattern joins the line to its formula header and item master:

• Retrieve all lines for a formula: SELECT * FROM GMD.LM_FORM_DTL WHERE FORMULA_ID = :formula_id ORDER BY LINE_NO;
• Resolve line items to descriptions: join LM_FORM_DTL.ITEM_ID = IC_ITEM_MST.ITEM_ID.
• Reconcile against header masters: join LM_FORM_DTL.FORMULA_ID = LM_FORM_MST.FORMULA_ID.
• Locate lines by narrative: join TEXT_CODE to LM_TEXT_HDR.
• Audit trailing-attribute usage via ATTRIBUTE_CATEGORY and ATTRIBUTE1–30.

Related Objects

• LM_FORM_MST — formula header; referenced twice (FORMULA_ID, TPFORMULA_ID).
• IC_ITEM_MST — item master; via ITEM_ID.
• SY_UOMS_MST — unit of measure validation; via ITEM_UM.
• LM_TEXT_HDR — text/narrative header; via TEXT_CODE.
• LM_FORM_DAT — dependent table referencing this table through FORMULALINE_ID.