Results for “formula_no”

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

Overview

PMIBV_FORMULA_LOV_V is a read-only view owned by the APPS schema in Oracle E-Business Suite. It belongs to the Process Manufacturing Intelligence (PMI) product family, which Oracle classifies as obsolete in release 12.1.1 and 12.2.2. The view provides a lightweight list-of-values (LOV) source for formula records, exposing only the three attributes required to drive a formula selection prompt: the surrogate identifier, a descriptive name, and the user-facing formula number. Because it is a view rather than a table, it stores no data of its own and inherits all rows directly from the Process Manufacturing formula master.

The view was originally consumed by PMI reporting and integration components that needed to resolve a formula_no value to its internal formula_id. In practice, most EBS implementations encounter this object only during database inventory audits or when reviewing legacy PMI customizations, since the standard Process Manufacturing forms and concurrent programs use their own LOV definitions.

Underlying Base Objects

The view is defined with a single SELECT statement over one documented base object, FM_FORM_MST, which the metadata lists as a synonym rather than a physical table reference. The definition carries the WITH READ ONLY clause, preventing DML through the view and guaranteeing that PMI and custom consumers cannot modify formula definitions through this interface.

The view text is minimal:

• SELECT FORMULA_ID, FORMULA_DESC1, FORMULA_NO FROM FM_FORM_MST WITH READ ONLY

No joins, filters, or functions are applied. Consequently, the view exposes every row present in the formula master, including formulas in any status or version. It does not restrict output to approved, active, or current-version formulas; any such filtering must be applied by the calling query through additional predicates against the base table.

Key Columns

• FORMULA_ID — The system-generated primary key of the formula record. This is the value returned to the calling form or program for storage in foreign-key columns on downstream entities such as recipes, batches, and routings.
• FORMULA_NO — The user-defined formula number, which is the value most users recognize and enter when searching. The original search term, "formula_no", resolves to this column.
• FORMULA_DESC1 — The primary description of the formula, typically used as the concatenated LOV display value alongside FORMULA_NO.

Columns such as formula version, status, and organization are not exposed. Queries that require those attributes must go against FM_FORM_MST directly.

Common Use Cases and Queries

The view is suited to validation, lookup, and reporting scenarios where a compact formula reference list is sufficient. A typical validation query checks whether a formula number entered by a user exists:

• SELECT formula_id, formula_no, formula_desc1 FROM apps.pmibv_formula_lov_v WHERE formula_no = :p_formula_no;

A reporting query may resolve stored IDs back to readable values:

• SELECT l.formula_no, l.formula_desc1 FROM apps.pmibv_formula_lov_v l WHERE l.formula_id IN (SELECT formula_id FROM apps.gme_batch_header);

Because the view predates modern PMI deprecation and performs no filtering, it should be treated as a convenience wrapper. Organizations migrating off PMI should replace references with direct queries against FM_FORM_MST, applying appropriate status and version predicates to avoid returning obsolete formula definitions.