Results for “estimated_amount”

50+ results




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

Overview

OZF_RELATED_DEAL_LINES is a Trade Management (OZF) transaction table in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the relationship between two modifiers that participate in a single Trade Deal Offer deal line. In Trade Management, a deal line can be governed by two modifiers simultaneously — for example, a primary discount plus a secondary accrual or a complementary qualifier. Rather than duplicating the offer structure, OZF_RELATED_DEAL_LINES records the pairing so that both list lines remain independently defined in Oracle Advanced Pricing while being consumed together by the deal.

Both MODIFIER_ID and RELATED_MODIFIER_ID are foreign keys to LIST_LINE_ID in QP_LIST_LINES, and QP_LIST_HEADER_ID is a foreign key to OZF_OFFERS. Consequently, the table functions as an associative structure linking two pricing entities to one offer. The mined Data Vault classification is a link table, which is a reasonable modeling suggestion: it carries no descriptive history of its own beyond the relationship and its boundaries, and its natural grain is the pairing of two modifiers.

Key Information Stored

The table contains 16 documented columns. The most significant are:

Common Use Cases and Queries

The table is queried primarily to resolve which two modifiers make up a deal line, and to retrieve the estimated quantity or amount ceilings associated with that pairing. A typical join retrieves both modifier definitions from Advanced Pricing:

  • Offer-to-modifier reporting: join OZF_RELATED_DEAL_LINES to OZF_OFFERS on QP_LIST_HEADER_ID to list all modifier pairings for a given deal.
  • Pricing resolution: join MODIFIER_ID and RELATED_MODIFIER_ID to QP_LIST_LINES (twice, using aliases) to obtain each modifier's list header, list line type, and pricing attributes.
  • Exposure analysis: aggregate ESTIMATED_AMOUNT by offer, honoring the ESTIMATED_AMOUNT_IS_MAX flag to distinguish ceiling values from expected values.
  • Quantity variance reporting: compare ESTIMATED_QTY against actual accrual or shipment quantities, grouping by ESTIMATE_QTY_UOM.

A representative query pattern joins the table to QP_LIST_LINES twice on the two modifier columns, filters by QP_LIST_HEADER_ID, and applies the security group predicate SECURITY_GROUP_ID to respect the operating unit context. The MODIFIER_ID search term most commonly originates from this join path, since users typically begin with a known modifier and need to find the offers in which it participates.

Related Objects

  • QP_LIST_LINES — referenced twice, via MODIFIER_ID and RELATED_MODIFIER_ID to LIST_LINE_ID. This is the primary dependency and the target of modifier_id lookups.
  • OZF_OFFERS — referenced via QP_LIST_HEADER_ID; the parent offer or deal header.
  • QP_LIST_HEADERS — reached through QP_LIST_LINES; supplies the pricing list context (list type, currency, effective dates) for each modifier.
  • FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID; governs row-level access.
  • OZF_RELATED_DEAL_LINES_PK / _U1 — the primary key constraint and unique index on RELATED_DEAL_LINES_ID.
  • OZF deal and offer APIs — the Trade Management offer creation and update logic that populates this table when dual-modifier deal lines are defined.

Because the table is a link between pricing list lines and offers, it should always be joined with QP_LIST_LINES or OZF_OFFERS rather than reported in isolation; the surrogate key alone carries no business meaning.