Search Results mtl_interorg_ship_methods




Overview
Explore in AI Chat

Overview

MRP_ITEM_SOURCING_LEVELS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined over the Master Scheduling/MRP (MRP) product tables. It presents the sourcing rules and sourcing assignments that govern how inventory items are replenished or transferred across organizations, suppliers, and customers. The view consolidates, for each inventory item and organization combination, the applicable sourcing rule, the source organization or vendor, allocation percentages, ranking, transit and shipping attributes, and the effective and disable dates of the associated receipt organization. The constant column SOURCING_LEVEL is returned as 1, indicating that the rows surfaced here represent item-level sourcing.

Because sourcing rules are central to planning, procurement, and inter-org transfer logic, this view functions as a convenient reporting and integration access point. Rather than joining the multiple assignment, sourcing rule, source organization, and receipt organization tables directly, planners, report developers, and integration interfaces can query a single object to retrieve the sourcing configuration of an item.

Underlying Base Objects

The documented base objects referenced by the view include MRP_SR_ASSIGNMENTS, MRP_SOURCING_RULES, MRP_SR_RECEIPT_ORG, MRP_SR_SOURCE_ORG, MTL_SYSTEM_ITEMS, MTL_INTERORG_SHIP_METHODS, MRP_ASSIGNMENT_SETS, MTL_ITEM_CATEGORIES, and MTL_PARAMETERS, all accessed through APPS synonyms. The core join path links MRP_SR_ASSIGNMENTS (the assignment of a sourcing rule to an item and organization, with ASSIGNMENT_TYPE constrained to 6 for ITEM-ORG) to MRP_SOURCING_RULES through SOURCING_RULE_ID. The receipt organization table MRP_SR_RECEIPT_ORG links by SR_RECEIPT_ID and supplies the effective and disable dates and the receipt organization. The source organization table MRP_SR_SOURCE_ORG supplies the source organization, vendor, allocation percent, and rank. Shipping attributes are drawn from MTL_INTERORG_SHIP_METHODS, joined on the from-organization and ship method, with item-organization context supplied by MTL_SYSTEM_ITEMS. The rule status is restricted to active (STATUS = 1), and outward joins accommodate missing shipping method data.

Key Columns

Common Use Cases and Queries

Typical uses include auditing the sourcing configuration of a specific item, validating that sourcing assignments and their effective dates align with planning assumptions, and feeding sourcing data into custom reports or integrations. The following query lists sourcing sources for a given item and organization:

SELECT inventory_item_id,
       organization_id,
       sourcing_rule_name,
       sourcing_rule_type,
       source_organization_id,
       vendor_id,
       allocation_percent,
       rank,
       effective_date,
       disable_date
FROM   apps.mrp_item_sourcing_levels_v
WHERE  inventory_item_id = :item_id
AND    organization_id  = :org_id
ORDER BY rank;

A second scenario examines all items sourcing from a particular organization, supporting inter-org transfer analysis:

SELECT inventory_item_id,
       organization_id,
       source_organization_id,
       allocation_percent,
       rank
FROM   apps.mrp_item_sourcing_levels_v
WHERE  source_organization_id = :source_org_id
ORDER BY inventory_item_id, rank;

Because SOURCING_LEVEL is fixed at 1 and assignment type is limited to ITEM-ORG, the view should be treated as an item-level sourcing source, with the effective and disable dates used to filter active configuration at the planning date.