Results for “formula_class”

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

Overview

FM_FORM_MST_VL is a seeded, valid PL/SQL view owned by the APPS schema within Oracle E-Business Suite, belonging to the GMD — Process Manufacturing Product Development product family. It is documented as a "Form Version view," and its purpose is to expose Oracle Forms version records maintained in the Process Manufacturing formula and recipe model. The view presents a language-specific, translated projection of formula master data, joining the base and translation layers of the formula master entity so that consumers see description text in the session's current language.

In practice, FM_FORM_MST_VL functions as the standard read-only interface through which reports, concurrent programs, integrations, and custom extensions retrieve formula version information without having to resolve the base/translation join themselves. Because it exposes the complete set of descriptive, control, and audit columns — including the DFF attribute columns and descriptive flexfield context — it is equally suitable for user-facing inquiries and for data extraction pipelines. The _VL suffix indicates that the row source is filtered by USERENV('LANG'), so results are automatically returned in the language of the connecting session.

Underlying Base Objects

Per the ETRM 12.2.2 metadata, the view is defined over two referenced base objects:

• FM_FORM_MST_B (SYNONYM) — the base table holding the formula/version master record.
• FM_FORM_MST_TL (SYNONYM) — the translation table holding the language-dependent description columns.

The view text confirms the join predicate B.FORMULA_ID = T.FORMULA_ID combined with T.LANGUAGE = USERENV('LANG'). The select list draws the majority of its columns from the base table (aliased B) and takes FORMULA_DESC1 and FORMULA_DESC2 from the translation table (aliased T). B.ROWID is surfaced as ROW_ID. Because the translation table is inner-joined, a row is returned only where a translation row exists for the session language; this is the standard Oracle multi-language ("_VL") pattern applied to seeded Process Manufacturing data.

Key Columns

The view exposes approximately 58 columns. The most frequently referenced include:

• FORMULA_DESC1 / FORMULA_DESC2 — the translated formula descriptions. FORMULA_DESC2 is the secondary description field and is a common user search target in formula inquiries.
• FORMULA_ID — the surrogate primary key linking the base and translation records; the primary join key for all related objects.
• FORMULA_NO / FORMULA_VERS — the user-visible formula number and version identifier.
• FORMULA_TYPE, SCALE_TYPE, FORMULA_CLASS, FMCONTROL_CLASS — classification and control attributes governing the formula's behaviour.
• FORMULA_STATUS, IN_USE, INACTIVE_IND, DELETE_MARK — lifecycle and usage flags used to determine active versus retired versions.
• TOTAL_INPUT_QTY, TOTAL_OUTPUT_QTY, YIELD_UOM — quantity and unit-of-measure metrics for the version.
• OWNER_ID, OWNER_ORGANIZATION_ID, MASTER_FORMULA_ID, PROJECT_ID — ownership, organization, master/child, and project references.
• ATTRIBUTE1 through ATTRIBUTE30, ATTRIBUTE_CATEGORY — descriptive flexfield segments.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.
• ROW_ID, TEXT_CODE — row identifier and descriptive text reference.

Common Use Cases and Queries

Typical uses include formula inquiry screens, version listings, integration extracts into MES or PLM systems, and ad hoc reporting against translated descriptions. The following query retrieves active versions and their descriptions:

• SELECT formula_no, formula_vers, formula_desc1, formula_desc2, formula_status FROM apps.fm_form_mst_vl WHERE inactive_ind = 0 ORDER BY formula_no, formula_vers;
• SELECT formula_id, formula_no, formula_desc2 FROM apps.fm_form_mst_vl WHERE UPPER(formula_desc2) LIKE '%BASE%';
• SELECT m.formula_no, m.formula_desc1, m.total_output_qty, m.yield_uom FROM apps.fm_form_mst_vl m WHERE m.owner_organization_id = :org_id;

Because the view enforces the session-language filter, no additional language predicate is required in consuming SQL. When the translation row for a given language is absent, the formula version will not appear; consumers requiring language-independent retrieval should query the base table FM_FORM_MST_B directly.