Search Results mrp_forecast_orig




Overview
Explore in AI Chat

Overview

APPS.MRP_KANBAN_DEMAND_V is a supplementary Oracle E-Business Suite view owned by the APPS schema and registered under FND Design Data MRP.MRP_KANBAN_DEMAND_V. Its documented status is VALID. Oracle classifies the object explicitly as a "supplementary view used to simplify forms coding," and the ETRM metadata carries Oracle's standard warning that querying or altering data through this view is not recommended because its definition may change dramatically in subsequent minor or major releases. In practice, the view functions as a denormalized read layer that exposes kanban demand records alongside resolved descriptive attributes—item names, organization codes, subinventory names, locator descriptions, and assembly context—so that Oracle Forms and similar UI components can render kanban demand information without issuing multiple lookups. It is a reporting and forms-support construct rather than a transactional interface, and it is not intended as a supported integration point for inbound or outbound data movement.

Underlying Base Objects

The documented referenced base objects are MRP_KANBAN_DEMAND (SYNONYM), MRP_KANBAN_PLANS (SYNONYM), MTL_SYSTEM_ITEMS_KFV (SYNONYM), MTL_PARAMETERS (SYNONYM), MFG_LOOKUPS (VIEW), and the packages MRP_GET_LOCATION and FLM_KANBAN_WORKBENCH_UTIL. MRP_KANBAN_DEMAND and MRP_KANBAN_PLANS supply the core demand and kanban plan transaction data, including demand quantity, demand date, demand type, and kanban designator. MTL_SYSTEM_ITEMS_KFV resolves inventory and assembly item identifiers into concatenated item names. MTL_PARAMETERS provides organization-level context. MFG_LOOKUPS translates numeric demand order types into descriptive text for the ORDER_TYPE_TEXT column. Because locator descriptions in Oracle EBS are derived at runtime rather than stored, the view relies on MRP_GET_LOCATION and FLM_KANBAN_WORKBENCH_UTIL to resolve locator and assembly locator names—reflected in the 4000-character datatype assigned to the LOCATOR and ASSEMBLY_LOCATOR columns, which accommodates concatenated locator segments returned by those package calls.

Key Columns

Common Use Cases and Queries

The view is primarily consumed by kanban workbench forms and diagnostic reporting where resolved item and locator descriptions are required. A representative query filtering on the demanded item or assembly follows:

  • SELECT kanban_designator, organization, item, assembly_item, demand_date, demand_quantity, order_type_text FROM apps.mrp_kanban_demand_v WHERE item = :p_item AND organization_id = :p_org;
  • SELECT assembly_item, subinventory, locator, demand_quantity FROM apps.mrp_kanban_demand_v WHERE assembly_item_id = :p_assembly_item_id ORDER BY demand_date;
  • SELECT planner_code, order_type_text, SUM(demand_quantity) FROM apps.mrp_kanban_demand_v GROUP BY planner_code, order_type_text;

Because the object is classified as a supplementary view, production reports should prefer the underlying MRP_KANBAN_DEMAND and MRP_KANBAN_PLANS tables directly. When the view is used, callers should treat the resolved name columns as display-only and avoid relying on locator string formats, which are generated by package logic and may vary across releases or patches.