Results for “mrpbv_replenishment_sources”

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

Overview

MRPBV_REPLENISHMENT_SOURCES is an APPS-owned read-only view within the Oracle E-Business Suite Master Scheduling/MRP (MRP) module. It exposes the configuration of replenishment sources that supply a given replenishment destination, combining source ranking, allocation percentages, and shipping method details into a single queryable interface. The view is defined over the MRP_SR_SOURCE_ORG table joined to MFG_LOOKUPS and MTL_INTERORG_SHIP_METHODS, and is typically used by planners, sourcing rule administrators, and reporting integrations to inspect how demand at a destination organization is allocated across multiple supply sources.

The view operates "WITH READ ONLY", meaning it cannot be used for DML; it is strictly a reporting and inquiry construct. Because it resolves the SOURCE_TYPE lookup meaning and the applicable inter-organization shipping method, it is a convenient single point for validating supplier and organization sourcing setups without manually joining the underlying MRP and inventory tables.

Underlying Base Objects

The documented base objects referenced by the view are:

• MRP_SR_SOURCE_ORG (SYNONYM) — the primary driver table, aliased SR, holding sourcing rule lines: source type, allocation percent, rank, shipping method, source and receipt identifiers, and the supplier/vendor identifiers.
• MFG_LOOKUPS (VIEW) — aliased LO, filtered to LOOKUP_TYPE = 'MRP_SOURCE_TYPE', supplying the descriptive meaning of the sourcing source type.
• MTL_INTERORG_SHIP_METHODS (SYNONYM) — aliased INTER, providing the shipping method valid between a specific from-organization and to-organization pair.
• MRP_SR_RECEIPT_ORG (SYNONYM) — used in a scalar subquery to resolve the receipt organization for a given replenishment receipt, matching the to-organization of the shipping method.

The joins use outer-join syntax: the shipping method link applies only when SR.SHIP_METHOD is not null and the from/to organizations match; the lookup join carries the (+) operator on the lookup side. The DISTINCT keyword removes duplicates that can arise from these multi-table resolutions.

Key Columns

• SOURCE_TYPE / MEANING — the lookup code and its decoded description identifying the kind of replenishment source (for example, organization or supplier).
• ALLOCATION_PERCENT — the percentage of demand assigned to this source within the sourcing rule.
• RANK — the priority order of the source when multiple sources are available.
• SHIPPING_METHOD — the inter-organization shipping method code carried through from MRP_SR_SOURCE_ORG; note this maps to the SR.SHIP_METHOD column in the view text and is relevant to the "shipping_method" search term.
• REPLENISHMENT_SOURCE_ID / SR_SOURCE_ID and REPLENISHMENT_DESTINATION_ID / SR_RECEIPT_ID — identifiers linking the source line to its sourcing and receipt definitions.
• SOURCE_ORGANIZATION_ID — the organization supplying the material.
• SUPPLIER_ID / VENDOR_ID and SUPPLIER_SITE_ID / VENDOR_SITE_ID — supplier and supplier site when the source type is external.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY.

Common Use Cases and Queries

Typical scenarios include auditing sourcing rules for a destination organization, verifying allocation percentages sum correctly, and confirming that a shipping method exists between the source and receiving organizations. A common query filters by shipping method:

SELECT source_type, allocation_percent, rank, shipping_method, source_organization_id, supplier_id FROM apps.mrpv_replenishment_sources WHERE shipping_method = :p_ship_method;

To review all sources supplying a specific organization, filter on the destination identifier:

SELECT meaning, allocation_percent, rank, shipping_method FROM apps.mrpv_replenishment_sources WHERE replenishment_destination_id = :p_dest_id ORDER BY rank;

Because the view is read-only and joins the shipping method table with an outer join, records with a null or invalid SHIP_METHOD are still returned, which is useful when diagnosing missing inter-org shipping method setups.