Results for “program_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OKX_QTE_PRC_ADJ_RLSHP_V is a read-only view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the OKX product family, which governs Contracts Integration and the flow of quoting and pricing data between Oracle Advanced Pricing/Quoting and downstream order and contract entities. The view exposes price adjustment relationship records—the model that links a primary price adjustment on a quote line to one or more related price adjustments—so that integration and reporting consumers can query quoting and pricing relationships without directly touching the underlying Advanced Pricing application tables. Because it is a thin, column-for-column passthrough of its base object, the view behaves as a reporting and integration surface rather than as a transformation layer.

Underlying Base Objects

The view is defined over a single base object, the synonym ASO_PRICE_ADJ_RELATIONSHIPS. That synonym resolves to the Oracle Advanced Pricing transaction table that physically stores adjustment relationship rows. The view text selects every column from the base object with no joins, filters, expressions, or aggregations, meaning there is a strict one-to-one correspondence between rows in the view and rows in ASO_PRICE_ADJ_RELATIONSHIPS. No additional tables, lookups, or product-specific views are referenced. This simplicity is intentional: OKX integration code can address a stable APPS-owned view while the underlying application table remains owned and maintained by the Advanced Pricing schema.

Key Columns

• ADJ_RELATIONSHIP_ID — Primary key identifier for the adjustment relationship record.
• QUOTE_LINE_ID — The quote line to which the adjustment relationship applies, anchoring the record to a specific line in a quote.
• PRICE_ADJUSTMENT_ID — The primary price adjustment participating in the relationship.
• RLTD_PRICE_ADJ_ID — The related (secondary) price adjustment tied to the primary adjustment. Together with PRICE_ADJUSTMENT_ID this defines the relationship pair.
• QUOTE_SHIPMENT_ID — The quote shipment context for the relationship, supporting shipment-level pricing granularity.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the framework to detect concurrent updates.
• Audit and concurrency columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, and REQUEST_ID provide standard WHO audit trail and concurrent program attribution.

Common Use Cases and Queries

Typical consumers use the view to enumerate how price adjustments on a quote line relate to one another, to migrate or reconcile quoting data during O2C integrations, and to validate that related adjustments are correctly populated before contract generation. A common query retrieves all relationships for a given quote line:

• SELECT adj_relationship_id, quote_line_id, price_adjustment_id, rltd_price_adj_id, quote_shipment_id FROM okx_qte_prc_adj_rlshp_v WHERE quote_line_id = :p_quote_line_id;
• SELECT a.price_adjustment_id, a.rltd_price_adj_id FROM okx_qte_prc_adj_rlshp_v a WHERE a.quote_line_id = :p_quote_line_id AND a.quote_shipment_id = :p_shipment_id;

Because the view carries no filters or joins, it is not intended for direct end-user inquiry screens; it is best used within extraction routines, reconciliation scripts, and integration programs that require a documented, APPS-owned access point to adjustment relationship data. For performance-sensitive loads, restricting by QUOTE_LINE_ID or ADJ_RELATIONSHIP_ID and relying on the underlying indexes on ASO_PRICE_ADJ_RELATIONSHIPS is recommended.