Results for “formula_vers”

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

Overview

FM_FORM_MST_V2 is a database view owned by the APPS schema in Oracle E-Business Suite, defined within the Process Manufacturing Product Development (GMD) product family. Its documented purpose is to expose formula version information, as reflected in its ETRM description, "Formula Version View." The view stores no data of its own; it serves purely as a read-only projection over the formula master data maintained in the base table FM_FORM_MST. The object carries a status of VALID in the documented environment, indicating it is compiled and available for use.

The view's primary functional role is to present a de-duplicated list of formula versions. Its definition applies SELECT DISTINCT to the FORMULA_VERS column and filters out rows marked for deletion, ensuring that consumers receive only active, unique version values. Because formula versions are the identifiers by which process manufacturers distinguish successive iterations of a product formulation, this view provides a convenient lookup layer for reporting, list-of-values population, and integration logic that needs to enumerate available versions without retrieving the full formula master record.

Underlying Base Objects

According to the documented metadata for ETRM 12.2.2, FM_FORM_MST_V2 is defined over a single referenced base object: FM_FORM_MST, accessed through a synonym. FM_FORM_MST is the formula master table in the GMD schema lineage, holding one record per formula version along with associated attributes such as formula ownership, status, and the DELETE_MARK soft-delete indicator.

The relationship between the view and its base table is direct and one-directional. No joins are present in the view text; there are no outer joins, unions, or subqueries. The view therefore inherits its column semantics entirely from FM_FORM_MST. The WHERE clause predicate DELETE_MARK = 0 restricts output to rows that have not been logically deleted, while the DISTINCT operator collapses the many-to-one relationship between formula records and version identifiers into a unique set. The same definition is documented for both Oracle EBS 12.1.1 and 12.2.2, indicating the view is stable across those releases.

Key Columns

• FORMULA_VERS — The sole column exposed by the view. It represents the formula version identifier, the value that distinguishes one revision of a formulation from another. Because the view is defined with SELECT DISTINCT over this column, every row returned carries a unique formula version value.

The narrow column footprint is deliberate. The view is not intended to supply descriptive attributes of a formula; those reside in FM_FORM_MST and in related formula detail tables. Instead, it functions as a distinct-value source for the version identifier itself, which simplifies downstream queries that would otherwise require explicit DISTINCT and soft-delete filtering against the base table.

Common Use Cases and Queries

Typical scenarios include populating a version selection list on a concurrent program parameter or OAF page, validating a version value supplied by an external integration, and producing counts or reports of active formula versions. A minimal retrieval query follows:

• SELECT FORMULA_VERS FROM APPS.FM_FORM_MST_V2;
• SELECT FORMULA_VERS FROM APPS.FM_FORM_MST_V2 WHERE FORMULA_VERS LIKE :p_vers_prefix;
• SELECT COUNT(*) FROM APPS.FM_FORM_MST_V2;

Because the view already enforces DELETE_MARK = 0 and DISTINCT, callers need not repeat that logic. When additional formula attributes are required, the view is commonly joined back to FM_FORM_MST on FORMULA_VERS, or replaced by a direct query against the base table with the appropriate columns selected. Users searching for "formula_vers" will find this view to be the most direct, documented access path to distinct active formula version values within the GMD module.