Results for “ozf_offers”

50+ results




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

Overview

OZF_OFFERS is the core header table for Oracle Trade Management offers in Oracle E-Business Suite 12.1.1 and 12.2.2. It resides in the OZF schema, which is owned by the Trade Management module, and functions as a surrogate extension to QP_LIST_HEADERS_B, the Oracle Advanced Pricing list header table. Where QP_LIST_HEADERS_B stores the generic pricing list definition shared across price lists, modifier lists, and qualification lists, OZF_OFFERS captures the attributes unique to trade promotions and offers: lifecycle status, performance (accrual/earning) dates, lumpsum offer types, budget linkage, volume tier behavior, and autopay configuration. Every offer row in OZF_OFFERS is anchored to a row in QP_LIST_HEADERS_B through the QP_LIST_HEADER_ID foreign key, so the two tables are read together in virtually every functional query.

From a Data Vault modeling perspective, the FK structure suggests classifying OZF_OFFERS as a hub. It carries its own surrogate key (OFFER_ID), two strong business keys (OFFER_CODE and QP_LIST_HEADER_ID), and is referenced by a large family of satellite-style detail and forecasting tables, which is consistent with hub behavior.

Key Information Stored

The documented physical schema contains 63 columns. The most operationally significant are:

Common Use Cases and Queries

Typical scenarios include offer status reporting, performance-period (accrual) reporting, budget consumption tracking, and revaluation of open accruals. A canonical join pulls the offer header together with its pricing list header:

SELECT o.offer_code, o.offer_type, o.status_code, o.perf_date_from, o.perf_date_to, qlh.name
FROM ozf_offers o, qp_list_headers_b qlh
WHERE o.qp_list_header_id = qlh.list_header_id
AND o.org_id = :p_org_id;

A second pattern enumerates offers in a given status window or by owner, using USER_STATUS_ID or OWNER_ID. A third pattern aggregates accruals by joining OZF_OFFER_PERFORMANCES on USED_BY_ID and OZF_OFFER_QUALIFIERS on OFFER_ID. Because child tables are keyed by OFFER_ID, always drive child queries from the parent key. Indexes U1 (OFFER_ID), U2 (QP_LIST_HEADER_ID), and U3 (OFFER_CODE) support the most common access paths.

Related Objects

The most frequently referenced objects in the OZF_OFFERS ecosystem are: