Search Results mrp_sr_receipt_org_pk

Overview

MRP_SR_RECEIPT_ORG is a table in the MRP (Master Scheduling/MRP) schema of Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the receiving organizations associated with sourcing rules and bills of distribution. In Oracle's supply chain planning architecture, a sourcing rule defines how a demand is fulfilled — from which source organization, supplier, or external source — and to which destination it flows. This table captures the destination or receipt side of that relationship, acting as the authoritative record of which inventory organizations (receiving organizations) may satisfy a given sourcing rule.

The table is central to multi-organization distribution planning, where a single sourcing rule can feed multiple receiving organizations. Each row links a sourcing rule to a specific receipt organization, bounded by an effective date range, enabling time-phased sourcing configurations. From a Data Vault modeling perspective, the table is heuristically classified as satellite-leaning: it holds descriptive, time-varying attributes (effective/disable dates, audit columns, and a set of DFF attributes) keyed by a surrogate identifier, which is characteristic of a satellite surrounding a business key rather than a pure hub or link.

Key Information Stored

The table contains 30 documented columns. The primary key is the surrogate SR_RECEIPT_ID, which uniquely identifies each receipt-organization assignment row. Business-key uniqueness is enforced by two unique indexes: MRP_SR_RECEIPT_ORG_U1 on SR_RECEIPT_ID and MRP_SR_RECEIPT_ORG_U2 on the composite of SOURCING_RULE_ID, RECEIPT_ORGANIZATION_ID, and EFFECTIVE_DATE.

• SR_RECEIPT_ID — surrogate primary key for the row.
• SOURCING_RULE_ID — foreign key to MRP_SOURCING_RULES; the rule to which this receipt organization applies.
• RECEIPT_ORGANIZATION_ID — foreign key to MTL_PARAMETERS; identifies the receiving (destination) inventory organization.
• EFFECTIVE_DATE — start of the validity window for the assignment.
• DISABLE_DATE — end of the validity window, after which the assignment is inactive.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield (DFF) columns for customer-defined extensions.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — standard EBS audit columns.
• LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program and session context columns.

Common Use Cases and Queries

Typical uses include reporting active sourcing-rule assignments per receiving organization, validating time-phased distribution configurations, and reconciling planning data before running MRP or ASCP. A representative query joining a receipt organization to its rule and organization name is:

• List active receipt organizations for a sourcing rule: select RECEIPT_ORGANIZATION_ID from MRP_SR_RECEIPT_ORG where SOURCING_RULE_ID = :p_rule and SYSDATE between EFFECTIVE_DATE and NVL(DISABLE_DATE, SYSDATE+1).
• Join to MTL_PARAMETERS on RECEIPT_ORGANIZATION_ID = ORGANIZATION_ID to resolve organization names.
• Join to MRP_SOURCING_RULES on SOURCING_RULE_ID to enumerate rule attributes alongside destinations.
• Audit recently changed assignments using LAST_UPDATE_DATE and LAST_UPDATED_BY.

Related Objects

The table participates in a small but tightly coupled network:

• MRP_SOURCING_RULES — parent of SOURCING_RULE_ID; defines the rule.
• MTL_PARAMETERS — parent of RECEIPT_ORGANIZATION_ID; supplies organization context.
• MRP_SR_SOURCE_ORG — child referencing SR_RECEIPT_ID, holding the source side of the assignment.
• MRP_SR_RECEIPT_ORG_U1 and MRP_SR_RECEIPT_ORG_U2 — unique indexes enforcing business-key integrity.

Together these objects model the full source-to-destination mapping used by Oracle planning engines.