Search Results mrp_sourcing_rules_pk

Overview

MRP.MRP_SOURCING_RULES is a core Master Scheduling/MRP (MRP) table that stores sourcing rules and bills of distribution used by Oracle E-Business Suite planning engines. A sourcing rule defines how a demand at a given destination organization is fulfilled — whether through a single supplying organization, a specific supplier, or a proportional allocation across multiple sources (a bill of distribution). These rules, in turn, drive planned orders, inter-org transfers, and procurement recommendations generated by the MRP, MPS, DRP, and ASCP planning processes.

In Data Vault modeling terms, the mined foreign-key structure suggests this object is hub-leaning. It carries a surrogate primary key (SOURCING_RULE_ID) referenced by dependent tables, which is characteristic of a hub or a hub-like reference entity. The dependent transactional details that attach to each rule (such as receipt organization allocations) behave more like links or satellites, but the sourcing rule itself functions as a stable business entity surrounded by descriptive attributes.

Key Information Stored

Of the 32 documented columns, the following are the most functionally significant:

• SOURCING_RULE_ID — the surrogate primary key (MRP_SOURCING_RULES_PK). It uniquely identifies each rule and is the column referenced by child tables.
• SOURCING_RULE_NAME and ORGANIZATION_ID — together forming the alternate business key captured in the unique index MRP_SOURCING_RULES_U2, ensuring rule names are unique within an operating unit/organization context.
• SOURCING_RULE_TYPE — distinguishes whether the record represents a global sourcing rule or a bill of distribution, controlling how it is applied during planning.
• STATUS — indicates whether the rule is active or inactive, governing whether the planning engine consumes it.
• PLANNING_ACTIVE — a planning-specific flag controlling participation in MRP/ASCP runs, distinct from general record status.
• DESCRIPTION — free-text documentation of the rule's intent.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle flexfield (DFF) columns for extensible, site-defined attributes.
• LAST_UPDATE_DATE, CREATION_DATE, LAST_UPDATED_BY, CREATED_BY, and LAST_UPDATE_LOGIN — the standard audit columns present across Oracle EBS tables.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE — concurrent program context columns recording the process that last touched the row.

Common Use Cases and Queries

Typical scenarios include reporting all active sourcing rules for a given organization, verifying that planning-active rules exist before an MRP run, and auditing rules modified by a specific concurrent program. A representative query follows:

• SELECT SOURCING_RULE_ID, SOURCING_RULE_NAME, SOURCING_RULE_TYPE, STATUS, PLANNING_ACTIVE FROM MRP.MRP_SOURCING_RULES WHERE ORGANIZATION_ID = :org_id;
• SELECT * FROM MRP.MRP_SOURCING_RULES WHERE SOURCING_RULE_ID = :rule_id; — retrieving a single rule by its surrogate key.
• Joining to MRP_SR_RECEIPT_ORG on SOURCING_RULE_ID to expand each rule into its receipt organizations for distribution analysis.
• Filtering on PLANNING_ACTIVE = 'Y' and STATUS to validate the rule set consumed by a planning run.

These queries support sourcing audits, plan diagnostics, and Oracle Discoverer or BI Publisher reports on distribution networks.

Related Objects

The most significant dependent object is MRP_SR_RECEIPT_ORG, which references this table via MRP_SR_RECEIPT_ORG.SOURCING_RULE_ID → MRP_SOURCING_RULES.SOURCING_RULE_ID. This child table stores the receipt-organization allocations that complete a bill of distribution and is the principal join target when expanding sourcing rules into fulfillment detail. Supporting objects include the sequential source or assignment tables that consume the rule, the organization definition tables (via ORGANIZATION_ID), and the standard concurrent program context tables referenced by REQUEST_ID and PROGRAM_ID. When querying, always qualify the schema as MRP.MRP_SOURCING_RULES and join through SOURCING_RULE_ID to traverse from the hub-like rule header to its allocation detail.