Search Results benefit_uom_code

Overview

OKC_PRICE_ADJUSTMENTS_V is a VALID view owned by the APPS schema in Oracle E-Business Suite and is part of the OKC – Contracts Core product family. Per the ETRM metadata, the view is defined over the OKC_PRICE_ADJUSTMENTS base table and exists to present its contents in a reportable and integration-friendly form. Functionally, OKC_PRICE_ADJUSTMENTS stores the individual price adjustment lines that Oracle Contracts applies to contract pricing, including modifiers, arithmetic operators, pricing phases, and the source pricing list or list line that drives the adjustment.

The view exposes the full operational and audit column set of the underlying table and is therefore the recommended access point for concurrent programs, reports, interfaces, and custom extensions that need read-only access to price adjustment data. Because it is a simple pass-through view with no filtering or joins, it behaves identically to the base table from a query-planning perspective. The ESTIMATED_FLAG column identified in the search is one of several flags that describe the state and nature of each price adjustment row and is available directly from this view.

Underlying Base Objects

The documented base object for this view is OKC_PRICE_ADJUSTMENTS, accessed through a synonym. The view text is a single-table SELECT against that synonym (aliased PATB), projecting columns rather than deriving them, joining to no other tables. As a result, there is a one-to-one row correspondence between the view and OKC_PRICE_ADJUSTMENTS: each row in the table appears exactly once in the view. No WHERE clause restricts the data, so the view is not filtered by status, date range, or business unit.

Because the view preserves the ROWID of the underlying row and exposes the base table's primary key (ID), consumers can use the view for both reporting and controlled updates where the view is treated as an updateable simple view. The presence of OBJECT_VERSION_NUMBER and the WHO columns confirms the view supports optimistic locking and standard audit tracking inherited from the base table.

Key Columns

The view projects the full column list of OKC_PRICE_ADJUSTMENTS. The most significant columns include:

• ID – Primary key identifying the individual price adjustment record.
• PAT_ID – Identifier linking the adjustment to its parent price adjustment template or grouping.
• CHR_ID, CLE_ID, BSL_ID, BCL_ID – Foreign keys to contract, line, and pricing rule entities to which the adjustment applies.
• MODIFIER_MECHANISM_TYPE_CODE, OPERAND, ARITHMETIC_OPERATOR – Define how the adjustment modifies price (for example, percentage or amount applied with a specific operator).
• ESTIMATED_FLAG – Indicates whether the price adjustment is estimated rather than finalized; a key column for pricing review and accrual reporting.
• AUTOMATIC_FLAG, UPDATE_ALLOWED, UPDATED_FLAG, APPLIED_FLAG, ON_INVOICE_FLAG – Control and state flags governing whether the adjustment is applied automatically, whether it has been updated or applied, and whether it appears on invoices.
• MODIFIED_FROM, MODIFIED_TO – Effective date range during which the adjustment is valid.
• PRICING_PHASE_ID – Identifies the pricing phase in which the adjustment is evaluated.
• LIST_HEADER_ID, LIST_LINE_ID, LIST_LINE_TYPE_CODE – References the pricing list header and line that the adjustment derives from.
• ADJUSTED_AMOUNT – The monetary result of applying the adjustment.
• CHARGE_TYPE_CODE, CHARGE_SUBTYPE_CODE – Classify the charge the adjustment applies to.
• RANGE_BREAK_QUANTITY, ACCRUAL_CONVERSION_RATE – Support quantity-based tiering and accrual conversion.
• CHANGE_REASON_CODE, CHANGE_REASON_TEXT – Capture the reason for the adjustment for audit purposes.
• CONTEXT and ATTRIBUTE1–ATTRIBUTE15 – Descriptive flexfield segments.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID, OBJECT_VERSION_NUMBER – Standard WHO and concurrent program audit columns.

Common Use Cases and Queries

Typical uses include pricing review reports, contract audit extracts, and integration queries that feed downstream pricing engines. Because the view is unfiltered, callers typically constrain it by contract identifiers, effective dates, or the flag columns. The following examples illustrate representative access patterns.

• Retrieve all adjustments for a contract: SELECT ID, PAT_ID, CHARGE_TYPE_CODE, OPERAND, ARITHMETIC_OPERATOR, ADJUSTED_AMOUNT FROM OKC_PRICE_ADJUSTMENTS_V WHERE CHR_ID = :p_contract_id;
• Isolate estimated (unconfirmed) adjustments: SELECT ID, PAT_ID, ESTIMATED_FLAG, APPLIED_FLAG, ADJUSTED_AMOUNT FROM OKC_PRICE_ADJUSTMENTS_V WHERE ESTIMATED_FLAG = 'Y';
• Find adjustments with an effective window covering a date: SELECT ID, CHR_ID, MODIFIED_FROM, MODIFIED_TO FROM OKC_PRICE_ADJUSTMENTS_V WHERE :p_date BETWEEN MODIFIED_FROM AND MODIFIED_TO;
• Audit recently modified rows: SELECT ID, CHR_ID, ESTIMATED_FLAG, LAST_UPDATED_BY, LAST_UPDATE_DATE, CHANGE_REASON_CODE FROM OKC_PRICE_ADJUSTMENTS_V WHERE LAST_UPDATE_DATE >= TRUNC(SYSDATE) - 7 ORDER BY LAST_UPDATE_DATE DESC;

For performance, queries should filter on indexed base-table columns such as CHR_ID, PAT_ID, or LIST_HEADER_ID, since the view inherits all indexes of OKC_PRICE_ADJUSTMENTS. Insert, update, and delete operations are possible through the view because it is a simple, key-preserving view, but direct DML against the base table is generally preferred for controlled maintenance. The ESTIMATED_FLAG column specifically supports use cases requiring separation of provisional versus finalized pricing adjustments for reporting and accrual accuracy.