Search Results mrp_sr_view_exp_v




Overview
Explore in AI Chat

Overview

MRP_SR_VIEW_EXP_V is an Oracle E-Business Suite database view owned by the APPS schema and defined within the MRP (Master Scheduling/MRP) product family. Its documented purpose is to present a sourcing rule / bill of distribution (BOD) expanded view. In other words, rather than exposing individual sourcing rule header and assignment tables in their normalized form, this view flattens the sourcing rule receipt organization data together with its associated source lines into a single, query-ready projection that includes resolved lookup meanings. This makes it particularly useful for reporting and integration scenarios where a complete picture of a sourcing rule's receipt organization and source organizations or vendors is required in one pass.

The view maintains a VALID status in ETRM for both Oracle EBS 12.1.1 and 12.2.2. Its reliance on standard MRP sourcing rule objects means the data it exposes reflects the sourcing rules and bills of distribution configured in the planning application.

Underlying Base Objects

The documented view text defines a join across three principal objects: MRP_SR_RECEIPT_ORG (accessed through a synonym), MRP_SR_SOURCE_ORG_V (a view), and MFG_LOOKUPS (a view). Additional documented referenced base objects include the FND_GLOBAL package.

The join condition links REC.SR_RECEIPT_ID to SOUR.SR_RECEIPT_ID. A filter excludes rows where SOUR.SOURCE_TYPE is 2, and the lookup join is constrained by both the lookup type and matching lookup code. Because the source-side object is itself a view, the expanded view effectively nests over additional sourcing rule source logic.

Key Columns

The view exposes the following documented columns:

  • SOURCING_RULE_ID — identifier of the parent sourcing rule.
  • SR_RECEIPT_ID — identifier of the receipt organization assignment record.
  • RECEIPT_ORGANIZATION_ID — the organization receiving the sourced supply.
  • SR_SOURCE_ID — identifier of the individual source line.
  • SOURCE_TYPE — resolved lookup meaning describing the source category.
  • SOURCE_ORGANIZATION_ID — source organization, coalesced to 0 via NVL when null.
  • SOURCE_ORGANIZATION_CODE — descriptive code of the source organization.
  • VENDOR_NAME / VENDOR_SITE — supplier details when the source is a vendor.
  • ALLOCATION_PERCENT — percentage of supply allocated to the source line.
  • RANK — priority ranking of the source.
  • SHIP_METHOD / INTRANSIT_TIME — shipping method and lead time.
  • ORG_VENDOR — a concatenation of SOURCE_ORGANIZATION_CODE and VENDOR_NAME for convenient display.

Common Use Cases and Queries

Typical uses include reporting on sourcing rule definitions across organizations, validating allocation percentages and ranks, and feeding planning or integration processes that require expanded sourcing rule data. A basic query follows:

SELECT sourcing_rule_id, receipt_organization_id, source_type, source_organization_code, vendor_name, allocation_percent, rank FROM apps.mrp_sr_view_exp_v WHERE sourcing_rule_id = :p_rule_id ORDER BY rank;

Because the view already resolves the source type meaning and concatenates organization and vendor, it is well suited to ad hoc reporting and data extraction without requiring additional lookup joins.