Search Results mrp_sr_receipt_org_u1

Overview

MRP.MRP_SR_RECEIPT_ORG is a transactional child table within the Oracle MRP (Material Requirements Planning) schema that stores the receiving organization assignments associated with Sourcing Rules and Bills of Distribution in Oracle Supply Chain Planning. Each row represents a single receiving organization that participates in a sourcing rule or bill of distribution for a defined date range, allowing planners to model how supply is routed from a source organization to one or more receipt organizations over time. The table is populated primarily through the Define Sourcing Rule and Define Bills of Distribution forms in Oracle Supply Chain Planning, and it is accessed at runtime by planning, sourcing, and bill-of-distribution explosion engines.

The table exhibits a clear parent-child relationship with MRP_SOURCING_RULES: it is a child of that table, and its rows cannot meaningfully exist outside the context of a parent sourcing rule. Under a heuristic Data Vault classification, this object is satellite-leaning — its grain is one row per receipt-organization/effective-date combination tied to a business key defined by the sourcing rule, and its non-key attributes (dates, flags, descriptive flexfield segments) are the kind of descriptive payload typically modeled as satellite attributes.

Key Information Stored

The table has 30 documented columns. The most significant are listed below.

• SR_RECEIPT_ID — Surrogate primary key (MRP_SR_RECEIPT_ORG_PK) that uniquely identifies each receipt-organization row.
• SOURCING_RULE_ID — Foreign key to MRP_SOURCING_RULES identifying the parent sourcing rule or bill of distribution to which the receipt-organization row belongs.
• RECEIPT_ORGANIZATION_ID — Foreign key to MTL_PARAMETERS identifying the receiving inventory organization. For Local Sourcing Rules this equals the ORGANIZATION_ID in MRP_SOURCING_RULES; for Global Sourcing Rules it is null.
• EFFECTIVE_DATE — The date from which the receipt-organization assignment becomes active.
• DISABLE_DATE — The date on which the receipt-organization assignment expires or is deactivated.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard Who columns providing audit trail metadata.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program context columns identifying which request or program last modified the row.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — Descriptive flexfield structure and segment columns for customer-extensible data.

Two unique indexes enforce business-key semantics: MRP_SR_RECEIPT_ORG_U1 is a single-column unique index on SR_RECEIPT_ID (the surrogate key), while MRP_SR_RECEIPT_ORG_U2 enforces uniqueness across the composite business key of SOURCING_RULE_ID, RECEIPT_ORGANIZATION_ID, and EFFECTIVE_DATE. The U2 index is the more meaningful business-key candidate, since it prevents overlapping effective-dated assignments for the same rule and receipt organization.

Common Use Cases and Queries

Typical reporting and integration scenarios rely on joining this table to its parent sourcing rule and to the inventory organization master to resolve names and attributes. A common pattern retrieves the current valid receipt organizations for a given sourcing rule:

• Fetch active receipt organizations: select r.SOURCING_RULE_ID, r.RECEIPT_ORGANIZATION_ID, r.EFFECTIVE_DATE, r.DISABLE_DATE from MRP_SR_RECEIPT_ORG r where r.SOURCING_RULE_ID = :rule_id and sysdate between nvl(r.EFFECTIVE_DATE, sysdate - 1) and nvl(r.DISABLE_DATE, sysdate + 1).
• Join to MTL_PARAMETERS to resolve the receiving organization code and name for a given RECEIPT_ORGANIZATION_ID.
• Join to MRP_SOURCING_RULES to identify whether the assignment belongs to a local or global sourcing rule or a bill of distribution.
• Audit queries using the Who columns and REQUEST_ID to trace which concurrent program populated or updated receipt-organization rows.
• Extract rows via the MRP_SR_SOURCE_ORG child relationship when reconciling source-to-receipt routing across a distribution network.

Related Objects

The most significant related objects for MRP_SR_RECEIPT_ORG are:

• MRP_SOURCING_RULES — Parent table; joined via MRP_SR_RECEIPT_ORG.SOURCING_RULE_ID = MRP_SOURCING_RULES.SOURCING_RULE_ID.
• MTL_PARAMETERS — Provides the receiving organization definition; joined via MRP_SR_RECEIPT_ORG.RECEIPT_ORGANIZATION_ID = MTL_PARAMETERS.ORGANIZATION_ID.
• MRP_SR_SOURCE_ORG — Child table that references this table through SR_RECEIPT_ID; used together to reconstruct full source-to-receipt routing logic.
• MRP_SR_ASSIGNMENTS / assignment tables — Define which sourcing rules apply to items, categories, or organizations, and are commonly used alongside this table in planning queries.
• MRP_SR_CATEGORY_SETS and related sourcing-rule setup tables — Provide the broader configuration context for how receipt organizations are consumed by planning.
• The Define Sourcing Rule and Define Bills of Distribution forms in Oracle Supply Chain Planning — The primary user interfaces that insert and maintain rows in this table.