Results for “order_type_text”

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

Overview

MRP_KANBAN_DEMAND_V is a seeded Oracle E-Business Suite view owned by the APPS schema and delivered as part of the Master Scheduling / MRP product family. It exposes kanban demand records generated by the Oracle Kanban planning process, presenting each demand line together with its parent kanban plan, item identity, organization context, and assembly consumption information. The view is defined in both release 12.1.1 and 12.2.2, and its status is VALID, meaning it is active and queryable in a standard installation.

The view is primarily a reporting and integration convenience layer. Instead of requiring external consumers, custom reports, or interfaces to join MRP_KANBAN_DEMAND to MRP_KANBAN_PLANS, MTL_SYSTEM_ITEMS_KFV, MTL_PARAMETERS, and the MFG_LOOKUPS lookup, the view pre-resolves those relationships and surfaces human-readable code combinations, organization codes, lookup meanings, and locator descriptions. This makes it well-suited for BI Publisher reports, Oracle Discoverer workbooks, custom concurrent programs, and inbound interface validation routines that need to inspect kanban demand without re-implementing the join logic.

Underlying Base Objects

The documented base objects referenced by APPS.MRP_KANBAN_DEMAND_V are:

• MRP_KANBAN_DEMAND (synonym) — the primary fact table holding one row per kanban demand record.
• MRP_KANBAN_PLANS (synonym) — the kanban plan header supplying the designator and input type.
• MTL_SYSTEM_ITEMS_KFV (synonym) — the key flexfield view that provides concatenated item segments for both the kanban item and the assembly item.
• MTL_PARAMETERS (synonym) — provides organization codes for the kanban organization and the assembly organization.
• MFG_LOOKUPS (view) — supplies the translated meaning for the demand order type.
• MRP_GET_LOCATION (package) — a PL/SQL function called to return a formatted locator description for both the kanban locator and the assembly locator.
• FLM_KANBAN_WORKBENCH_UTIL (package) — a PL/SQL function used to derive the component category identifier for the kanban plan and item.

The view joins these objects using an outer join to the assembly organization and assembly item, since a kanban demand may not reference a consuming assembly. The lookup join is conditional on the kanban plan input type, resolving forecast origin, schedule origin, or WIP schedule type as appropriate.

Key Columns

• DEMAND_ID, KANBAN_PLAN_ID — primary key of the demand row and the owning kanban plan.
• KANBAN_DESIGNATOR — the user-defined identifier of the kanban plan.
• ORGANIZATION_ID, ORGANIZATION — kanban organization identifier and code.
• INVENTORY_ITEM_ID, ITEM — kanban item identifier and concatenated flexfield segments.
• SUBINVENTORY, LOCATOR_ID, LOCATOR — supply location for the kanban item.
• ASSEMBLY_ITEM_ID, ASSEMBLY_ITEM — the assembly item that consumes the kanban component, where applicable.
• ASSEMBLY_ORG_ID, ASSEMBLY_ORG, ASSEMBLY_SUBINVENTORY, ASSEMBLY_LOCATOR_ID, ASSEMBLY_LOCATOR — assembly-side organization and location details.
• DEMAND_DATE, DEMAND_QUANTITY — the date and quantity of the kanban demand.
• ORDER_TYPE, ORDER_TYPE_TEXT — the coded order type and its translated meaning from MFG_LOOKUPS.
• PLANNER_CODE — the planner assigned to the kanban item.
• CATEGORY_ID — component category derived by FLM_KANBAN_WORKBENCH_UTIL.

Common Use Cases and Queries

Typical uses include kanban workbench reporting, demand-versus-supply analysis for pull signals, and integration extraction for supplier kanban or e-kanban systems. A simple listing of kanban demand by plan and item can be produced as follows:

• SELECT kanban_designator, organization, item, demand_date, demand_quantity, order_type_text FROM apps.mrp_kanban_demand_v WHERE kanban_plan_id = :p_plan_id ORDER BY demand_date;
• SELECT organization, item, SUM(demand_quantity) total_qty FROM apps.mrp_kanban_demand_v WHERE demand_date BETWEEN :p_from AND :p_to GROUP BY organization, item;
• SELECT kanban_designator, assembly_item, assembly_org, demand_quantity FROM apps.mrp_kanban_demand_v WHERE assembly_item_id IS NOT NULL;

Because the view invokes PL/SQL functions such as MRP_GET_LOCATION and FLM_KANBAN_WORKBENCH_UTIL.GET_CATEGORY_ID, performance is best when queries are filtered by KANBAN_PLAN_ID, ORGANIZATION_ID, or DEMAND_DATE to restrict the row set passed to those functions.