Search Results consider_demand_tf

Overview

The view MRP_I2_DUMMY_PART_MASTER_V is a Rhythm integration view within the Oracle E-Business Suite Master Scheduling/MRP module. It presents a consolidated record of every item defined as a planned part in Rhythm, exposing the master-data attributes that the planning engine requires to generate planned orders, time fences, and lot-sizing decisions. The view is documented as a "Rhythm view supporting information regarding parts planned in Rhythm," and the ETRM metadata records that it is not implemented in the database in the documented configuration; it exists as part of the interface layer used to publish item planning attributes to external planning processes.

Because the view flattens item, planning, and organization-level attributes into a single row per inventory item, it functions as a reporting and integration surface rather than a transactional object. Downstream extracts, custom concurrent programs, and third-party scheduling tools reference it to obtain a stable, read-only projection of planned part data without joining the numerous base planning tables directly.

Underlying Base Objects

The view is defined over a single documented base object, MRP_RHX_PLANNED_ITEMS_V, which supplies the item-level planning attributes. The filter clause WHERE I.MRP_PLANNING_CODE IN (3, 4, 7, 8) restricts output to items that are actively planned under the Rhythmic planning codes (typically MRP, MPS, DRP, and related planned classifications), excluding non-planned or unplanned items. The metadata records no additional underlying tables beyond this view, though several expressions reference the PL/SQL function MRP_I2_ERP.GET_PARAMETER, which resolves organization-specific planning parameters at query time.

Key Columns

• PART_NUMBER / INVENTORY_ITEM_ID / ORGANIZATION_ID — Item and organization keys that uniquely identify each planned part.
• MAKE_OR_BUY_CODE — Derived from PLANNING_MAKE_BUY_CODE, indicating whether the item is manufactured or purchased.
• PLANNING_TIME_FENCE — Resolves PLANNING_TIME_FENCE_DAYS; when zero, it is computed from the DEFAULT_PLANNING_TF_OFFSET parameter plus postprocessing and full lead times.
• DEMAND_TIME_FENCE — The column most directly tied to the user's search term: it returns I.DEMAND_TIME_FENCE_DAYS only when the parameter CONSIDER_DEMAND_TF equals 'Y', otherwise zero. This DECODE makes the view's demand time fence behavior parameter-driven per organization.
• LEADTIME / POSTPROCESSING_LEADTIME — Sums of preprocessing, full, and postprocessing lead times.
• MINIMUM_ORDER_QUANTITY / MAXIMUM_ORDER_QUANTITY / INCREMENTAL_LOT_SIZE — Lot-sizing controls; MAX defaults to 999999999 and INCREMENTAL applies CEIL when rounding control type is 1.
• FIXED_DAYS_SUPPLY, PLANNER_CODE, UOM, SELLABLE, CATEGORY, BUYER_ID — Supporting planning and procurement attributes.
• ASSEMBLE_TO_ORDER, PHANTOM_FLAG — Assemble-to-order and WIP supply type indicators.

Common Use Cases and Queries

Typical uses include auditing planning time fences, verifying demand time fence configuration per organization, and extracting planned parts for external scheduling systems. A sample query:

SELECT PART_NUMBER, ORGANIZATION_ID, MAKE_OR_BUY_CODE, PLANNING_TIME_FENCE, DEMAND_TIME_FENCE, PLANNER_CODE FROM MRP_I2_DUMMY_PART_MASTER_V WHERE ORGANIZATION_ID = :org_id ORDER BY PART_NUMBER;

Analysts investigating the CONSIDER_DEMAND_TF parameter can compare the DEMAND_TIME_FENCE column against the source DEMAND_TIME_FENCE_DAYS value on MRP_RHX_PLANNED_ITEMS_V to confirm whether the parameter is enabled for a given organization, since the view suppresses the fence value entirely when CONSIDER_DEMAND_TF resolves to anything other than 'Y'.