Search Results sourcing_rule




Overview
Explore in AI Chat

Overview

APPS.MRPBV_SOURCING_RULES is a Business Intelligence System (BIS) view in Oracle E-Business Suite, registered under the FND Design Data object MRP.MRPBV_SOURCING_RULES and reported with a status of VALID. The view is owned by the APPS schema and is classified as a view of type "Business Intelligence System view." Its stated purpose is to present sourcing rule names together with their associated descriptions, exposing this sourcing-rule data in a denormalized, read-friendly form suited to reporting and integration rather than transactional maintenance.

In the planning context of Oracle EBS 12.1.1 and 12.2.2, sourcing rules define the prioritized allocation of supply to demand across organizations, suppliers, and shipping networks. The BIS view surfaces that configuration at a level that is convenient for ad hoc queries, Discoverer workbooks, and custom concurrent programs, without requiring the report author to resolve lookup codes or join supporting lookup views manually. The presence of a PLANNING_ACTIVE_FLAG column is significant for users who searched this term: it provides a pre-resolved indicator of whether a given sourcing rule is active for planning purposes, allowing filters such as "show only planning-active rules" to be applied directly.

Underlying Base Objects

The documented ETRM metadata identifies two referenced base objects for APPS.MRPBV_SOURCING_RULES: MFG_LOOKUPS (a VIEW) and MRP_SOURCING_RULES (a SYNONYM). The view is documented as not being referenced by any other database object, which confirms its role as a terminal, presentation-layer artifact rather than a dependency for further application logic.

MRP_SOURCING_RULES is the core planning table that stores sourcing rule headers, including the rule name, description, organization, and the planning-active indicator. MFG_LOOKUPS is the standard Oracle Manufacturing lookup view, and it is used here to translate the stored lookup code in the planning-active column into a meaningful value for reporting. This explains the wider-than-expected VARCHAR2(80) length of PLANNING_ACTIVE_FLAG in the column list: the view likely exposes the decoded lookup meaning rather than the raw one-character code. Because the view is defined over these two objects, it inherits the security and data visibility of the APPS schema and reflects changes made to the underlying sourcing-rule definitions immediately.

Key Columns

  • SOURCING_RULE VARCHAR2(50) — the name of the sourcing rule, the primary human-readable identifier.
  • DESCRIPTION VARCHAR2(80) — the descriptive text associated with the sourcing rule.
  • PLANNING_ACTIVE_FLAG VARCHAR2(80) — indicates whether the sourcing rule is active for planning; this is the column of interest for the search term "planning_active_flag" and is a primary filter criterion.
  • SOURCING_RULE_ID NUMBER — the unique surrogate key of the sourcing rule, used for joins to detail tables such as sourcing-rule assignments.
  • ORGANIZATION_ID NUMBER — the inventory organization to which the sourcing rule belongs.
  • LAST_UPDATE_DATE / LAST_UPDATED_BY — audit columns recording the most recent modification.
  • CREATION_DATE / CREATED_BY — audit columns recording the initial creation of the record.

Common Use Cases and Queries

The view is typically used to list sourcing rules for a given organization, to identify which rules are planning-active, and to join rule names back to assignment or sourcing detail data. A standard listing query is:

  • SELECT SOURCING_RULE, DESCRIPTION, PLANNING_ACTIVE_FLAG, SOURCING_RULE_ID, ORGANIZATION_ID FROM APPS.MRPBV_SOURCING_RULES;
  • Filtering planning-active rules: add WHERE PLANNING_ACTIVE_FLAG = 'Y' (or the decoded lookup meaning returned by the view).
  • Organization-specific reporting: add WHERE ORGANIZATION_ID = :org_id to scope results to one inventory organization.
  • Audit review: select the LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, and CREATED_BY columns to trace who defined or changed a sourcing rule.

Because the view is a BIS artifact, it is best consumed for read-only reporting and integration extracts. Any change to sourcing-rule definitions must be made through the standard planning setup forms against the base table, after which the view reflects the new values.