Results for “replenish_to_order_flag”

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

Overview

WIP_OPEN_DEMANDS_V is an APPS-owned, VALID view in the Work in Process (WIP) module of Oracle E-Business Suite, documented for releases 12.1.1 and 12.2.2. Its stated purpose is to retrieve sales orders that are not reserved, exposing unreserved order demand that is relevant to the shop floor. The view is a filtered, enriched projection built on top of OE_WIP_OPEN_DEMANDS_V, joining that order-management view to MTL_SYSTEM_ITEMS and applying conversion and profile utilities. In reporting and integration, it serves as a low-level data source for identifying WIP-eligible, order-driven demand that has not yet been soft- or hard-reserved against supply, allowing planners and interfaces to reconcile open sales order requirements with manufacturing execution.

Underlying Base Objects

The documented base objects referenced by the view are:

• OE_WIP_OPEN_DEMANDS_V (VIEW) — the primary driver, supplying organization, demand header/line, requirement date, item, demand class, UOM, and open quantity columns.
• MTL_SYSTEM_ITEMS (SYNONYM) — joined on ORGANIZATION_ID and INVENTORY_ITEM_ID to supply PRIMARY_UOM_CODE and REPLENISH_TO_ORDER_FLAG, and to enforce item-level filters.
• INV_CONVERT (PACKAGE) — invoked via INV_UM_CONVERT to translate demand quantities into the item's primary UOM.
• FND_PROFILE (PACKAGE) and OE_LINE_UTIL (PACKAGE) — used indirectly by the underlying order-management view for profile and order-line derivation logic.

The join to MTL_SYSTEM_ITEMS is restrictive: only items with BUILD_IN_WIP_FLAG = 'Y', PICK_COMPONENTS_FLAG = 'N', and BOM_ITEM_TYPE = 4 (Standard) are retained. This confines the result set to standard, buildable, non-pick items.

Key Columns

• ORGANIZATION_ID — inventory organization of the demand.
• DEMAND_SOURCE_HEADER_ID / DEMAND_ORDER_HEADER_ID — header identifiers for the demand source and originating sales order.
• DEMAND_SOURCE_LINE_ID / DEMAND_SOURCE_LINE_NUMBER — line-level identifiers and visible line number.
• REQUIREMENT_DATE — date the demand is required.
• INVENTORY_ITEM_ID — item for which demand exists.
• DEMAND_CLASS_CODE — demand class classification.
• DEMAND_UOM_CODE / PRIMARY_UOM_CODE — the demand's transactional and primary units of measure.
• DEMAND_OPEN_QUANTITY — unreserved open demand in demand UOM.
• PRIMARY_OPEN_QUANTITY — the same quantity converted to primary UOM via INV_CONVERT.INV_UM_CONVERT.
• REPLENISH_TO_ORDER_FLAG — indicates whether the item is configured as replenish-to-order, the attribute most frequently searched by users of this view.

Common Use Cases and Queries

Typical scenarios include building availability or exception reports for unreserved sales demand, feeding planning or scheduling processes, and filtering demand by replenish-to-order eligibility. Repository or ETRM-driven searches, such as those on replenish_to_order_flag, are used to locate the view as the source of this attribute alongside open demand quantities.

Sample query listing open, unreserved order demand for replenish-to-order capable items in an organization:

• SELECT organization_id, inventory_item_id, demand_source_line_number, requirement_date, demand_open_quantity, primary_open_quantity, replenish_to_order_flag
• FROM apps.wip_open_demands_v
• WHERE organization_id = :org_id
• AND replenish_to_order_flag = 'Y'
• AND requirement_date BETWEEN :start_date AND :end_date
• ORDER BY requirement_date, inventory_item_id;

Because the view pre-applies the buildable, non-pick, standard-item restrictions and performs UOM conversion inline, it simplifies downstream logic that would otherwise require joining OE_WIP_OPEN_DEMANDS_V to MTL_SYSTEM_ITEMS and calling INV_UM_CONVERT directly.