Results for “assembly_org_id”

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

Overview

The MRP_KANBAN_DEMAND table resides in the MRP schema and belongs to the Master Scheduling/MRP product family within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores demand information for items that are included in a kanban plan, providing the quantitative and date-driven inputs that drive kanban replenishment signaling. Where a kanban plan defines the replenishment strategy for a set of items, MRP_KANBAN_DEMAND captures the individual demand records against which kanban quantities are evaluated and triggered.

The table is documented as VALID and contains 23 columns. Its physical schema is owned by MRP with a primary key constraint MRP_KANBAN_DEMAND_PK defined on the DEMAND_ID column. A unique index, MRP_KANBAN_DEMAND_U1, is also defined on DEMAND_ID, confirming it as the business-key candidate. From a Data Vault modeling perspective, the mined foreign-key structure classifies this object heuristically as standalone; that is, it does not present the classic hub-and-link topology of highly normalized reference data. A modeler may nonetheless treat DEMAND_ID as a hub-like natural key candidate and the descriptive attributes as satellite content, but the documented relationship pattern is a single outbound reference to MRP_KANBAN_PLANS.

Key Information Stored

The most operationally significant columns describe both the demand being planned and the supply-side context for replenishment:

• DEMAND_ID — surrogate primary key and business-key candidate (unique index MRP_KANBAN_DEMAND_U1); uniquely identifies each demand row.
• KANBAN_PLAN_ID — foreign key to MRP_KANBAN_PLANS; associates the demand with its parent kanban plan.
• ORGANIZATION_ID — the inventory organization in which the demand applies.
• INVENTORY_ITEM_ID — the item for which demand is recorded.
• SUBINVENTORY and LOCATOR_ID — the demand-side storage location.
• ASSEMBLY_ITEM_ID, ASSEMBLY_ORG_ID, ASSEMBLY_SUBINVENTORY, and ASSEMBLY_LOCATOR_ID — the parent assembly context that consumes the item.
• DEMAND_DATE — the date on which the demand occurs.
• DEMAND_QUANTITY — the quantity required.
• ORDER_TYPE — classifies the originating demand order type.
• KANBAN_ITEM_FLAG — indicates whether the item is kanban-controlled.
• LAST_UPDATE_DATE, CREATED_BY, LAST_UPDATED_BY, CREATION_DATE, REQUEST_ID, PROGRAM_ID, and PROGRAM_APPLICATION_ID — standard audit and concurrent-program columns.

Common Use Cases and Queries

Typical usage centers on kanban planning and replenishment reporting. Analysts join demand rows to the parent plan to summarize required quantities by item and date:

• Listing outstanding demand for a plan: SELECT demand_id, inventory_item_id, demand_date, demand_quantity FROM mrp.mrp_kanban_demand WHERE kanban_plan_id = :plan_id ORDER BY demand_date;
• Aggregating demand by item and organization: SELECT organization_id, inventory_item_id, SUM(demand_quantity) FROM mrp.mrp_kanban_demand GROUP BY organization_id, inventory_item_id;
• Joining to kanban plans to filter active plans: SELECT d.* FROM mrp.mrp_kanban_demand d, mrp.mrp_kanban_plans p WHERE d.kanban_plan_id = p.kanban_plan_id;

Reporting use cases include shortage analysis, kanban sizing validation, and reconciliation of demand against replenishment signals.

Related Objects

• MRP_KANBAN_PLANS — the parent plan; joined via KANBAN_PLAN_ID.
• MRP_KANBAN_DEMAND_PK / MRP_KANBAN_DEMAND_U1 — primary and unique constraints on DEMAND_ID.
• MTL_SYSTEM_ITEMS_B — item definition lookup via INVENTORY_ITEM_ID.
• MTL_PARAMETERS — organization context via ORGANIZATION_ID.
• ORG_ORGANIZATION_DEFINITIONS — organization validation and reporting.
• MTL_ITEM_LOCATIONS — locator resolution via LOCATOR_ID.
• FND_CONCURRENT_REQUESTS — audit linkage via REQUEST_ID.