Results for “so_pricing_rules_b”

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

Overview

SO_PRICING_RULES_B is the base (non-translated) header table in the Oracle Order Entry (OE) schema that stores the definition of pricing rules within Oracle E-Business Suite Release 12.1.1 and 12.2.2. Pricing rules act as the governing construct that links an item group or a price list line to a reusable set of pricing logic. Each row in the table represents a single pricing rule header, identified by the surrogate primary key PRICING_RULE_ID, and is subsequently referenced by pricing rule line detail tables, item group line definitions, and price list line records.

The table belongs to the Oracle Pricing and Order Management family of objects. In practice it is populated and maintained through the pricing rule setup user interface and the Pricing Engine, rather than through direct DML. Where a price list or item group must be associated with a specific pricing formula or calculation context, the headers stored here are the anchor point. Under a heuristic Data Vault classification mined from the foreign key structure, SO_PRICING_RULES_B is hub-leaning: it presents a durable business key (PRICING_RULE_ID) that links outward to multiple dependent and detail entities, which is characteristic of a hub. This is offered as a modeling suggestion only, not as a physical design in the shipped applications schema.

Key Information Stored

The table is documented with 25 physical columns in the OE schema. Two rows of metadata are especially important.

• PRICING_RULE_ID — The surrogate primary key, enforced by the constraint SO_PRICING_RULES_B_PK and reinforced by the unique index SO_PRICING_RULES_B_U1. It is also the business-key candidate documented for the object, since no other unique index is present. Consumers and foreign tables join to this column.
• FORMULA — Holds the expression or formula reference that defines how pricing is calculated for the rule. This is the functional payload of the header and is evaluated by the pricing engine during price list processing and order line pricing.
• START_DATE_ACTIVE / END_DATE_ACTIVE — Effective-dating columns that determine when the pricing rule becomes active and when it expires. Queries that need currently valid rules typically filter on these against SYSDATE.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN capture the standard EBS who/when audit trail, supporting reconciliation and change-tracking reports.
• CONTEXT and ATTRIBUTE1 through ATTRIBUTE15 — The standard DFF (Descriptive Flexfield) columns. CONTEXT identifies which attribute set applies, while ATTRIBUTE1–15 store the context-dependent values configured by the implementation.

No descriptive or translated name column is present in the documented base table, which is why the object is named with the _B suffix; translated names, where used, are stored in the corresponding _TL counterpart outside the documented structure.

Common Use Cases and Queries

The most common requirement is to enumerate active pricing rules and their associated detail lines for a given price list or item group.

• Reporting on currently effective rules: SELECT PRICING_RULE_ID, FORMULA, START_DATE_ACTIVE, END_DATE_ACTIVE FROM OE.SO_PRICING_RULES_B WHERE TRUNC(SYSDATE) BETWEEN START_DATE_ACTIVE AND NVL(END_DATE_ACTIVE, TRUNC(SYSDATE)+1);
• Joining rule headers to their line values for a pricing audit: the query links SO_PRICING_RULES_B to OE_PRC_RULE_LINE_VALUES or SO_PRICING_RULE_LINES on PRICING_RULE_ID to reconstruct the full rule definition.
• Identifying which rules reference a specific item group, by joining through SO_ITEM_GROUP_LINES on PRICING_RULE_ID.
• Change-history reporting using LAST_UPDATE_DATE and LAST_UPDATED_BY to support SOX or audit reviews of pricing configuration.
• DFF-based segmentation, filtering on CONTEXT and specific ATTRIBUTE columns to summarize rules by implementation-defined category.

Because the table is an application-owned header, direct updates are discouraged; changes are normally applied through the pricing setup forms or the supported concurrent processes.

Related Objects

The documented foreign key relationships identify the principal dependent and referencing objects. In each case the join column is PRICING_RULE_ID matching SO_PRICING_RULES_B.PRICING_RULE_ID.

• SO_PRICING_RULE_LINES — Detail lines that define the conditions and values belonging to each pricing rule header.
• OE_PRICING_RULE_LINES — The OE-schema counterpart of the pricing rule line detail.
• OE_PRC_RULE_LINE_VALUES — Stores the value-level attributes of a rule line, forming the lowest granularity of the rule definition.
• SO_ITEM_GROUP_LINES — Associates item groups with the pricing rule applied to them.
• OE_ITEM_GROUP_LINES — The OE-schema item group line object referencing the same header.
• SO_PRICE_LIST_LINES_115 — Price list lines that reference a pricing rule for list price computation.

Collectively these objects form the pricing rule constellation, with SO_PRICING_RULES_B acting as the hub that anchors rule headers to item group, price list, and rule line consumers across the OE schema.