Search Results pmifv_formula_summary_v




Overview
Explore in AI Chat

Overview

The APPS.PMIFV_FORMULA_SUMMARY_V view is a reporting construct within the Oracle E-Business Suite Process Manufacturing Intelligence (PMI) module, identified in ETRM metadata as obsolete but still present and VALID in environments running 12.1.1 and 12.2.2. The view consolidates master formula definition attributes, effectivity records, and associated routing information into a single denormalized result set. Crucially, and as stated in the object description, it does not contain ingredient (formula detail line) information; it presents the product and effectivity information for a formula including routing information. This makes the view a rapid reference for formula headers, their plant and organization effectivity windows, and the routing tied to each effectivity record, without the cost of joining and aggregating ingredient lines.

The view fulfills a typical PMI role: providing a security-filtered, code-resolved read model suitable for reporting, dashboards, and downstream integration. It is read-only and depends on several package calls to resolve lookup meanings and enforce organization security at query time.

Underlying Base Objects

The view is defined in the APPS schema and is built over the following documented base objects:

  • FM_FORM_MST (FMASTER) — the formula master record, supplying formula number, version, type, scale type, class, descriptions, and audit columns. This is the driving table of the join.
  • FM_FORM_EFF (EFFECTIVITY) — formula effectivity rows, providing organization, item, routing, customer, quantity ranges, and start/end dates.
  • IC_ITEM_MST (PRODUCT) — inventory item master, supplying the product item number and descriptions.
  • OP_CUST_MST (CUSTOMER) — customer master, supplying customer number and name for customer-specific effectivity.
  • FM_ROUT_HDR (ROUTING) — routing header, supplying routing number, version, description, class, quantity, and unit of measure.
  • SY_ORGN_MST (SECORG) — organization master used inside the inline security subquery.

Two packages are referenced. PMI_COST_ANALZ_PACK.GMCA_GET_MEANING resolves the GMD_FORMULA_USE lookup for both the formula type and the effectivity formula use. PMI_SECURITY_PKG.SHOW_RECORD restricts the result set by organization, so users only see effectivity rows for organizations to which they have access.

Key Columns

Common Use Cases and Queries

A frequent requirement, and the one implied by the search term gmd_formula_use, is reporting formulas by their intended use together with their effectivity and routing. A representative query follows:

  • SELECT formula_no, formula_vers, formula_type, item_no, orgn_code, routing_no, start_date, end_date FROM apps.pmifv_formula_summary_v WHERE formula_type = 'PRODUCTION' ORDER BY formula_no, orgn_code;
  • SELECT item_no, item_desc1, routing_no, cust_no, start_date, end_date FROM apps.pmifv_formula_summary_v WHERE orgn_code = 'M1' AND TRUNC(SYSDATE) BETWEEN start_date AND end_date;
  • SELECT formula_no, formula_vers, preference, min_qty, max_qty, std_qty FROM apps.pmifv_formula_summary_v WHERE item_id = :p_item_id ORDER BY preference;

Because ingredient data is deliberately excluded, users requiring component-level detail must join to the formula detail tables separately. The organization security predicate is applied internally, so direct queries from a reporting schema should generally be executed in an APPS-initialized session to ensure the security package and profile context resolve correctly.