Results for “rounding_direction”

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

Overview

GMF_MATERIAL_EFFECTIVITIES_VW1 is a helper view owned by the APPS schema in Oracle E-Business Suite, belonging to the GMF – Process Manufacturing Financials product family. In EBS 12.1.1 and 12.2.2 it is documented as a "helper view for Item substitution for costing." Its principal role is to resolve, for each formula material line, which item actually participates in a costing calculation when substitutions are permitted. Rather than presenting a flat material list, the view applies a ranking function to select a single effective row per formula line, so that downstream costing engines and custom reports see one qualified item per line instead of the full set of candidate substitutions.

The view surfaces material effectivity attributes such as quantity, unit of measure, scrap and yield contribution, allocation, and scaling behaviour, together with substitution quantities (SUB_ORIGINAL_QTY, SUB_REPLACE_QTY) and validity dates. Its status is VALID, confirming it is a supported, queryable object.

Underlying Base Objects

The view is defined over a single documented base object: GMD_MATERIAL_EFFECTIVITIES_VW, itself a view in the GMF material effectivity family. The definition carries the predicate WHERE 1 = 1, a conventional no-op filter that keeps the view open to substitution or predicate injection, and layers a window function over the base view:

• RANK() OVER (PARTITION BY FORMULA_ID, LINE_TYPE, LINE_NO ORDER BY ORIGINAL_ITEM_FLAG, PREFERENCE) RK — ranks candidate material rows within each formula line, preferring the original item (ORIGINAL_ITEM_FLAG) and then the substitution preference order defined on the base view.
• All other columns are passed through unchanged from GMD_MATERIAL_EFFECTIVITIES_VW.

Because it references a view rather than base tables directly, GMF_MATERIAL_EFFECTIVITIES_VW1 inherits the join logic of GMD_MATERIAL_EFFECTIVITIES_VW and adds only the ranking filter layer. Consumers typically restrict to RK = 1 to obtain the selected effective item.

Key Columns

• FORMULA_ID / FORMULALINE_ID / LINE_NO / LINE_TYPE — Identify the formula and the specific material line being evaluated; these form the partitioning key for the ranking.
• ITEM_ID / ORIGINAL_ITEM_FLAG — The effective item and a flag indicating whether it is the original formula item rather than a substitute.
• QTY / ITEM_UM / SCALE_TYPE / SCALE_MULTIPLE / SCALE_ROUNDING_VARIANCE / ROUNDING_DIRECTION — Quantity, unit of measure, and scaling attributes used in costing and yield calculations.
• SCRAP_FACTOR / CONTRIBUTE_YIELD_IND — Scrap factor and the yield-contribution indicator (the user's search term), which determines whether the line contributes to yield computation.
• PHANTOM_TYPE / COST_ALLOC — Phantom handling and cost allocation behaviour for the material.
• LINE_ITEM_ID / LINE_ITEM_UOM / LINE_ITEM_QTY / LINE_ITEM_PRIMARY_UOM — Line item detail retained for reporting and reconciliation.
• SUB_ORIGINAL_QTY / SUB_REPLACE_QTY — Quantities of the original item and its replacement, supporting substitution ratio calculations.
• START_DATE / END_DATE — Effectivity dates bounding when the substitution is valid.
• RK — The computed rank; RK = 1 identifies the preferred effective material row per formula line.

Common Use Cases and Queries

Typical uses include costing item-substitution resolution, yield-contribution reporting, and formula material audits. A standard query selecting the preferred effective item per formula line follows:

• SELECT FORMULA_ID, LINE_NO, ITEM_ID, QTY, ITEM_UM, CONTRIBUTE_YIELD_IND, SUB_ORIGINAL_QTY, SUB_REPLACE_QTY FROM APPS.GMF_MATERIAL_EFFECTIVITIES_VW1 WHERE RK = 1 AND FORMULA_ID = :formula_id ORDER BY LINE_TYPE, LINE_NO;
• Filtering yield-impacting lines: add AND CONTRIBUTE_YIELD_IND = 'Y'.
• Auditing all candidates, including alternates: omit RK = 1 and order by FORMULA_ID, LINE_NO, RK to inspect substitution preference.
• Date-based effectivity: add AND SYSDATE BETWEEN START_DATE AND END_DATE.

Because the view encapsulates ranking and effectivity logic, it is well suited to reporting and interface extracts where a single resolved material row per formula line is required, avoiding the need to re-implement substitution preference rules in custom SQL.