Search Results validity_rule_status

Overview

The APPS.FM_FORM_EFF_VW3 view is a reporting and integration construct within the Oracle E-Business Suite Process Manufacturing Product Development (GMD) module. It presents a consolidated, date-effective projection of formula and recipe validity rules, joining recipe header information to the status definitions that govern those rules. The view exposes a single logical row for each distinct combination of recipe, validity rule, status, and associated quantity or organization attributes, making it suitable for downstream reporting, interface extraction, and programmatic lookups.

The view is particularly relevant to consumers searching on the term "validity_rule_status," because that column is central to its join logic and its business meaning. VALIDITY_RULE_STATUS carries the status code that qualifies whether a given recipe validity rule is active, pending, or otherwise categorized, and it is resolved against the status master to yield the STATUS_TYPE classification. In EBS 12.1.1 and 12.2.2, this view is documented as VALID under the APPS schema and remains a stable reference point for both custom reports and standard GMD functionality that requires a pre-joined, status-annotated view of recipe validity.

Underlying Base Objects

FM_FORM_EFF_VW3 is defined over three documented base objects, all referenced through APPS synonyms: GMD_RECIPES_B, GMD_RECIPE_VALIDITY_RULES, and GMD_STATUS_B. The recipe validity rules table is the driving table of the view, supplying the primary business content, including dates, quantities, preferences, and the VALIDITY_RULE_STATUS code. GMD_RECIPES_B provides the recipe header context, contributing RECIPE_ID as well as the ROUTING_ID and FORMULA_ID linkage. GMD_STATUS_B is joined to translate the stored status code into a STATUS_TYPE, using the predicate GRV.VALIDITY_RULE_STATUS = GS.STATUS_CODE.

The join between GMD_RECIPE_VALIDITY_RULES and GMD_RECIPES_B is keyed on RECIPE_ID. The view text also includes DECODE logic on ORGN_CODE, substituting LAB_TYPE when the organization code is null, which reflects the shared laboratory and plant organization model used in process manufacturing. The DISTINCT clause removes duplicate combinations arising from the status join. Two columns, CUST_ID and TRANS_CNT, are exposed as literal zero values, indicating they exist for interface compatibility rather than as stored data.

Key Columns

• RECIPE_ID — Identifier of the parent recipe from GMD_RECIPES_B.
• FMEFF_ID — Aliased from RECIPE_VALIDITY_RULE_ID; the unique key of the validity rule record.
• VALIDITY_RULE_STATUS — The status code qualifying the rule; the object of the user's search.
• STATUS_TYPE — Status classification derived from GMD_STATUS_B.
• ORGN_CODE — Organization code, defaulting to LAB_TYPE when the organization code is null.
• ITEM_ID / INVENTORY_ITEM_ID — Item identifiers associated with the validity rule.
• FORMULA_USE — Aliased from RECIPE_USE, indicating the intended use of the formula.
• START_DATE / END_DATE — Effective period during which the validity rule applies.
• MIN_QTY, MAX_QTY, STD_QTY, INV_MIN_QTY, INV_MAX_QTY — Quantity boundaries governing the rule.
• ITEM_UM / DETAIL_UOM — Units of measure for the associated quantities.
• PREFERENCE — Preference ranking for rule selection.
• ROUTING_ID / FORMULA_ID — Routing and formula references from the recipe header.
• REVISION, ORGANIZATION_ID, PLANNED_PROCESS_LOSS — Additional process manufacturing attributes.
• Audit columns — CREATION_DATE, LAST_UPDATE_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, DELETE_MARK, TEXT_CODE.

Common Use Cases and Queries

Typical uses include identifying active formula validity rules for a recipe, reporting on status distribution across recipes, and feeding integration extracts with date-effective rule data. A common query filters on status and effective dates:

• SELECT recipe_id, fmeff_id, validity_rule_status, status_type, item_id, start_date, end_date FROM apps.fm_form_eff_vw3 WHERE validity_rule_status = 'ACTIVE';
• SELECT recipe_id, COUNT(*) FROM apps.fm_form_eff_vw3 WHERE TRUNC(SYSDATE) BETWEEN start_date AND end_date GROUP BY recipe_id;
• SELECT validity_rule_status, status_type, COUNT(*) FROM apps.fm_form_eff_vw3 GROUP BY validity_rule_status, status_type;

Because the view already resolves status types and applies DISTINCT, it simplifies ad hoc reporting that would otherwise require repeated joins across the three base tables.