Search Results op_cntr_brk_uk




Overview
Explore in AI Chat

Overview

The OP_CNTR_BRK table is a core data object within the Oracle E-Business Suite (EBS) Process Manufacturing Logistics (GML) module. It serves as the primary repository for storing price break information associated with contracts. This table is essential for implementing tiered pricing models, where the unit price of an item is adjusted based on achieving specific quantity or value thresholds. Its role is to define the precise conditions and corresponding pricing adjustments that apply to a contract line, enabling sophisticated and automated pricing calculations within the procurement and sales processes of Process Manufacturing.

Key Information Stored

The table's structure is designed to capture the parameters of a price break. The primary key (OP_CNTR_BRK_PK) is the BREAKTYPE_ID, which uniquely identifies each price break record. A unique key (OP_CNTR_BRK_UK) is also defined on the combination of PRICE_ID, LINE_NO, QTY_BREAKPOINT, and VALUE_BREAKPOINT, ensuring data integrity for the breakpoint definitions. The critical columns include:

  • PRICE_ID: The foreign key linking the price break to its parent contract detail line in the OP_CNTR_DTL table.
  • LINE_NO: A sequence number, likely used to order multiple price breaks for a single contract line.
  • QTY_BREAKPOINT: The quantity threshold at which the price break becomes effective.
  • VALUE_BREAKPOINT: The monetary value threshold that can alternatively trigger the price break.
  • BREAKTYPE_ID: The unique identifier for the price break type, which may determine the calculation method (e.g., discount percentage, fixed new price).

Common Use Cases and Queries

This table is central to pricing engines during order entry and invoice generation. A common use case is determining the applicable unit price for a contract line item by comparing the ordered quantity against the defined QTY_BREAKPOINT values. For reporting, analysts query this table to audit contract pricing tiers or analyze discount structures. A typical SQL pattern involves joining OP_CNTR_BRK to OP_CNTR_DTL and the main contracts header table to retrieve a full pricing schedule.

SELECT ctr.contract_num,
       dtl.line_num,
       brk.line_no,
       brk.qty_breakpoint,
       brk.value_breakpoint
FROM   gml.op_cntr_brk brk,
       gml.op_cntr_dtl dtl,
       gml.op_cntr_hdr ctr
WHERE  brk.price_id = dtl.price_id
AND    dtl.contract_id = ctr.contract_id
AND    ctr.contract_num = '<CONTRACT_NUMBER>'
ORDER BY dtl.line_num, brk.qty_breakpoint;

Related Objects

The OP_CNTR_BRK table has a direct and critical relationship with the OP_CNTR_DTL table, as defined by its foreign key constraint on the PRICE_ID column. This establishes that price breaks are child records to contract detail lines. The table is also intrinsically linked to the broader contracts hierarchy, which includes OP_CNTR_HDR for header information. Programs and APIs within the GML module that perform pricing calculations, contract copying, or price maintenance will read from and write to this table to manage tiered pricing logic.