Search Results mrp_sourcing_rules_u2

Overview

MRP.MRP_SOURCING_RULES is a core Oracle E-Business Suite table within the MRP (Material Requirements Planning) schema that stores the header definitions of sourcing rules and bills of distribution. In Oracle EBS 12.1.1 and 12.2.2, this table functions as the master repository for sourcing rule names, descriptions, and organizational context, and it is populated through the Define Sourcing Rule form in the Oracle Advanced Supply Chain Planning and MRP application modules. Each row represents a single sourcing rule or bill of distribution header, which downstream planning engines use to determine how demand is allocated across supply sources, organizations, and suppliers.

The object carries a VALID status and resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10. The documented physical schema identifies 32 columns, and the table is classified heuristically as hub-leaning within a Data Vault modeling perspective. This classification suggests that MRP_SOURCING_RULES is best modeled as a hub entity, with dependent detail (such as receipt organization assignments) represented as satellites or links. The primary key, MRP_SOURCING_RULES_PK, is defined on SOURCING_RULE_ID.

Key Information Stored

The table's most significant columns include:

• SOURCING_RULE_ID — Numeric surrogate primary key uniquely identifying each sourcing rule or bill of distribution. Documented as the PK column and as the single-column unique index MRP_SOURCING_RULES_U1.
• SOURCING_RULE_NAME — VARCHAR2(50) business name of the sourcing rule or bill of distribution. Combined with ORGANIZATION_ID, it forms the composite unique index MRP_SOURCING_RULES_U2, making it a business-key candidate.
• ORGANIZATION_ID — Numeric organization identifier establishing the owning organization for the rule. Part of the composite unique business key with SOURCING_RULE_NAME.
• DESCRIPTION — VARCHAR2(80) free-text description of the rule's purpose.
• STATUS — Numeric column documented as not currently used.
• SOURCING_RULE_TYPE — Numeric column documented as not currently used.
• PLANNING_ACTIVE — Flag indicating whether the rule is active for planning purposes.
• ATTRIBUTE_CATEGORY — VARCHAR2(30) descriptive flexfield structure defining column.
• ATTRIBUTE1 through ATTRIBUTE15 — VARCHAR2(150) descriptive flexfield segments for client-specific extension data.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard Who audit columns capturing creation and modification metadata.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program context columns identifying the batch process that last touched the row.

Common Use Cases and Queries

Sourcing rules drive procurement, transfer, and distribution decisions in ASCP, MRP, and Inventory. Common reporting scenarios include identifying all sourcing rules for a given organization, auditing rule changes, and validating that receipt organizations are correctly attached to a rule header.

A typical query resolves a rule by its composite business key:

• SELECT sourcing_rule_id, sourcing_rule_name, description FROM mrp.mrp_sourcing_rules WHERE sourcing_rule_name = :name AND organization_id = :org_id;

Another frequent pattern lists all active rules for an organization:

• SELECT sourcing_rule_id, sourcing_rule_name, planning_active FROM mrp.mrp_sourcing_rules WHERE organization_id = :org_id AND planning_active = 1 ORDER BY sourcing_rule_name;

Auditing queries exploit the Who and concurrent program columns to trace rule creation or modification by user and request.

Related Objects

The documented foreign key relationship shows that MRP_SR_RECEIPT_ORG.SOURCING_RULE_ID references MRP.MRP_SOURCING_RULES.SOURCING_RULE_ID, meaning each receipt organization assignment depends on a parent sourcing rule header. This child table stores the organization-level receipt details that complete a bill of distribution definition. Beyond this documented FK, related objects in the sourcing model typically include the assignment and detail tables that consume SOURCING_RULE_ID to link rules to items, organizations, and suppliers, as well as the Define Sourcing Rule form and associated concurrent programs recorded in the PROGRAM_ID columns. Reporting views in the MRP schema frequently join MRP_SOURCING_RULES to MRP_SR_RECEIPT_ORG and organization master tables to present complete sourcing definitions. When building queries, the primary link to preserve is the SOURCING_RULE_ID join between MRP_SOURCING_RULES and MRP_SR_RECEIPT_ORG.