Search Results mrpbv_sourcing_rules




Overview

MRPBV_SOURCING_RULES is an APPS-owned database view within the Oracle E-Business Suite Master Scheduling/MRP (MRP) product family. It presents a filtered, presentation-ready projection of the sourcing rules defined in the Oracle Advanced Supply Chain Planning and MRP sourcing infrastructure. Specifically, the view exposes sourcing rules of type 1 (the Oracle-defined sourcing rule classification used for supply chain sourcing assignments) whose "planning active" attribute has been resolved against the SYS_YES_NO lookup, so that consumers see a human-readable Yes/No meaning instead of the raw lookup code.

In EBS 12.1.1 and 12.2.2 environments the view is a read-only construct, declared with the WITH READ ONLY clause, and is designed for reporting, integration, and downstream query use rather than for transactional updates. It shields report developers and integration points from having to re-join MRP_SOURCING_RULES to MFG_LOOKUPS manually, and it applies the Oracle row-level security predicate on ORGANIZATION_ID so that multi-org access rules are enforced at query time. Because it is a view definition serialized in the APPS schema, its behavior is consistent across the 12.1.1 and 12.2.2 releases, and the object carries a VALID status in the ETRM dictionary.

Underlying Base Objects

The documented ETRM metadata identifies two referenced base objects: MFG_LOOKUPS (itself a VIEW) and MRP_SOURCING_RULES (referenced through a SYNONYM in the APPS schema). MRP_SOURCING_RULES is the authoritative table holding sourcing rule headers, including the sourcing rule name, description, type, planning-active code, and owning organization. MFG_LOOKUPS provides the lookup meanings used to translate the PLANNING_ACTIVE lookup code into a descriptive value.

The view definition joins MRP_SOURCING_RULES (aliased SO) to MFG_LOOKUPS (aliased LO) on SO.PLANNING_ACTIVE = LO.LOOKUP_CODE, restricted to LO.LOOKUP_TYPE = 'SYS_YES_NO'. It further restricts MRP_SOURCING_RULES to SO.SOURCING_RULE_TYPE = 1 and applies the organization security check against SO.ORGANIZATION_ID. Only rows for which the organization access predicate is satisfied are returned, which is the standard Oracle multi-org behavior for MRP planning objects.

Key Columns

  • SOURCING_RULE — The sourcing rule name, derived from MRP_SOURCING_RULES.SOURCING_RULE_NAME. This is the primary user-facing identifier of the rule.
  • DESCRIPTION — The free-text description of the sourcing rule as maintained on MRP_SOURCING_RULES.
  • PLANNING_ACTIVE_FLAG — The resolved meaning (Yes/No) from MFG_LOOKUPS for the SYS_YES_NO lookup, indicating whether the sourcing rule participates in planning.
  • SOURCING_RULE_ID — The unique surrogate key of the sourcing rule, joining back to MRP_SOURCING_RULES.
  • ORGANIZATION_ID — The inventory organization that owns the sourcing rule; also the column governed by the row-level security predicate.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — Standard Oracle audit columns propagated from MRP_SOURCING_RULES.

Common Use Cases and Queries

Typical uses include validating sourcing rule configuration before a planning run, auditing which rules are planning-active, and feeding sourcing rule metadata into custom reports, extracts, or integration interfaces. The following query lists all planning-active sourcing rules visible to the current organization context:

  • SELECT sourcing_rule, description, planning_active_flag, organization_id FROM apps.mrpbv_sourcing_rules ORDER BY organization_id, sourcing_rule;
  • SELECT sourcing_rule, sourcing_rule_id FROM apps.mrpbv_sourcing_rules WHERE planning_active_flag = 'Yes' AND organization_id = :org_id;

Because the view is read-only and already resolves the lookup and applies organization security, it is well suited for use in BI Publisher reports, Oracle Discoverer workbooks, and custom PL/SQL cursors where sourcing rule reference data is required without directly joining MFG_LOOKUPS.