Search Results formula_pk
Overview
The database object EDW_PMI_PFRM_PFRM_LCV is a reporting view associated with the Process Manufacturing Intelligence (PMI) product family in Oracle E-Business Suite. It belongs to the Enterprise Data Warehouse (EDW) layer, as indicated by the EDW_ prefix, and follows the naming convention of a "List of Values" (LOV) view, denoted by the _LCV suffix. Its primary purpose is to present a flattened, denormalized list of process manufacturing formulas that can be consumed by PMI analytics, dashboards, and downstream integration extracts.
The view is explicitly marked as Obsolete in the ETRM 12.2.2 metadata, and the documentation records that the object is Not implemented in this database. This means that although the view text and column definitions are documented, the object may not exist as a deployed database view in a standard 12.1.1 or 12.2.2 environment. It should therefore be treated as a reference artifact for legacy PMI implementations rather than a supported reporting interface in current releases.
Underlying Base Objects
The view text is defined over two base objects:
- FM_FORM_MST — the Process Manufacturing formula master table, aliased as F, which supplies the formula number, version, description, class, and audit dates.
- EDW_LOCAL_INSTANCE — an EDW local instance reference table, aliased as I, which supplies the INSTANCE_CODE value that identifies the source instance.
The documented metadata states that referenced base objects are "none documented," reflecting the obsolete status. Nonetheless, the view SQL clearly joins FM_FORM_MST to EDW_LOCAL_INSTANCE without an explicit join condition, producing a cross-product that stamps each formula row with the local instance code. Within the broader PMI schema, this formula data also normally relates to FM_FORM_MST_B (formula details), FM_FORM_EFF (formula effects), and FM_MATL_DTL, though these are not part of the view definition itself.
Key Columns
- ALL_FK — a literal constant 'ALL', used as a surrogate foreign key for LOV "select all" behavior.
- FORMULA_PK — the concatenated primary key formed as FORMULA_NO || '-' || FORMULA_VERS || '-' || INSTANCE_CODE || '-OPM'. This is the column most relevant to the user's search term "formula_pk."
- FORMULA_NUMBER — the formula number from FM_FORM_MST.
- VERSION — the formula version (FORMULA_VERS).
- DESCRIPTION — the formula description (FORMULA_DESC1).
- FORMULA_CLASS — the classification of the formula.
- FORMULA_DP and NAME — both expressed as FORMULA_NO || ':' || FORMULA_VERS, providing a display and name representation.
- INSTANCE_CODE — the source instance identifier from EDW_LOCAL_INSTANCE.
- LAST_UPDATE_DATE and CREATION_DATE — standard audit columns.
- USER_ATTRIBUTE1–5 — placeholder descriptive flexfield columns, all returned as NULL.
Common Use Cases and Queries
Because the view is obsolete and not implemented, practical use is limited to historical PMI reporting or migration analysis. Where the object exists, it is typically queried to populate formula LOVs or to resolve a FORMULA_PK back to its components. Example:
- Formula LOV lookup:
SELECT FORMULA_PK, NAME FROM EDW_PMI_PFRM_PFRM_LCV WHERE FORMULA_NUMBER LIKE :p_no; - Decompose a surrogate key:
SELECT FORMULA_NUMBER, VERSION, INSTANCE_CODE FROM EDW_PMI_PFRM_PFRM_LCV WHERE FORMULA_PK = :p_pk; - Instance-scoped listing:
SELECT FORMULA_NUMBER, VERSION, DESCRIPTION, FORMULA_CLASS FROM EDW_PMI_PFRM_PFRM_LCV WHERE INSTANCE_CODE = :p_inst ORDER BY FORMULA_NUMBER;
In 12.1.1 and 12.2.2 environments, equivalent current functionality is generally delivered through supported PMI or OPM formula views, so the legacy object should not be relied upon for new development.
-
View: EDW_PMI_PFRM_PFRM_LCV
12.1.1
product: PMI - Process Manufacturing Intelligence , implementation_dba_data: Not implemented in this database ,
-
View: EDW_PMI_PFRM_PFRM_LTC_IV
12.1.1
product: PMI - Process Manufacturing Intelligence , implementation_dba_data: Not implemented in this database ,
-
Table: EDW_PMI_PFRM_PFRM_LTC
12.1.1
product: PMI - Process Manufacturing Intelligence , implementation_dba_data: Not implemented in this database ,