Search Results adjust_backdated_offer




Overview
Explore in AI Chat

Overview

OZF_ADJUSTMENT_EXT_PVT is a private (PVT-classified) PL/SQL package in the APPS schema that supports the Oracle E-Business Suite Trade Management (formerly Oracle Advanced Pricing / Channel Revenue Management) adjustment and accrual engine. In the ETRM 12.2.2 metadata it is listed with a VALID status and is documented as being invoked by, and returning control to, the OZF_ACCRUAL_ENGINE package. Its principal business role is to calculate, validate and post customer and volume-based adjustment amounts that arise from backdated offers, volume offers, and their utilization, and to feed the results back into the accrual and funds-utilization process. The package therefore sits at the point where supplier accrual entitlements are translated into order-level or line-level adjustments, using pricing engine views and order management tables as source data.

Key Procedures and Functions

The ETRM documentation lists ten documented procedures and functions within the package. These are grouped functionally as follows:

  • ADJUST_VOLUME_OFFER — drives the adjustment process for volume-based offers.
  • ADJUST_BACKDATED_OFFER — handles adjustments where an offer is applied retrospectively to transactions already processed.
  • VOLUME_OFFER_ADJUSTMENT — computes the adjustment amount for a volume offer.
  • VOLUME_OFFER_UTIL_ADJUSTMENT — computes the adjustment arising from the utilization of a volume offer against accrued funds.
  • GET_ORDER_AMOUNT_QUANTITY — retrieves the order amount and quantity that form the basis of the adjustment calculation.
  • PROCESS_RESULT — the generic result-processing routine that posts or records the computed adjustment.
  • PROCESS_VO_RESULT — variant of the result processor specific to volume offer output.
  • PROCESS_SSD_RESULT — variant of the result processor for the SSD (supplier-specific discount / special settlement) result path.
  • PROCESS_PRICING_RESULT — processes results returned from the pricing engine and applies the corresponding adjustment.

The procedures are internally organized so that the calculation routines call the appropriate PROCESS_* result handler after the amount has been determined. Exact parameter signatures are not published in the metadata and should not be assumed.

Tables Accessed

The package reads and writes a defined set of APPS synonymous tables. Order data is sourced from OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL, with pricing detail read through OE_PRICE_ADJUSTMENTS and the pricing line-detail view QP_LDETS_V. Customer identity and site data are resolved through HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES_ALL and HZ_CUST_SITE_USES_ALL. Offer and funds configuration is held in OZF_OFFERS, OZF_OFFER_ADJUSTMENTS_B, OZF_FUNDS_ALL_B and OZF_FUNDS_UTILIZED_ALL_B, while OZF_MARKET_PRESET_TIERS and OZF_DENORM_QUERIES supply denormalized market and eligibility criteria. Adjustment eligibility staging and activity tracking use OZF_ADJ_TEMP_ELIGIBILITY, OZF_ACTIVITY_CUSTOMERS and OZF_ACTIVITY_PRODUCTS. FND_API is used for the standard API error/return-status conventions.

Usage Notes

Because the package is classified as private (PVT), it is not part of the public API surface and should not normally be called directly from customer code. It is designed to be invoked by OZF_ACCRUAL_ENGINE and by other OZF packages during the accrual and adjustment lifecycle, typically behind concurrent programs that process offers, backdated adjustments and volume offer utilization. In the ETRM 12.2.2 update it is referenced by one other package, consistent with a controlled internal call hierarchy. Customizations that need adjustment logic should preferably use the accrual engine entry points rather than calling OZF_ADJUSTMENT_EXT_PVT procedures directly, since the interface and internal ordering of PROCESS_* calls may vary between releases such as 12.1.1 and 12.2.2.