Search Results op_chrg_brk

Overview

The OP_CHRG_BRK table is a core data object within the Oracle E-Business Suite (EBS) Process Manufacturing Logistics (GML) module. It functions as a detail table, storing the specific charge break records that define how a charge is calculated. In the context of logistics and process manufacturing, charges often apply to transactions based on tiered or bracketed criteria, such as quantity ranges, weight slabs, or distance bands. This table holds the individual breakpoints or tiers that constitute the complete pricing or costing rule for a given charge. Its primary role is to support the detailed configuration and application of complex freight, handling, or other logistical charges within the supply chain.

Key Information Stored

The table's structure is designed to link a break record to a master charge definition and define its specific parameters. The metadata indicates three critical columns. The CHRGBREAK_ID serves as the unique primary identifier for each individual break record. The CHARGE_ID is a foreign key column that links the break back to its parent charge master record in the OP_CHRG_MST table. The LINE_NO column is used to sequence multiple break records within a single charge, ensuring the correct order for tiered calculations. While the specific business rule columns (e.g., break quantity, rate, UOM) are not detailed in the provided excerpt, they would typically reside in this table to define the threshold and the resulting charge amount or percentage for that specific tier.

Common Use Cases and Queries

This table is central to any process that calculates applied charges for logistics transactions. A common use case is generating a report of all tiered rates configured for a specific freight charge. The following query pattern would retrieve the sequenced break details for a given CHARGE_ID:

• SELECT charge_id, line_no, [break_qty], [rate] FROM gml.op_chrg_brk WHERE charge_id = <ID> ORDER BY line_no;

Another critical use case is during transaction processing, where the system queries this table to find the applicable break tier based on the transaction's quantity or weight. For instance, determining the correct freight charge for a shipment weight would involve a query to find the record where the shipment weight falls between the defined break ranges for a specific charge. Data fixes or audits may also target this table to update rate values or correct the sequencing of breaks within a charge structure.

Related Objects

The OP_CHRG_BRK table has a direct and essential relationship with the OP_CHRG_MST table, as defined by its foreign key. OP_CHRG_MST holds the header-level definition of the charge (e.g., charge name, type, effective dates), while OP_CHRG_BRK stores the detailed tier rules. Any application logic or interface that creates or updates charge breaks will likely interact with this table pair. While not specified in the metadata, this table is also expected to be referenced by key GML APIs responsible for charge calculation and by various inventory, shipping, or cost management reports that need to display the breakdown of applied charges.