Search Results mrp_ap_sr_rules_sn
Overview
The view MRP_AP_SOURCING_RULES_V belongs to the Oracle E-Business Suite product family MRP – Master Scheduling/MRP. It exposes sourcing rule definitions used by the planning engine to determine how demand is satisfied — whether through existing on-hand inventory, internal transfers, or external procurement. Sourcing rules are central to the Oracle Advanced Supply Chain Planning (ASCP) and Master Scheduling/MRP sourcing logic, and this view provides a stable, query-friendly projection of the underlying sourcing rule tables.
Within the EBS 12.1.1 and 12.2.2 environments, the view is part of the documented object dictionary (ETRM). The ETRM metadata explicitly notes "Not implemented in this database" for its implementation/DBA data, indicating that coverage exists primarily as documented reference rather than as a live-installed object in the inspected instance. Its documented view text shows it is defined over a single source object, MRP_AP_SR_RULES_SN.
The view is commonly encountered in reporting and integration work where planners or interface programs need to enumerate sourcing rules, their organizational scope, and their planning status without navigating the full internal naming conventions of the base table.
Underlying Base Objects
The ETRM metadata documents one referenced base object: MRP_AP_SR_RULES_SN. The "SN" suffix in Oracle's sourcing model is characteristically associated with sourcing rule definition records in the Advanced Planning sourcing hierarchy. The view applies a simple projection: it renames the rule key and name columns, carries through organization and descriptive attributes, and appends a derived row identifier (RN) aliased as RN1.
- Base object: MRP_AP_SR_RULES_SN
- Relationship type: one-to-one projection (no joins documented)
- Owner/schema: not documented in ETRM for this view
Because the metadata documents no additional base objects, consumers should treat the view as a thin layer over the sourcing rule table rather than as a composite of assignment, bill-of-distribution, or sourcing hierarchy tables.
Key Columns
The view exposes the following columns as documented:
- SOURCING_RULE_ID — Surrogate primary key of the sourcing rule record.
- SOURCING_RULE_NAME — User-defined name identifying the rule, used in assignment and planning logic.
- ORGANIZATION_ID — The inventory organization to which the rule belongs; supports multi-org filtering.
- DESCRIPTION — Free-text description of the rule's purpose.
- STATUS — Lifecycle status of the rule record.
- SOURCING_RULE_TYPE — Classification of the rule (for example, whether it governs sourcing, bill of distribution, or related assignment semantics).
- PLANNING_ACTIVE — The flag most relevant to the searched term "planning_active". This attribute indicates whether the sourcing rule is enabled and considered by the planning engine during a planning run. Rules where this flag is inactive are excluded from sourcing decisions.
- RN1 — An alias of the base column
RN, functioning as a row identifier in the underlying source.
Common Use Cases and Queries
Typical scenarios include auditing which rules are active for planning, verifying organizational coverage, and feeding downstream integration extracts. To list all planning-active sourcing rules:
SELECT SOURCING_RULE_ID, SOURCING_RULE_NAME, ORGANIZATION_ID, SOURCING_RULE_TYPE
FROM MRP_AP_SOURCING_RULES_V
WHERE PLANNING_ACTIVE = 'Y';
To find rules for a specific organization:
SELECT SOURCING_RULE_NAME, DESCRIPTION, STATUS
FROM MRP_AP_SOURCING_RULES_V
WHERE ORGANIZATION_ID = :org_id
AND PLANNING_ACTIVE = 'Y';
Because the ETRM documentation marks the view as not implemented in the examined database, developers should confirm its live presence in their instance before relying on it in production queries, and fall back to MRP_AP_SR_RULES_SN where necessary.
-
View: MRP_AP_SOURCING_RULES_V
12.2.2
product: MRP - Master Scheduling/MRP , implementation_dba_data: Not implemented in this database ,
-
View: MRP_AP_SOURCING_RULES_V
12.1.1
product: MRP - Master Scheduling/MRP , implementation_dba_data: Not implemented in this database ,