Search Results mrp_sr_source_org_u1

Overview

MRP.MRP_SR_SOURCE_ORG is a transactional detail table within the Oracle E-Business Suite Supply Chain Planning schema. It stores the individual source organizations or source suppliers that constitute a Sourcing Rule or a Bill of Distribution. Each row represents one source line attached to a receipt organization, capturing either an internal manufacturing/transfer source (an inventory organization) or an external supplier and supplier site, together with the percentage of supply allocated to that source and its rank within the rule.

The table is documented as a child of MRP.MRP_SR_RECEIPT_ORG, with SR_RECEIPT_ID acting as the FK back to the parent. It is populated through the Define Sourcing Rules and Define Bills of Distribution forms in Oracle Supply Chain Planning. The object resides in the APPS_TS_TX_DATA tablespace with PCTFREE 10, and its unique indexes are held in APPS_TS_TX_IDX.

From a heuristic Data Vault modeling perspective, the mined FK structure classifies this object as a link: it resolves relationships between a receipt organization record and external hubs such as MTL_PARAMETERS (organization) and PO_VENDORS (supplier). It should not be treated as a standalone hub, since its identity derives from the parent receipt organization.

Key Information Stored

The surrogate primary key is SR_SOURCE_ID (NUMBER), described as the unique identifier for a row and enforced by unique index MRP_SR_SOURCE_ORG_U1 — the index referenced in the user's search term. This is the only single-column unique constraint and is the correct column for row-level joins and for lookups from dependent objects.

A second unique index, MRP_SR_SOURCE_ORG_U2, is a composite business key over SR_RECEIPT_ID, SOURCE_ORGANIZATION_ID, VENDOR_ID, and VENDOR_SITE_ID. Together these four columns constitute the documented business-key candidate: the combination that uniquely identifies a source line within its parent receipt organization. Practically, this means a rule cannot contain two identical source records distinguished only by rank or allocation.

• SR_RECEIPT_ID — FK to the parent MRP_SR_RECEIPT_ORG row; defines which sourcing rule or bill of distribution this source line belongs to.
• SOURCE_ORGANIZATION_ID — FK to MTL_PARAMETERS; identifies an internal source organization.
• VENDOR_ID — FK to PO_VENDORS; identifies an external source supplier.
• VENDOR_SITE_ID — the specific supplier site used for the source.
• SOURCE_TYPE — numeric discriminator for the type of source (organization versus supplier).
• ALLOCATION_PERCENT — the percentage of supply allocated to this source within the rule.
• RANK — the priority order of the source; OLD_RANK is documented as no longer in use.
• SECONDARY_INVENTORY — VARCHAR2(10), documented as not currently used.
• SHIP_METHOD — shipping method associated with the source line.
• Standard Who columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — plus REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE for concurrent program traceability.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the descriptive flexfield structure and segments.

Common Use Cases and Queries

Typical usage centers on sourcing rule analysis, supply allocation validation, and planning data reconciliation. A frequent pattern joins the source lines back to their parent receipt organization:

• Listing all sources for a given rule: SELECT * FROM mrp.mrp_sr_source_org WHERE sr_receipt_id = :receipt_id ORDER BY rank;
• Resolving internal sources to organization names via JOIN mtl_parameters mp ON s.source_organization_id = mp.organization_id.
• Resolving supplier sources via JOIN po_vendors v ON s.vendor_id = v.vendor_id, optionally joining the vendor site for address detail.
• Validating allocation: aggregate ALLOCATION_PERCENT by SR_RECEIPT_ID to confirm it totals 100 percent.
• Identifying rows by primary key using the U1 index: WHERE sr_source_id = :id.
• Change-audit reporting using LAST_UPDATE_DATE and the PROGRAM_* columns to trace which concurrent request created or modified a source line.

Related Objects

The following objects are the most significant in relation to MRP_SR_SOURCE_ORG, based on the documented FK and PK relationships:

• MRP.MRP_SR_RECEIPT_ORG — parent table, joined on SR_RECEIPT_ID.
• MRP.MRP_SR_SOURCE_ORG_U1 / _U2 — the unique indexes on SR_SOURCE_ID and on the composite business key.
• MTL_PARAMETERS — referenced via SOURCE_ORGANIZATION_ID for internal source organizations.
• PO_VENDORS — referenced via VENDOR_ID for supplier sources.
• PO_VENDOR_SITES_ALL — implicit companion lookup for VENDOR_SITE_ID enrichment.
• The Define Sourcing Rules and Define Bills of Distribution forms in Oracle Supply Chain Planning, which are the maintenance entry points for this data.