Search Results mrp_sr_source_org




Overview
Explore in AI Chat

Overview

MRP_SR_SOURCE_ORG is a transactional table residing in the MRP schema of Oracle E-Business Suite (R12.1.1 and R12.2.2). It stores the source organization lines that belong to a Sourcing Rule or a Bill of Distribution. Each row defines one upstream supply point — an internal organization, a supplier, or a supplier site — from which a downstream organization or item may be sourced, together with the allocation percentage and rank that govern how demand is split across multiple sources. The table is a core component of the Oracle Master Scheduling/MRP sourcing engine and is consumed during planning, replenishment, and distribution requirement calculations.

From a Data Vault modeling perspective, the mined foreign-key structure suggests this object behaves as a link table: it resolves the many-to-many relationships between a sourcing rule receipt (MRP_SR_RECEIPT_ORG), an inventory organization (MTL_PARAMETERS), and a supplier (PO_VENDORS). The heuristic classification is offered as a modeling suggestion rather than a documented Oracle attribute.

Key Information Stored

The table contains 36 documented columns. The most significant include:

  • SR_SOURCE_ID — the surrogate primary key, enforced by unique index MRP_SR_SOURCE_ORG_U1. Uniquely identifies each source line.
  • SR_RECEIPT_ID — foreign key to MRP_SR_RECEIPT_ORG, linking the source line to its owning sourcing rule or bill of distribution receipt.
  • SOURCE_ORGANIZATION_ID — foreign key to MTL_PARAMETERS; the internal source organization.
  • VENDOR_ID — foreign key to PO_VENDORS; the supplier when the source is external.
  • VENDOR_SITE_ID — the supplier site associated with the vendor source.
  • SOURCE_TYPE — discriminates the nature of the source (internal organization versus supplier).
  • ALLOCATION_PERCENT — the percentage of demand allocated to this source.
  • RANK and OLD_RANK — priority ordering used to sequence sources when allocation rules apply.
  • SECONDARY_INVENTORY — the secondary inventory location within the source organization.
  • SHIP_METHOD — the shipping method used to move supply from this source.
  • REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, and PROGRAM_UPDATE_DATE — concurrent program context identifying the process that created or last updated the row.
  • LAST_UPDATE_DATE, CREATED_BY, and the ATTRIBUTE1–ATTRIBUTE15 flex columns — auditing and extensibility fields.

The documented business-key candidate is unique index MRP_SR_SOURCE_ORG_U2, spanning SR_RECEIPT_ID, SOURCE_ORGANIZATION_ID, VENDOR_ID, and VENDOR_SITE_ID.

Common Use Cases and Queries

Typical scenarios include auditing sourcing rule definitions, verifying allocation percentages across source lines, and reconciling supplier-to-organization sourcing relationships. A representative query joins the source lines back to their receipt header:

  • SELECT s.SR_SOURCE_ID, s.SR_RECEIPT_ID, s.SOURCE_ORGANIZATION_ID, s.VENDOR_ID, s.ALLOCATION_PERCENT, s.RANK FROM MRP.MRP_SR_SOURCE_ORG s WHERE s.SR_RECEIPT_ID = :p_receipt_id ORDER BY s.RANK;
  • Reporting sourcing rules by supplier: join VENDOR_ID to PO_VENDORS and SOURCE_ORGANIZATION_ID to MTL_PARAMETERS to produce a downstream-to-upstream sourcing map.
  • Validating allocation integrity: SUM(ALLOCATION_PERCENT) grouped by SR_RECEIPT_ID should equal 100 where allocation logic is in force.
  • Change tracking: filtering on LAST_UPDATE_DATE and PROGRAM_ID identifies who last modified a sourcing definition.

Related Objects

The following objects are most significant to this table:

  • MRP_SR_RECEIPT_ORG — joined on SR_RECEIPT_ID; the parent receipt/sourcing-rule header.
  • MTL_PARAMETERS — joined on SOURCE_ORGANIZATION_ID; supplies organization attributes.
  • PO_VENDORS — joined on VENDOR_ID; supplies supplier details.
  • Sourcing rule and bill of distribution definition tables in the MRP schema that feed the SR_RECEIPT_ID hierarchy.
  • MRP planning and replenishment concurrent programs that read these source lines when generating planned orders.

Because the sourcing engine derives supply paths directly from these rows, any change to allocation, rank, or source organization directly affects planning output for all downstream organizations assigned to the rule.