Search Results automatic_flag

Overview

OKC_PRICE_ADJUSTMENTS_HV is an APPS-owned, VALID database view within the Oracle E-Business Suite Contracts Core (OKC) product family. It exposes price adjustment and pricing modifier data maintained against contract and pricing entities, providing a denormalized, read-oriented projection of the underlying price adjustment base table. The "_HV" suffix indicates that this is the "header view" variant defined over the price adjustments history/base structure, typically used to present the current or latest attribute values of pricing modifiers in a form suitable for concurrent programs, forms, and integration interfaces.

In the context of Oracle EBS 12.1.1 and 12.2.2, this object serves as a reporting and integration access point for downstream modules such as Advanced Pricing, Order Management, and Receivables, which consume contract pricing adjustment definitions. Because the view joins directly to base columns without aggregation, it preserves row-level fidelity, allowing callers to filter on flags such as AUTOMATIC_FLAG — the attribute most relevant to the user's search — to distinguish modifiers that apply automatically from those requiring manual invocation.

Underlying Base Objects

Per the documented ETRM metadata, the sole referenced base object is OKC_PRICE_ADJUSTMENTS_H, accessed through an APPS synonym. The alias PATB in the view text confirms that all projected columns are drawn from that table. The view therefore imposes no additional join, filter, or transformation logic beyond column aliasing; it is a straight projection with selected column renames (for example PATB.ID is exposed as ID, PATB.ROWID as ROW_ID, and PATB.ATTRIBUTE2 through ATTRIBUTE15 retain their names). This design means row cardinality and data integrity are governed entirely by the base table, and any DML against OKC_PRICE_ADJUSTMENTS_H is immediately visible through the view.

Key Columns

• AUTOMATIC_FLAG — Indicates whether the price adjustment is applied automatically during pricing evaluation or requires manual selection.
• MODIFIER_MECHANISM_TYPE_CODE — Classifies the modifier mechanism (for example, discount, surcharge, or price break).
• OPERAND / ARITHMETIC_OPERATOR — Defines the value acted upon and the arithmetic operation applied.
• PAT_ID, CHR_ID, CLE_ID, BSL_ID, BCL_ID — Foreign keys to pricing attributes, charge, and price list/benefit structures.
• MODIFIED_FROM / MODIFIED_TO — Effective dating for the adjustment.
• UPDATE_ALLOWED, UPDATED_FLAG, APPLIED_FLAG, ON_INVOICE_FLAG — Workflow and lifecycle control flags.
• ESTIMATED_FLAG, ADJUSTED_AMOUNT, ACCRUAL_FLAG, ACCRUAL_CONVERSION_RATE — Financial and accrual-related attributes.
• LIST_HEADER_ID, LIST_LINE_ID, LIST_LINE_NO, LIST_LINE_TYPE_CODE — Price list linkage.
• ATTRIBUTE1–ATTRIBUTE15, CONTEXT — Descriptive flexfield support.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — Standard audit and optimistic locking columns.

Common Use Cases and Queries

Typical usage centers on identifying and auditing automatic pricing adjustments. The following query lists automatic adjustments for a given price list line:

• SELECT ID, PAT_ID, MODIFIER_MECHANISM_TYPE_CODE, OPERAND, ARITHMETIC_OPERATOR, ADJUSTED_AMOUNT
• FROM APPS.OKC_PRICE_ADJUSTMENTS_HV
• WHERE AUTOMATIC_FLAG = 'Y'
• AND LIST_LINE_ID = :p_list_line_id
• AND TRUNC(SYSDATE) BETWEEN MODIFIED_FROM AND NVL(MODIFIED_TO, SYSDATE);

Other scenarios include extracting adjustment definitions for pricing integration, reconciling accrual-flagged modifiers, and reporting on modifiers linked to specific charge types. Because the view is a direct projection, standard audit columns and OBJECT_VERSION_NUMBER are available for change-detection feeds.