Results for “build_in_wip_flag”

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

Overview

MRP_UNSCHEDULED_ORDERS_V is an APPS-owned view in the Oracle E-Business Suite Master Scheduling/MRP (MRP) product family. Its purpose is to expose planned orders generated by the planning engine that are not tied to a discrete scheduled work order line, presenting them in a normalized, demand-source-shaped format that downstream forms, reports, and integration programs can consume. In practice the view projects rows from MRP_RECOMMENDATIONS of order type 5 (planned orders) and reformats them as pseudo demand-source records using the "planned order" convention of DEMAND_SOURCE_TYPE = 100.

The view is relevant to searches for replenish_to_order_flag because it exposes KFV.REPLENISH_TO_ORDER_FLAG (and KFV.BUILD_IN_WIP_FLAG) directly from the key-flexfield item master. Any query, report, or personalization that needs to know whether a planned/unscheduled supply is replenish-to-order or replenish-to-stock can read this attribute here without joining back to MTL_SYSTEM_ITEMS_KFV.

Underlying Base Objects

The documented view text joins MTL_SYSTEM_ITEMS_KFV (alias KFV), MRP_SYSTEM_ITEMS (RSI1), MRP_PLANS (MP1), MRP_RECOMMENDATIONS (MR1), and WIP_LINES (WL). Item context is resolved by matching KFV.INVENTORY_ITEM_ID and ORGANIZATION_ID to RSI1 and MR1. Plan context is resolved through MRP_PLANS on COMPILE_DESIGNATOR and through MRP_PLAN_ORGANIZATIONS when the plan spans multiple organizations.

Metadata for Release 12.2.2 lists additional referenced objects, including BOM_OPERATIONAL_ROUTINGS, OE_ORDER_LINES_ALL, OE_ORDER_HOLDS_ALL, and the HZ_* party/account/site/location synonyms, together with the packages MRP_FLOW_SCHEDULE_UTIL, MRP_GET_PROJECT, MRP_MANAGER_PK, INV_SALESORDER, INV_DECIMALS_PUB, CTO_WIP_WORKFLOW_API_PK, and OE_INSTALL, and the MRP_DESIGNATORS_VIEW view. These reflect the full planning ecosystem the scheduled/unscheduled order views draw upon — flow schedule quantities, project/task description lookups, sales-order and CTO handling, and designator resolution. The filter NVL(KFV.RELEASE_TIME_FENCE_CODE,-1) <> 6 excludes kanban items, and MR1.ORDER_TYPE = 5 restricts the result to planned orders.

Key Columns

• ROWID / literal 2 — Identifies the source recommendation row; the constants flag the "planned orders" option.
• ORGANIZATION_ID, INVENTORY_ITEM_ID, CONCATENATED_SEGMENTS — Organization, item, and concatenated item flexfield value.
• LINE_ID — WIP_LINES.LINE_ID, indicating the production line context for line-based plans.
• Schedule/quantity columns — NVL(FIRM_DATE, NEW_SCHEDULE_DATE) and NVL(FIRM_QUANTITY, NEW_ORDER_QUANTITY) give the firm-or-new date and quantity; a DERIVED_QUANTITY-type column applies GREATEST(quantity − flow quantity, 0) using MRP_FLOW_SCHEDULE_UTIL.GET_FLOW_QUANTITY.
• DEMAND_SOURCE_TYPE / DEMAND_SOURCE_LINE — Set to 100 (planned order) and TO_CHAR(MR1.TRANSACTION_ID) respectively.
• PROJECT_ID / TASK_ID with PROJECT() / TASK() — Project and task identifiers plus their descriptive names from MRP_GET_PROJECT.
• FIXED_LEAD_TIME, VARIABLE_LEAD_TIME — Lead-time components sourced from MRP_SYSTEM_ITEMS.
• FIRM_PLANNED_TYPE, DEMAND_CLASS, END_ITEM_UNIT_NUMBER — Planning attributes carried from MRP_RECOMMENDATIONS.
• REPLENISH_TO_ORDER_FLAG, BUILD_IN_WIP_FLAG — Item-level replenishment and WIP flags sourced from MTL_SYSTEM_ITEMS_KFV, the attributes of primary interest when searching for replenish_to_order_flag.

Common Use Cases and Queries

Typical usage includes identifying all unscheduled planned supplies for an item/organization, separating replenish-to-order versus replenish-to-stock planned orders, and feeding custom planning reports or interfaces that expect the demand-source layout.

• Locate planned orders for a plan and organization:

  SELECT organization_id, inventory_item_id, concatenated_segments,
         demand_source_line, replenish_to_order_flag
    FROM apps.mrp_unscheduled_orders_v
   WHERE organization_id = :org_id;

• Isolate replenish-to-order planned supply:

  SELECT concatenated_segments, demand_source_line, project_id, task_id
    FROM apps.mrp_unscheduled_orders_v
   WHERE replenish_to_order_flag = 'Y';

• Report planned-order context for a compile designator via MRP_RECOMMENDATIONS, joining on TRANSACTION_ID carried in DEMAND_SOURCE_LINE.

Because the view is defined in APPS and built primarily on planning synonyms, query grants and synonym access should be confirmed for the reporting schema. Filtering by plan status (MP1.PLAN_COMPLETION_DATE and DATA_COMPLETION_DATE NOT NULL) is already embedded, so only completed plans are returned.