Search Results ozf_offer_adj_rltd_lines




Overview
Explore in AI Chat

Overview

The OZF_OFFER_ADJ_RLTD_LINES table resides in the OZF schema and belongs to the Oracle Trade Management module. It exists to support Trade Deal offer adjustments, specifically the scenario in which a single deal line carries two modifiers. In such cases, the table records the relationship between the two constituent offer adjustment lines, effectively acting as a bridge between the underlying pricing list lines. The from_list_line_id and to_list_line_id columns are foreign keys to the list_line_id column in the QP (Advanced Pricing) schema, which anchors the Trade Management adjustment configuration to the pricing engine.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign key structure is standalone. This suggests the table is best treated as an independent construct rather than being folded into a strict hub or satellite pattern. It carries its own surrogate key and does not exhibit a dependent-child or pure link topology, so modelers seeking to represent it in a warehouse should preserve it as a self-contained entity, optionally decomposed into a hub (offer adjustment line) plus a link to the QP list line references.

Key Information Stored

The table contains eleven documented columns. The surrogate primary key is offer_adj_rltd_line_id, which is also enforced by the unique index OZF_OFFER_ADJ_RLTD_LINES_U1; this makes it the business-key candidate for the row as well as the technical identifier. The most operationally significant columns are:

  • offer_adj_rltd_line_id — surrogate primary key and unique business key of the relationship row.
  • offer_adjustment_id — identifies the parent offer adjustment to which the relationship belongs.
  • from_list_line_id — the originating QP list line in the relationship (FK reference to QP list_line_id).
  • to_list_line_id — the destination QP list line in the relationship (FK reference to QP list_line_id).
  • security_group_id — foreign key to FND_SECURITY_GROUPS, enforcing multi-tenant / business-group data isolation.
  • object_version_number — optimistic locking version used by the Oracle Forms/ADF layer to prevent concurrent update conflicts.
  • creation_date, created_by — standard WHO audit columns recording insert metadata.
  • last_update_date, last_updated_by, last_update_login — audit columns capturing the most recent modification and session context.

Together, from_list_line_id and to_list_line_id encode the directional pairing that defines how two modifiers relate on one deal line. The offer_adjustment_id groups related pairs under a single adjustment header. The absence of descriptive attributes (names, dates of effect) means the table is primarily structural and relational rather than descriptive.

Common Use Cases and Queries

Typical uses center on reconstructing the modifier pairs applied within a Trade Deal, validating that both legs of a two-modifier deal line were correctly persisted, and reporting on pricing adjustment relationships for audit or reconciliation against QP list lines. A common query joins the relationship table to itself or to the offer adjustment header to expose the pair:

  • Extracting all related line pairs for a given adjustment: SELECT * FROM ozf.ozf_offer_adj_rltd_lines WHERE offer_adjustment_id = :p_id;
  • Resolving both list lines in a single row: a self-join or two lookups into QP list lines keyed on from_list_line_id and to_list_line_id.
  • Security-filtered reporting: filter by security_group_id to respect business-group partitioning.
  • Change tracking: order by last_update_date to identify recently modified relationships for integration or data-quality checks.

Related Objects

  • FND_SECURITY_GROUPS — referenced by security_group_id; governs access partitioning.
  • QP list line table (list_line_id) — the pricing source referenced by from_list_line_id and to_list_line_id.
  • OZF offer adjustment header — the parent identified by offer_adjustment_id, grouping related line pairs.
  • OZF_OFFER_ADJ_RLTD_LINES_PK / _U1 — the primary key constraint and unique index enforcing offer_adj_rltd_line_id.
  • Trade Management deal/offer APIs and concurrent programs — consuming processes that populate and reconcile these relationships.