Results for “breakpoint_factor”

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

Overview

OP_PRCE_BRK is a GML (Process Manufacturing Logistics) schema table that stores the price break definitions attached to items on a pricelist. In Oracle EBS pricing architecture, a pricelist line establishes a base or list price for an item; OP_PRCE_BRK extends that line with quantity-dependent or value-dependent tiers, allowing a single item to carry multiple price points that vary according to the breakpoint reached. The table is owned by GML and is marked VALID in the ETRM 12.2.2 documentation set, with the same object present in 12.1.1.

From a Data Vault modeling perspective, the FK structure suggests a satellite-leaning classification: OP_PRCE_BRK carries a PRICE_ID foreign key back to the pricelist item table, positioning it as descriptive, time-varying detail hanging off the item-level business key rather than acting as an independent hub or link.

Key Information Stored

The documented physical schema contains fourteen columns. The most significant are:

• BREAKTYPE_ID — surrogate primary key (OP_PRCE_BRK_PK), uniquely identifying each price break row.
• PRICE_ID — foreign key to OP_PRCE_ITM, tying the break to the parent pricelist item line.
• LINE_NO — sequence number ordering the breaks within a given pricelist item.
• QTY_BREAKPOINT — the quantity threshold at which a new price break applies.
• VALUE_BREAKPOINT — the monetary or value threshold for the break, used in value-based pricing.
• BREAKPOINT_FACTOR — the multiplier applied to derive the break price.
• BREAKPOINT_PRICE — the actual price applicable once the breakpoint is reached.
• DELETE_MARK — soft-delete flag; 1 indicates the row is logically deleted.
• TRANS_CNT — transaction counter used for concurrency and change tracking.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns recording who created and last modified the record.

The business-key candidate is the composite unique index OP_PRCE_BRK_U1 over PRICE_ID, LINE_NO, QTY_BREAKPOINT, and VALUE_BREAKPOINT, which guarantees that no two breaks overlap within the same pricelist line and threshold combination.

Common Use Cases and Queries

Typical usage centers on retrieving the effective price for a given order quantity. A reporting query joins OP_PRCE_BRK to OP_PRCE_ITM and selects the highest QTY_BREAKPOINT not exceeding the ordered quantity:

• SELECT p.price_id, p.item_id, b.qty_breakpoint, b.breakpoint_price FROM op_prce_brk b, op_prce_itm p WHERE b.price_id = p.price_id AND b.delete_mark = 0 AND b.qty_breakpoint <= :ordered_qty ORDER BY b.qty_breakpoint DESC.
• Validating pricelist integrity — detecting gaps or overlaps between consecutive LINE_NO values for a PRICE_ID.
• Auditing price maintenance activity using CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, and LAST_UPDATE_DATE.
• Reporting volume- or value-based discount tiers for procurement and sales analysis.

Related Objects

The primary relationship is the foreign key OP_PRCE_BRK.PRICE_ID → OP_PRCE_ITM, which makes OP_PRCE_ITM the principal parent object for any join. Additional significant objects in the GML pricing family include OP_PRCE_HDR (pricelist headers), OP_PRCE_LST (pricelist definitions), and the related order and item master tables used to resolve item identifiers. Pricelist maintenance and price-break retrieval are typically driven through GML pricing APIs and concurrent programs rather than direct DML, but direct SQL against OP_PRCE_BRK remains common for reporting and validation. Any query must filter DELETE_MARK = 0 to exclude logically deleted rows.