Search Results mrp_bod_task_sr_levels_v




Overview
Explore in AI Chat

Overview

MRP_BOD_TASK_SR_LEVELS_V is a read-only view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the Master Scheduling/MRP product family and is described in the ETRM repository as the "BOD task sourcing rule levels view." The object is registered with a VALID status, indicating that it compiles successfully and is available for query in a standard installation.

The view exposes sourcing rule assignment data at the item and organization level, structured for consumption by Business Object Document (BOD) processing tasks. Sourcing rules in Oracle MRP define how supply is allocated across organizations and suppliers, specifying percentages and rank for each source. This view flattens that hierarchical configuration into a single result set that includes the receipt organization, source organization, vendor, and ship method attributes, along with computed intransit time and ship method values derived from the MRP_SCATP_PVT package. This makes it suitable for integration scenarios where external planning systems or downstream BOD consumers require a normalized representation of sourcing rules rather than the underlying normalized tables.

Underlying Base Objects

The view is defined over several base and derived objects. The primary sourcing rule tables are exposed through synonyms including MRP_SOURCING_RULES, MRP_SR_ASSIGNMENTS, MRP_SR_RECEIPT_ORG, and MRP_SR_SOURCE_ORG. Item data is sourced from MRP_SYSTEM_ITEMS, with MTL_SYSTEM_ITEMS, MTL_ITEM_CATEGORIES, and MTL_PARAMETERS also documented as referenced objects. MRP_PLAN_ORGANIZATIONS_V provides the planning organization context, and MRP_SCATP_PVT is referenced as a package supplying the GET_INTRANSIT_TIME and GET_SHIP_METHOD functions.

The FROM clause joins MRP_PLAN_ORGANIZATIONS_V, MRP_SR_ASSIGNMENTS, MRP_SYSTEM_ITEMS, MRP_SOURCING_RULES, MRP_SR_RECEIPT_ORG, and MRP_SR_SOURCE_ORG. Join conditions link items to assignments by inventory item and organization, connect source and receipt organization records through SR_RECEIPT_ID, and tie receipt organizations back to sourcing rules. The view text includes an ORDERED hint and explicit index hints on MRP_SR_ASSIGNMENTS_U2, MRP_SOURCING_RULES_U1, MRP_SR_RECEIPT_ORG_U2, and MRP_SR_SOURCE_ORG_U2, using nested loops to control the execution plan.

Key Columns

Common Use Cases and Queries

The view is typically queried to report sourcing rule configuration for a given item and organization, particularly when investigating the receipt_org attribute that determines which organization receives supply from a given source. A common query filters by inventory item and organization:

  • SELECT sourcing_rule_name, source_organization_id, receipt_organization_id, allocation_percent, rank FROM mrp_bod_task_sr_levels_v WHERE inventory_item_id = :p_item AND organization_id = :p_org;
  • SELECT inventory_item_id, organization_id, receipt_organization_id, effective_date, disable_date FROM mrp_bod_task_sr_levels_v WHERE receipt_organization_id = :p_receipt_org AND sourcing_rule_type = 1;

These queries support sourcing rule validation, integration extracts for BOD task processing, and diagnostic review of intransit time and ship method resolution across receipt organizations. Because the view joins multiple sourcing rule tables and invokes packaged functions, queries should be constrained by item, organization, or sourcing rule to avoid full scans.