Search Results source_organization

Overview

MRP_KANBAN_DETAILS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes detailed attribute-level information about Kanban pull sequences defined within Oracle Master Scheduling/MRP. The view denormalizes the core Kanban pull sequence record from MTL_KANBAN_PULL_SEQUENCES and joins it to the associated Kanban plan header, item definition, source location, supplier, and WIP line data, producing a single flat result set for Kanban analysis.

Because it is a view rather than a base table, it carries no storage of its own and reflects the current state of its underlying objects at query time. It is intended primarily for reporting, ad hoc inquiry, and integration extracts relating to replenishment signaling and Kanban card configuration. The view remains in VALID status in the ETRM repository for 12.2.2.

Underlying Base Objects

The view is defined across a documented set of base objects:

• MTL_KANBAN_PULL_SEQUENCES (synonym) — the driving table, aliased PS, supplying organization, item, subinventory, source type, and replenishment parameters.
• MRP_KANBAN_PLANS (synonym) — aliased KAN, providing the Kanban designator and description.
• MTL_SYSTEM_ITEMS_KFV (synonym) — aliased ITEM, supplying concatenated item segments and planner code.
• MTL_PARAMETERS (synonym) — aliased MP, supplying the source organization code.
• MFG_LOOKUPS (view) — aliased KST, decoding SOURCE_TYPE via lookup type MTL_KANBAN_SOURCE_TYPE.
• PO_VENDORS and PO_VENDOR_SITES_ALL (views) — supplying supplier name and site code.
• WIP_LINES (synonym) — supplying the WIP line code.
• MRP_GET_LOCATION (package) — resolving locator identifiers to descriptive locations.
• FLM_KANBAN_WORKBENCH_UTIL (package) — deriving the component category identifier.

All joins to supplier, source organization, and WIP line data are outer joins, so pull sequences without those attributes remain visible.

Key Columns

• PULL_SEQUENCE_ID / KANBAN_PLAN_ID — primary identifiers linking the row to its pull sequence and Kanban plan.
• SOURCE_ORGANIZATION_ID / ORGANIZATION_CODE — the supplying organization and its code; directly relevant to the “source_organization” search terms.
• SOURCE_TYPE / MEANING — the replenishment source classification decoded from MFG_LOOKUPS.
• INVENTORY_ITEM_ID / ITEM — item identifier and concatenated segments.
• SUBINVENTORY_NAME, LOCATOR_ID, LOCATOR — the consuming location details.
• SOURCE_SUBINVENTORY, SOURCE_LOCATOR_ID — the replenishment source location.
• SUPPLIER_ID, VENDOR_NAME, SUPPLIER_SITE_ID, VENDOR_SITE_CODE — supplier details for external source types.
• NUMBER_OF_CARDS, KANBAN_SIZE, REPLENISHMENT_LEAD_TIME — Kanban sizing and planning parameters.
• FIXED_LOT_MULTIPLIER, MINIMUM_ORDER_QUANTITY, SAFETY_STOCK_DAYS — replenishment control attributes.

Common Use Cases and Queries

Typical uses include auditing Kanban configuration by source organization, listing replenishment parameters for a plan, and extracting supplier-linked Kanbans for procurement review. A representative query filtering on source organization is:

• SELECT pull_sequence_id, kanban_designator, item, organization_code, source_subinventory, meaning FROM apps.mrp_kanban_details_v WHERE source_organization_id = :org_id;
• SELECT kanban_plan_id, item, number_of_cards, kanban_size FROM apps.mrp_kanban_details_v WHERE organization_id = :org_id ORDER BY item;

Because the view invokes MRP_GET_LOCATION and FLM_KANBAN_WORKBENCH_UTIL per row, large unfiltered extracts should be bounded by organization or plan predicates to control execution cost.