Search Results check_duplicate_line_charges

Overview

OE_CHARGE_PVT is an internal, private PL/SQL package in the APPS schema that encapsulates the pricing and charge calculation logic used throughout Oracle Order Management. The "PVT" suffix in Oracle E-Business Suite naming conventions denotes a private API — one intended for invocation by other application packages and forms rather than by customer extensions. In this role, OE_CHARGE_PVT serves as the central engine for computing order-level charges, including freight, cost, and receivable-related amounts, and for validating that charges are not duplicated across order headers and lines. It is a foundational dependency of the public OE_ORDER_PUB API, meaning that virtually every order created or modified through the Order Management interface ultimately relies on this package to resolve charge amounts against the Advanced Pricing (QP) engine.

Key Procedures and Functions

The package exposes ten documented procedures and functions:

• GET_CHARGE_AMOUNT — derives the charge amount applicable to an order entity, returning the value resolved from pricing and charge definitions.
• GET_COST_TYPES — retrieves the cost type definitions relevant to charge determination.
• GET_COST_AMOUNT — returns the calculated cost associated with an order line or charge.
• GET_SHIPPED_STATUS — determines the shipment status used to qualify whether a charge applies.
• CHECK_DUPLICATE_LINE_CHARGES — validates that a charge is not redundantly applied to an order line.
• CHECK_DUPLICATE_HEADER_CHARGES — performs the equivalent duplication check at the order header level.
• CHECK_DUPLICATE_CHARGES — the general duplication-checking routine covering both header and line contexts.
• GET_LINE_WEIGHT_OR_VOLUME — retrieves line-level weight or volume, which frequently serves as the basis for freight charges.
• FREIGHT_DEBUG — a diagnostic routine for troubleshooting freight charge resolution.
• GET_REC_CHARGE_AMOUNT — returns receivable-related charge amounts.

Tables Accessed

OE_CHARGE_PVT accesses its data through APPS synonyms. Order and charge data are read from OE_ORDER_LINES_ALL and OE_PRICE_ADJUSTMENTS, with the latter holding the price adjustment records generated by Advanced Pricing. Weight and volume qualification draws on QP_QUALIFIERS and QP_PRICING_ATTRIBUTES. The pricing engine context is established through QP_EVENT_PHASES, QP_PRICING_PHASES, QP_LIST_HEADER_PHASES, and QP_LIST_LINES, which together define modifier list phases and their applicability. PLITBLM is used as the pricing list line table structure supporting charge resolution logic.

Usage Notes

OE_CHARGE_PVT is not a public API and should not be called directly by custom code; Oracle documents it as referenced by six other packages. It is invoked by OE_CHARGE_PVT's own dependent packages, notably OE_COMMITMENT_PVT and OE_ORDER_PUB, and by the Order Management forms OE_OE_FORM_HEADER, OE_OE_FORM_LINE, OE_OE_TOTALS_SUMMARY, and OE_TOTALS_GRP. It is also referenced by the concurrent program XML publisher component ONT_OEXOEWFR_XMLP_PKG. Developers extending Order Management should route charge-related logic through OE_ORDER_PUB rather than this private package, as its signature is not guaranteed across releases. Understanding these dependencies is nonetheless valuable when troubleshooting freight, cost, or duplicate-charge issues in Oracle EBS 12.1.1 and 12.2.2.