Search Results frmty_lkp

Overview

PMITS_FORMULA_MASTER_V is an APPS-owned reporting view in the Process Manufacturing Intelligence (PMI) module of Oracle E-Business Suite. It is described in the ETRM metadata as the "GMD Formula Master View." Its purpose is to expose a denormalized, human-readable projection of process manufacturing formulas by joining the master formula table to lookup, status, class, organization, and user reference data. Rather than requiring report authors to resolve coded values against multiple lookup and master tables, the view resolves those codes into descriptive meanings at query time.

The view is validated and available in both 12.1.1 and 12.2.2. It carries an embedded security predicate through PMI_SECURITY_PKG.SHOW_RECORD, which filters rows so that only organizations the current user is authorized to see are returned. This makes the view suitable for secured reporting, analytics, and integration extracts where formula master data must be presented with resolved descriptive attributes.

Underlying Base Objects

The view text joins the following documented base objects:

• FM_FORM_MST_VL — the formula master base table (aliased FMV), supplying the core formula attributes.
• FND_USER — supplies OWNER and OWNER_DESC from USER_NAME and DESCRIPTION.
• GMD_STATUS — supplies STATUS from STATUS_CODE.
• FM_FORM_CLS — supplies FORMULA_CLASS_DESC; joined with an outer join (+).
• SY_ORGN_MST — supplies ORGN_DESC from ORGN_NAME.
• GEM_LOOKUPS — used three times (aliases FRMTY_LKP, ACTND_LKP, SCATY_LKP) to resolve FORMULA_TYPE, INACTIVE_IND, and SCALE_TYPE against lookup type GME_YES_NO.

The ETRM metadata lists DUAL (a synonym) among the referenced base objects, reflecting the dictionary-level dependency capture. The join conditions tie formulas to their owner, status, class, and organization, and resolve each coded attribute through the GEM_LOOKUPS reference set.

Key Columns

• FORMULA_ID, FORMULA_NO, FORMULA_VERS — formula identifier, number, and version.
• FORMULA_DESC1, FORMULA_DESC2 — descriptive text for the formula.
• FORMULA_TYPE, SCALE_TYPE, INACTIVE_IND — resolved MEANING values from the GME_YES_NO lookup type.
• FORMULA_CLASS, FMCONTROL_CLASS, FORMULA_CLASS_DESC — formula class code and its description.
• FORMULA_STATUS, STATUS — status code and its resolved meaning.
• ORGN_CODE, ORGN_DESC — organization code and name.
• OWNER_ID, OWNER, OWNER_DESC — owner user identifier, user name, and description.
• TOTAL_INPUT_QTY, TOTAL_OUTPUT_QTY, FORMULA_UOM — aggregate input/output quantities and the unit of measure.
• TEXT_CODE, DELETE_MARK, PROJECT_ID — standard descriptive-flexfield, soft-delete, and project references.

The recurring GME_YES_NO lookup type is the connecting thread for the type, scale, and inactive-indicator columns, which is directly relevant to the searched term "gme_yes_no."

Common Use Cases and Queries

Typical uses include formula master listings, organization-scoped formula reports, and extracts that feed downstream analytics. The security predicate means results automatically reflect the querying user's organization access.

SELECT formula_no, formula_vers, formula_desc1,
       formula_type, scale_type, status, orgn_desc, owner
FROM   apps.pmits_formula_master_v
WHERE  inactive_ind = 'No'
ORDER  BY formula_no, formula_vers;

To analyze formula classification and ownership:

SELECT formula_class_desc, COUNT(*) formula_count
FROM   apps.pmits_formula_master_v
WHERE  delete_mark = 0
GROUP  BY formula_class_desc;

Because the view already resolves GME_YES_NO meanings, report authors should filter on the descriptive MEANING values rather than underlying lookup codes, simplifying query construction for process manufacturing formula reporting.