Search Results range_break_quantity




Overview
Explore in AI Chat

Overview

OE_AK_LINE_PRCADJS_V is an APPS-owned database view in Oracle E-Business Suite, classified under the Order Management (ONT) product family. Its status is VALID in both the 12.1.1 and 12.2.2 releases. The view presents order line price adjustment information in a form suited to Oracle Application Framework (OAF) "AK" (Attribute/Kanban-style) query regions and to external integrations that require a denormalized, flat representation of price adjustment detail.

The object exposes one row per price adjustment applied to an order line, combining pricing modifier attributes, rebate/accrual attributes, tax attributes, and descriptive flexfield context columns. Because the view carries pricing-phase, modifier-level, and rebate-specific columns, it is directly relevant to users searching on rebate_payment_system_code. That column is part of a set of rebate-related fields (REBATE_TRANSACTION_TYPE_CODE, REBATE_TRANSACTION_REFERENCE, REDEEMED_DATE, REDEEMED_FLAG, ACCRUAL_FLAG, and similar) that support the accrual and redemption accounting performed by Oracle Advanced Pricing and Order Management rebate processing.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over the base object OE_PRICE_ADJUSTMENTS_V. The view text confirms this: the SELECT list is drawn from OE_PRICE_ADJUSTMENTS, the underlying adjustments entity, and the final FROM clause references the adjustments source. OE_AK_LINE_PRCADJS_V therefore acts as a presentation layer over the adjustments view, adding literal and RPAD-derived columns for OAF display context while passing through nearly all business columns unchanged.

This places the view one layer above OE_PRICE_ADJUSTMENTS_V, which itself resolves to the price adjustment tables (OE_PRICE_ADJUSTMENTS). Consequently, the view inherits the base object's pricing modifier structure: list header and list line references, modifier mechanism type, operand and arithmetic operator, adjusted-from and adjusted-to ranges, and price break information.

Key Columns

Common Use Cases and Queries

Typical uses include rebate accrual reconciliation, pricing analysis for order lines, and integration extracts feeding external rebate settlement engines. A common query retrieves rebate adjustments for a given order line, filtered by payment system:

SELECT line_id, price_adjustment_id, rebate_transaction_type_code, rebate_payment_system_code, accrual_flag, redeemed_flag, adjusted_amount FROM apps.oe_ak_line_prcadjs_v WHERE line_id = :p_line_id AND rebate_payment_system_code IS NOT NULL;

To summarize accrued rebates by payment system across a period, users aggregate on REBATE_PAYMENT_SYSTEM_CODE with ACCRUAL_FLAG and ADJUSTED_AMOUNT, and join to order headers for customer and date filters. For OAF-based inquiry pages, the view's RPAD-generated display columns and CHAR(1) indicators are consumed directly by the framework to render read-only adjustment grids. Because the view is based on OE_PRICE_ADJUSTMENTS_V, all queries should account for the underlying pricing phase and modifier level logic when interpreting adjusted amounts.