Search Results lock_control




Overview
Explore in AI Chat

Overview

OKX_ORD_PRC_ADJ_ATRBS_V is a seeded Oracle E-Business Suite view owned by the APPS schema and classified under the OKX – Contracts Integration product family. It exposes the attribute-level detail of price adjustments that govern order pricing within Oracle Order Management, and it is consumed by the Contracts Integration flows that synchronize pricing structures between Order Management and Oracle Contracts. In EBS 12.1.1 and 12.2.2, the view is registered as VALID, meaning its definition compiles successfully against the referenced base object and can be queried directly by reporting tools, concurrent programs, and integration APIs without modification.

The view is deliberately narrow in scope: it projects the pricing-attribute rows that qualify a given price adjustment, including the context in which the attribute applies, the comparison operator, the from/to value ranges, and the lock control flag. Because the definition is a straightforward projection rather than a join, it functions as a read-only convenience layer over the underlying Order Management table, shielding integration code from future changes to the base table’s physical layout.

Underlying Base Objects

The view is defined over a single documented base object, OE_PRICE_ADJ_ATTRIBS, accessed through a synonym in the APPS schema. No additional joins, unions, or aggregations are documented in the view text, so the row cardinality of OKX_ORD_PRC_ADJ_ATRBS_V matches the qualifying rows of OE_PRICE_ADJ_ATTRIBS. Each row carries PRICE_ADJUSTMENT_ID, which is the foreign key back to the parent price adjustment header, allowing the attribute detail to be joined to the adjustment definition and, in turn, to the list or modifier that owns it.

Because it is a view and not a materialized object, querying it always reflects the current committed state of OE_PRICE_ADJ_ATTRIBS. There is no denormalization, no snapshot, and no incremental refresh to manage. This makes the view safe for real-time reporting but also means that performance characteristics are inherited directly from the base table and its indexes.

Key Columns

  • PRICE_ADJUSTMENT_ID — Identifier of the parent price adjustment; the join key to the adjustment header.
  • PRICE_ADJ_ATTRIB_ID — Primary identifier for the individual attribute row.
  • PRICING_CONTEXT — Context in which the attribute is evaluated, typically indicating the qualifier entity such as the order, the line, or the customer.
  • PRICING_ATTRIBUTE — The specific attribute being qualified, for example an order type or a customer segment.
  • PRICING_ATTR_VALUE_FROM / PRICING_ATTR_VALUE_TO — The lower and upper bounds of the attribute value range against which the adjustment is tested.
  • COMPARISON_OPERATOR — The operator applied when comparing the incoming value to the from/to range.
  • FLEX_TITLE — Descriptive flexfield context or title associated with the attribute definition.
  • LOCK_CONTROL — The lock control flag that governs whether the attribute row is protected from modification, and the specific column users most often search for when diagnosing why a price adjustment attribute cannot be edited or why an integration update is being rejected.

Common Use Cases and Queries

The most frequent use of this view is auditing and troubleshooting price adjustment attributes, particularly the LOCK_CONTROL flag. Integration developers and functional analysts query it to determine which attribute rows are locked before attempting updates through the Contracts Integration interface.

To retrieve all attributes for a specific price adjustment:

  • SELECT PRICE_ADJUSTMENT_ID, PRICING_CONTEXT, PRICING_ATTRIBUTE, PRICING_ATTR_VALUE_FROM, PRICING_ATTR_VALUE_TO, COMPARISON_OPERATOR, LOCK_CONTROL FROM APPS.OKX_ORD_PRC_ADJ_ATRBS_V WHERE PRICE_ADJUSTMENT_ID = :p_adjustment_id;

To isolate locked attribute rows across the instance:

  • SELECT PRICE_ADJUSTMENT_ID, PRICE_ADJ_ATTRIB_ID, PRICING_ATTRIBUTE, LOCK_CONTROL FROM APPS.OKX_ORD_PRC_ADJ_ATRBS_V WHERE LOCK_CONTROL IS NOT NULL;

To inspect the operator distribution for a given pricing context:

  • SELECT PRICING_ATTRIBUTE, COMPARISON_OPERATOR, COUNT(*) FROM APPS.OKX_ORD_PRC_ADJ_ATRBS_V WHERE PRICING_CONTEXT = :p_context GROUP BY PRICING_ATTRIBUTE, COMPARISON_OPERATOR;

These queries are read-only and can be executed against a reporting copy of the database. Because the view has no restrictive predicates, always constrain it by PRICE_ADJUSTMENT_ID or another selective column when querying a production instance.