Results for “planned_process_loss”

2 results




Overview
Explore in AI Chat

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

Overview

GMF_FORM_EFF_VW is a view owned by the APPS schema in Oracle E-Business Suite, registered as VALID and associated with the GMF (Process Manufacturing Financials) product family. It appears in ETRM documentation for both 12.1.1 and 12.2.2. Its stated purpose is that of an internal helper view supporting the Standard Cost Rollup process. It is not intended as an end-user reporting object; rather, it presents a flattened, cost-rollup-oriented projection of process manufacturing formula validity data.

The view exposes recipe-level validity rules as a form-effectivity record set, exposing a fixed CUST_ID of 0 and TRANS_CNT of 0, which signals its role as an internal staging/helper structure rather than a transactional entity. Because it is a view and not a table, it carries no unique constraints of its own; DISTINCT is used in the definition to collapse duplicates arising from the underlying joins.

Underlying Base Objects

The view is defined over three documented base objects, all accessed via synonyms:

The join condition is GR.RECIPE_ID = GRV.RECIPE_ID, with GRV.VALIDITY_RULE_STATUS = GS.STATUS_CODE. Only statuses with STATUS_TYPE in ('400','700','900') are returned, restricting the view to the status classes relevant to cost rollup processing.

Key Columns

  • RECIPE_ID — Recipe header identifier.
  • FMEFF_ID — The rule identifier renamed from RECIPE_VALIDITY_RULE_ID; acts as the effective form/validity key.
  • VALIDITY_RULE_STATUS / STATUS_TYPE — Status code and its class (400/700/900).
  • ORGN_CODE — Decoded as ORGN_CODE where present, otherwise LAB_TYPE, normalizing organization versus laboratory scope.
  • ITEM_ID / INVENTORY_ITEM_ID — Item references on the validity rule.
  • FORMULA_USE — Renamed from RECIPE_USE.
  • START_DATE / END_DATE — Effectivity window.
  • MIN_QTY, MAX_QTY, STD_QTY, INV_MIN_QTY, INV_MAX_QTY — Quantity bounds and standard quantity.
  • ITEM_UM, DETAIL_UOM — Item unit of measure and the detail unit of measure, the latter being the column referenced in the user's search term.
  • PREFERENCE, PLANNED_PROCESS_LOSS, REVISION, ORGANIZATION_ID — Costing and planning attributes.

Common Use Cases and Queries

Because it is an internal helper view, direct ad hoc querying is uncommon; however, it is useful for diagnosing cost rollup behaviour and for validating formula effectivity across organizations. Typical queries filter by recipe, organization, or validity window.

SELECT RECIPE_ID, FMEFF_ID, ORGN_CODE, ITEM_ID, DETAIL_UOM, STD_QTY, START_DATE, END_DATE FROM GMF_FORM_EFF_VW WHERE RECIPE_ID = :p_recipe_id ORDER BY START_DATE;

SELECT GR.ITEM_ID, GR.ORGN_CODE, GR.DETAIL_UOM, GR.STD_QTY FROM APPS.GMF_FORM_EFF_VW GR WHERE GR.ORGANIZATION_ID = :p_org_id AND GR.VALIDITY_RULE_STATUS = :p_status AND SYSDATE BETWEEN GR.START_DATE AND GR.END_DATE;

Note that status filtering is already constrained by the view definition, and that CUST_ID and TRANS_CNT are hard-coded placeholders. Consumers should treat the view as read-only and subject to change without notice.