Results for “oebv_pricing_rules”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OEBV_PRICING_RULES is a read-only database view in the Oracle E-Business Suite Order Entry (OE) module that exposes the pricing rule definitions stored in the Oracle Advanced Pricing foundation. The view presents one row per pricing rule, carrying the rule identifier, its descriptive name, the pricing formula expression, administratively descriptive text, and the standard effective-dating and audit columns. In Oracle EBS 12.1.1 and 12.2.2 the view functions primarily as a reporting and integration surface: it allows external systems, custom concurrent programs, and BI Publisher reports to retrieve pricing rule metadata without issuing direct queries against the underlying SO_PRICING_RULES table.

The ETRM metadata classifies the object as "Retrofitted," which indicates that the view exists to preserve backward compatibility with an earlier object definition carried forward into the current release. The view text confirms that it is a simple projection of the base table: it selects PRICING_RULE_ID, NAME, FORMULA, DESCRIPTION, START_DATE_ACTIVE, END_DATE_ACTIVE, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, and CREATED_BY from SO_PRICING_RULES, terminating with the WITH READ ONLY clause to enforce non-mutability. The metadata further records the implementation status as "Not implemented in this database," meaning the specific instance from which the ETRM extract was drawn does not contain the view; the definition remains documented for reference and for environments where the object has been deployed.

Underlying Base Objects

The view is defined over a single base object, SO_PRICING_RULES, aliased implicitly within the view text. No additional referenced base objects are documented in the ETRM metadata. SO_PRICING_RULES is the Oracle Advanced Pricing table that stores pricing rule headers, including the rule formula that drives list price, modifier, or qualifier calculations. Because OEBV_PRICING_RULES is a straight column-for-column projection with no joins, unions, or filtering predicates, cardinality is identical to the base table: one row in SO_PRICING_RULES produces exactly one row in the view. The WITH READ ONLY clause prevents DML through the view, ensuring that pricing rule maintenance continues to occur through the supported Advanced Pricing forms and APIs rather than through ad hoc view updates.

Key Columns

• PRICING_RULE_ID — Surrogate primary key identifying each pricing rule; the join key to pricing rule detail and qualifier tables.
• NAME — User-defined rule name presented in pricing rule setup and inquiry screens.
• FORMULA — The expression or formula text that defines how the rule computes its result.
• DESCRIPTION — Free-form descriptive text for the rule.
• START_DATE_ACTIVE / END_DATE_ACTIVE — Effective-dating bounds determining when the rule is valid; a null end date indicates an open-ended rule.
• LAST_UPDATE_DATE / LAST_UPDATED_BY — Standard audit columns recording the most recent modification and its author.
• CREATION_DATE / CREATED_BY — Standard audit columns recording initial row creation and its author.

The ETRM column listing abbreviates the effective-dating columns as START_DATE and END_DATE, while the view text confirms the actual column names are START_DATE_ACTIVE and END_DATE_ACTIVE.

Common Use Cases and Queries

Typical use cases include auditing active pricing rules, extracting rule metadata for data warehousing, and validating rule effective dates during order pricing troubleshooting. A representative query selecting currently active rules is:

SELECT PRICING_RULE_ID, NAME, FORMULA, START_DATE_ACTIVE, END_DATE_ACTIVE FROM OEBV_PRICING_RULES WHERE TRUNC(SYSDATE) BETWEEN START_DATE_ACTIVE AND NVL(END_DATE_ACTIVE, TRUNC(SYSDATE));

A second common pattern inventories rule names and descriptions for integration extracts or reconciliation reports:

SELECT PRICING_RULE_ID, NAME, DESCRIPTION, LAST_UPDATE_DATE FROM OEBV_PRICING_RULES ORDER BY NAME;

Because the view is read-only and unfiltered, all filtering, date logic, and formatting should be applied by the calling query or report.