Search Results so_pricing_rule_lines




Overview
Explore in AI Chat

Overview

The SO_PRICING_RULE_LINES table is a core transactional data object within the Oracle E-Business Suite (EBS) Order Entry (OE) module, specifically for versions 12.1.1 and 12.2.2. It functions as the child table to SO_PRICING_RULES_B, storing the detailed, sequential steps that define a pricing rule's logic. A pricing rule is a configurable engine component used to calculate complex prices, charges, or adjustments on sales orders. Each row in this table represents a single step in the rule's execution flow, allowing for sophisticated, multi-step pricing calculations that can incorporate formulas, conditions, and lookups. Its existence is critical for implementing advanced, rule-based pricing strategies beyond standard price lists.

Key Information Stored

The table's structure is designed to manage the sequence and components of a pricing rule. Its composite primary key, consisting of PRICING_RULE_ID and STEP_NUMBER, enforces uniqueness and defines the execution order of steps within a specific rule. The PRICING_RULE_ID is a foreign key linking the line directly to its parent rule definition in SO_PRICING_RULES_B. A crucial column is FORMULA_COMPONENT_ID, which references SO_RULE_FORMULA_COMPONENTS. This link associates each rule step with a specific mathematical or logical formula component, such as an operand, operator, or function, that defines the action of that step. Other columns typically include attributes to control step execution logic, though the provided metadata specifically confirms the core structural columns of the primary and foreign keys.

Common Use Cases and Queries

This table is primarily accessed for troubleshooting pricing rule execution, auditing rule definitions, and generating reports on active pricing logic. A common scenario involves diagnosing why a particular charge was calculated on an order. A developer or analyst would trace from the order line to the applied pricing rule and then query the rule's steps to review the calculation sequence. A fundamental query retrieves all steps for a given rule, ordered for clarity:

  • SELECT step_number, formula_component_id FROM oe.so_pricing_rule_lines WHERE pricing_rule_id = <RULE_ID> ORDER BY step_number;

Another critical use case is identifying all pricing rules that utilize a specific formula component, which is essential for impact analysis before modifying a shared component:

  • SELECT DISTINCT prl.pricing_rule_id FROM oe.so_pricing_rule_lines prl WHERE prl.formula_component_id = <COMPONENT_ID>;

Related Objects

SO_PRICING_RULE_LINES sits at the center of a key relationship hierarchy within the pricing engine. It has defined foreign key relationships with the following objects:

  • SO_PRICING_RULES_B: The parent table. Each line must belong to a valid pricing rule header (join on PRICING_RULE_ID).
  • SO_RULE_FORMULA_COMPONENTS: Provides the formula logic for each step. The line references a specific component via FORMULA_COMPONENT_ID.
  • SO_PRICING_RULE_LINE_VALUES: A child table that stores specific input values or parameters for each rule step. It references SO_PRICING_RULE_LINES using the composite key (PRICING_RULE_ID, STEP_NUMBER).

This structure creates a chain: SO_PRICING_RULES_B (header) → SO_PRICING_RULE_LINES (steps) → SO_PRICING_RULE_LINE_VALUES (step parameters), with SO_RULE_FORMULA_COMPONENTS as a shared master source for calculation logic.