Results for “formula_no”

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

Overview

FM_FORM_MST_V1 is a database view owned by the APPS schema in Oracle E-Business Suite, classified under the GMD product family — Process Manufacturing Product Development. Its documented description is "Formula Numbers View." As the name and definition imply, the view presents a deduplicated list of formula numbers drawn from the formula master data maintained by Oracle Process Manufacturing (OPM). It contains a single column, FORMULA_NO, and exposes no other attributes of the formula record.

Within the Oracle EBS reporting and integration layer, FM_FORM_MST_V1 functions as a lightweight lookup object rather than a full transactional view. Users and developers searching on the term "formula_no" typically encounter this view while looking for a canonical list of valid formula identifiers — for example, to populate a list of values, drive a validation query, or join an external report to the OPM formula catalog without pulling the entire FM_FORM_MST row set. Because the view filters out logically deleted records, it returns only formulas that remain active in the master table.

Underlying Base Objects

The view is defined over a single referenced base object, documented as FM_FORM_MST (exposed through a synonym in the APPS schema). FM_FORM_MST is the OPM Formula Master table, which holds the header-level attributes of each formula, including its formula number, version, ownership, and status. The view text documented in the ETRM metadata is:

• SELECT DISTINCT FORMULA_NO FROM FM_FORM_MST WHERE DELETE_MARK = 0

Two characteristics of this definition are significant. First, the DELETE_MARK = 0 predicate implements Oracle's standard soft-delete convention: rows flagged with DELETE_MARK = 1 are considered removed and are excluded from the view. Second, the DISTINCT keyword collapses the potential for multiple rows per formula number. In FM_FORM_MST, a formula may exist in more than one version, so a naive select of FORMULA_NO could return duplicates; the view guarantees one row per distinct formula number. Because the view references only the header table, it carries no dependency on formula detail, routing, or validity rule tables.

Key Columns

The view exposes exactly one column:

• FORMULA_NO — the formula number, the business-facing identifier assigned to a formula in OPM. In FM_FORM_MST this is the primary business key used throughout the formula lifecycle, including formula versioning, batch creation, and cost rollups. In this view it is presented as a unique, non-deleted value suitable for use as a lookup key or join predicate.

No version number, description, status, or organizational attribute is exposed. Consumers requiring those details must join back to FM_FORM_MST or to companion views on the same key.

Common Use Cases and Queries

Typical scenarios include populating a concurrent program parameter list of values, validating a formula number supplied by an external system, and building a distinct count of active formulas. A simple retrieval of all active formula numbers follows:

• SELECT FORMULA_NO FROM APPS.FM_FORM_MST_V1 ORDER BY FORMULA_NO;

To restrict to a known set, a bind-based filter is preferred: SELECT FORMULA_NO FROM APPS.FM_FORM_MST_V1 WHERE FORMULA_NO = :p_formula_no;

Because the view returns only the identifier, reports needing descriptive or version-level context should join to the base table, for example: SELECT v.FORMULA_NO, m.FORMULA_DESC, m.FORMULA_STATUS FROM APPS.FM_FORM_MST_V1 v, APPS.FM_FORM_MST m WHERE v.FORMULA_NO = m.FORMULA_NO AND m.DELETE_MARK = 0;

For integration, the view is well suited as a source in interface staging loads where only the master list of live formula numbers is required, reducing data volume and eliminating soft-deleted records without additional filtering logic. Developers should note that the DISTINCT operation carries a small sorting cost on large formula catalogs, but given the narrow projection the overhead is minimal.