Search Results gmd_formula_use




Overview

APPS.PMIFV_FORMULA_SUMMARY_V is a read-only security-aware view in the Oracle E-Business Suite Process Manufacturing (OPM) module. It presents a consolidated, denormalized summary of formula master records joined to their effectivity definitions, associated products, customers, and routings. The "PMIFV" prefix identifies it as part of the Process Manufacturing Inventory/Formula family of views, while the "_SUMMARY_V" suffix indicates it is intended as a reporting and integration surface rather than a base transaction entity.

Because the view is defined with a WITH READ ONLY clause, it cannot be used for DML. It is consumed by forms, concurrent programs, BI Publisher reports, and inbound/outbound interfaces that need a single flattened row per formula effectivity without manually reconstructing the multi-table join. The view is particularly notable for resolving code lookups inline via PMI_COST_ANALZ_PACK.GMCA_GET_MEANING, so consumers receive human-readable meanings for the GMD_FORMULA_USE lookup rather than raw codes. Row-level organization security is enforced through PMI_SECURITY_PKG.SHOW_RECORD.

Underlying Base Objects

The view is defined over five synonyms that resolve to OPM base tables, joined through outer joins so that a formula master row survives even when no effectivity, product, customer, or routing match exists:

  • FM_FORM_MST (fmaster) — formula master. Filtered by INACTIVE_IND = 0 and DELETE_MARK = 0.
  • FM_FORM_EFF (effectivity) — formula effectivity/use records, joined on FORMULA_ID. Filtered by DELETE_MARK = 0.
  • IC_ITEM_MST (product) — inventory item master, joined on ITEM_ID.
  • OP_CUST_MST (customer) — customer master, joined on CUST_ID.
  • FM_ROUT_HDR (routing) — routing header, joined on ROUTING_ID.
  • SY_ORGN_MST (secorg) — organization master, used in the security subquery.
  • PMI_COST_ANALZ_PACK — package supplying GMCA_GET_MEANING for lookup translation.
  • PMI_SECURITY_PKG — package supplying SHOW_RECORD for organization-level row filtering.
  • FND_PROFILE — referenced by the security package, listed as a documented base object via its profile dependencies.

Key Columns

The view exposes formula-level, effectivity-level, and resolved descriptive attributes:

Common Use Cases and Queries

The view is typically queried when a user searches for gmd_formula_use, because the FORMULA_USE code and its translated meaning are the primary lookup dimension for formula applicability (for example, production, costing, or quality usage). A standard query lists active formulas with their effectivity and product context:

  • SELECT FORMULA_NO, FORMULA_VERS, FORMULA_DESC1, ORGN_CODE, ITEM_NO, FORMULA_USE, START_DATE, END_DATE FROM APPS.PMIFV_FORMULA_SUMMARY_V WHERE ORGN_CODE = :org AND SYSDATE BETWEEN START_DATE AND NVL(END_DATE, SYSDATE);
  • SELECT FORMULA_ID, FORMULA_NO, CUST_NO, ROUTING_NO, STD_QTY, ITEM_UM FROM APPS.PMIFV_FORMULA_SUMMARY_V WHERE FORMULA_NO = :formula;
  • Reporting formula effectivity by customer or routing, since those combinations drive plant scheduling and cost rollups.
  • Feeding interface or migration extracts where the resolved meanings are required inline rather than through a secondary lookup query.

Because organization security is applied via PMI_SECURITY_PKG.SHOW_RECORD, results are automatically constrained to the organizations the connected user is authorized to see, making the view suitable for direct exposure in self-service reports without additional security predicates.