Results for “charge_id”

50+ results




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

Overview

OP_CHRG_BRK is a charge breaks table in the Oracle EBS Process Manufacturing Logistics (GML) schema, holding the breakpoint definitions that drive tiered or graduated pricing and charge calculations. In process manufacturing, charges such as freight, handling, or surcharges are frequently computed in bands rather than at a flat rate — for example, a tariff that changes at a defined weight or value threshold. Each row in OP_CHRG_BRK represents one such break, capturing the quantity or value boundary at which the charge rate or factor changes, along with the resulting price and factor values applicable to that band.

The table is owned by the GML schema and its documented physical schema contains 14 columns. It carries two unique indexes: OP_CHRG_BRK_PK on the surrogate key CHRGBREAK_ID, and OP_CHRG_BRKI1 on the composite business key (CHARGE_ID, LINE_NO). A single foreign key relates OP_CHRG_BRK.CHARGE_ID to OP_CHRG_MST, tying each break line to its parent charge definition.

Under the heuristic Data Vault classification mined from the FK structure, OP_CHRG_BRK leans satellite. This is a modeling suggestion rather than a physical design statement: the table carries descriptive and qualifying attributes (breakpoints, factors, prices) that hang off a parent hub or link keyed by CHARGE_ID, and would typically be modeled as a satellite on the charge key, with effectivity or change tracking spanning the LINE_NO sequence.

Key Information Stored

The table distinguishes its surrogate key from its business-key candidates, which is important both for indexing and for understanding row identity:

  • CHRGBREAK_ID — the surrogate primary key (index OP_CHRG_BRK_PK). This is the technical unique identifier used for referential integrity and programmatic access.
  • CHARGE_ID — the foreign key to OP_CHRG_MST and the first component of the composite business key OP_CHRG_BRKI1. It identifies the parent charge to which the break belongs.
  • LINE_NO — the second component of OP_CHRG_BRKI1 and the sequence number that orders breaks within a charge. Combined with CHARGE_ID, it uniquely identifies a break line in business terms.
  • QTY_BREAKPOINT — the quantity threshold at which the charge tier changes; the quantity-based band boundary.
  • VALUE_BREAKPOINT — the monetary or value threshold at which the charge tier changes; the value-based band boundary.
  • BREAKPOINT_FACTOR — the multiplicative factor applied once the corresponding breakpoint is reached.
  • BREAKPOINT_PRICE — the price or rate associated with the band defined by the breakpoint.
  • TRANS_CNT — a transaction count column, typically used for multi-row or concurrent update control.
  • DELETE_MARK — the soft-delete flag; a nonzero value indicates a logically deleted break line that should be filtered in most queries.
  • Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — provide standard Oracle EBS who/when tracking on insert and update.

Common Use Cases and Queries

Typical usage is resolving the applicable price or factor for a given charge and quantity or value, and reporting the full break structure of a charge.

Retrieve all active breaks for a charge in line order:

  • SELECT charge_id, line_no, qty_breakpoint, value_breakpoint, breakpoint_factor, breakpoint_price FROM op_chrg_brk WHERE charge_id = :charge_id AND NVL(delete_mark,0) = 0 ORDER BY line_no;

Resolve the band applicable to a supplied quantity by selecting the highest breakpoint not exceeding that quantity:

  • SELECT breakpoint_factor, breakpoint_price FROM op_chrg_brk WHERE charge_id = :charge_id AND qty_breakpoint <= :qty AND NVL(delete_mark,0) = 0 ORDER BY qty_breakpoint DESC; — take the first row.

Reporting scenarios include charge setup verification (ensuring breakpoints are contiguous and non-overlapping within a charge), pricing audits comparing effective factors across charges, and data migration or interface loads where break lines are staged and loaded in LINE_NO order.

Related Objects

  • OP_CHRG_MST — the parent charge master. Joined via OP_CHRG_BRK.CHARGE_ID = OP_CHRG_MST.CHARGE_ID; the primary relationship for any query needing charge headers alongside their break lines.
  • OP_CHRG_BRKI1 — the composite unique index on (CHARGE_ID, LINE_NO) that enforces the business key and supports ordered retrieval of breaks per charge.
  • OP_CHRG_BRK_PK — the primary key index on CHRGBREAK_ID, used for single-row lookups and referential checks.
  • Charge and pricing setup forms/APIs in the GML module — these maintain OP_CHRG_MST and its OP_CHRG_BRK detail lines together, so inserts and updates to break lines should respect the parent charge and LINE_NO sequencing.