Search Results get_customer_total_amnts




Overview
Explore in AI Chat

Overview

QP_CROSS_ORDER_VOLUME_LOAD is an Oracle E-Business Suite pricing package owned by the APPS schema. Its name and procedure set indicate that it supports Advanced Pricing functionality related to cross-order volume or cross-order amount-based qualifiers — that is, pricing qualifications that evaluate a customer's cumulative purchasing activity across multiple orders rather than a single order line. The package builds and maintains the derived data used by the pricing engine to determine whether a customer qualifies for volume or amount-based price breaks accumulated over a defined period.

The header comment records a revision date of 2006 and a "noship" status, confirming the package is an internal, non-shipped implementation object rather than a public API. The ETRM records its owner as APPS and classifies it as OTHER, meaning Oracle does not document it as a supported extension point. The package spec exposes a small set of worker procedures and helper functions that transform order history and customer total amounts into pricing qualification data.

Key Procedures and Functions

  • CREATE_CROSSORDVOL_BRK — the primary worker procedure. It accepts an organization identifier and a load effective date, and is responsible for building or refreshing the cross-order volume records for the specified organization and effective period. Because the package as a whole references the qualified list and pricing attribute tables, this procedure is the likely entry point that drives the qualification load.
  • GET_CUSTOMER_TOTAL_AMNTS — reads and returns the accumulated customer total amounts for up to three cross-order volume periods, resolved against a supplied set of book (SOB) currency context. This is the procedure the searched term targets, so it is the documented interface through which cumulative customer purchase values are surfaced for qualification evaluation.
  • GET_UOM_CODE — a function that returns the unit-of-measure code for a given inventory item and organization, used to normalize quantities before cross-order volume comparison.
  • GET_CONVERTED_QTY — a function that converts an ordered quantity into the unit of measure required for volume accumulation, taking the item, organization, source quantity, and source UOM as inputs.
  • GET_VALUE — a function that resolves a period value against date and tolerance inputs, returning the numeric value used in qualification or break computation.
  • CONVERT_TO_BASE_CURR — a function that converts a transaction amount from a source currency to a target currency using a supplied conversion date, rate, and conversion type, ensuring cross-order amounts are compared on a consistent currency basis.

Tables Accessed

The documented table list reflects both order history and pricing setup. Order data is sourced from OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL, which supply the transactions whose amounts and quantities are accumulated. Customer-level roll-ups are read from OE_CUST_TOTAL_AMTS_ALL, and item-level customer volumes from OE_ITEM_CUST_VOLS_ALL; these are the derived tables central to cross-order qualification. MTL_SYSTEM_ITEMS is joined to resolve item attributes and UOM information.

Pricing setup is accessed through QP_PRICING_ATTRIBUTES, QP_QUALIFIERS, QP_LIST_HEADERS, and QP_LIST_LINES. These tables define the price lists, qualifiers, and attribute mappings that determine which cross-order volume rules exist and when they apply. The package therefore reads order and item data and aligns it with the pricing model defined in the QP schema.

Usage Notes

QP_CROSS_ORDER_VOLUME_LOAD is an internal pricing engine component. It is referenced by one other package in the documented metadata, indicating it is invoked programmatically by the pricing qualification or pricing engine layer rather than called directly by end users. Its operation is scoped by organization and by an effective date passed to CREATE_CROSSORDVOL_BRK, consistent with a batch or concurrent refresh that rebuilds cumulative cross-order volumes on a schedule.

Because the package is flagged as non-shipped and classified as OTHER, custom code should not call it directly. The safe integration surface for cross-order volume or customer total amount requirements is the supported Oracle Pricing public APIs and the underlying OE and QP data model, not this package. Reimplementing the logic of GET_CUSTOMER_TOTAL_AMNTS or CONVERT_TO_BASE_CURR in a custom wrapper risks divergence from the internal behavior, which Oracle may change without notice.