Search Results so_pricing_rule_line_values




Overview
Explore in AI Chat

Overview

The SO_PRICING_RULE_LINE_VALUES table is a core data object within the Oracle E-Business Suite (EBS) Order Entry (OE) module, specifically for releases 12.1.1 and 12.2.2. It functions as a child table in the pricing rules architecture, storing the specific column values that define the conditions for a pricing rule step. Its primary role is to hold the discrete data points against which order line attributes are evaluated to determine if a pricing rule qualifies and applies a discount, surcharge, or other price adjustment. The table is essential for the execution of complex, multi-step, and attribute-based pricing strategies within the order management lifecycle.

Key Information Stored

The table's structure is designed to store multi-dimensional condition values. Its primary key is a composite of seven columns, emphasizing the granularity of the data. The key columns are PRICING_RULE_ID and STEP_NUMBER, which link the values to a specific step within a specific pricing rule defined in the parent SO_PRICING_RULE_LINES table. The remaining five columns, VALUE1 through VALUE5, hold the actual conditional data. These columns typically correspond to the attributes selected in the pricing rule setup, such as specific item numbers, category IDs, customer classifications, or price list identifiers. The exact meaning of each VALUE column is context-dependent on the rule's configuration.

Common Use Cases and Queries

A primary use case is troubleshooting pricing rule application failures. Analysts query this table to verify the exact criteria a rule step is checking. Common SQL patterns involve joining to the parent rule lines and header tables to get a complete view of a rule's logic. For example, to audit all value conditions for a specific pricing rule, one might use:

  • SELECT rule_line.rule_number, line_values.*
  • FROM oe.so_pricing_rule_line_values line_values,
  • oe.so_pricing_rule_lines rule_lines,
  • oe.so_pricing_rules rule_header
  • WHERE line_values.pricing_rule_id = rule_lines.pricing_rule_id
  • AND line_values.step_number = rule_lines.step_number
  • AND rule_lines.pricing_rule_id = rule_header.pricing_rule_id
  • AND rule_header.rule_number = '&RULE_NUMBER';

Reporting use cases include generating a catalog of all pricing rule conditions for compliance reviews or analyzing the distribution of rules based on the types of values stored (e.g., how many rules are based on Item versus Category).

Related Objects

The table has a direct and critical foreign key relationship with the SO_PRICING_RULE_LINES table, which defines the rule steps. The relationship is enforced on the columns SO_PRICING_RULE_LINE_VALUES.PRICING_RULE_ID and SO_PRICING_RULE_LINE_VALUES.STEP_NUMBER referencing SO_PRICING_RULE_LINES. This design makes SO_PRICING_RULE_LINE_VALUES a dependent child table; a row cannot exist without a corresponding step in SO_PRICING_RULE_LINES. The pricing rule lines table itself is a child of SO_PRICING_RULES (headers). This object is integral to the pricing engine and is referenced by internal OE APIs and views that process order pricing, though direct external APIs for manipulation are typically based on the higher-level pricing rule entities.