Results for “ozf_offer_adjustments_b”

50+ results




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

Overview

OZF_OFFER_ADJUSTMENTS_B is the base table in the Oracle Trade Management (OZF) module that stores all adjustments applied to an offer. In Oracle EBS 12.1.1 and 12.2.2, offers represent promotional or trade programs created by channel, sales, or marketing organizations, and adjustments define the specific incentive mechanics — such as discounts, rebates, accruals, or lump-sum settlements — attached to those offers. Each row in this table represents a single offer adjustment header, identified by the surrogate primary key OFFER_ADJUSTMENT_ID.

The table resides in the OZF schema with 32 documented columns. From a Data Vault modeling perspective, the FK structure suggests classifying this entity as hub-leaning: OFFER_ADJUSTMENT_ID functions as a durable business key, with descriptive attributes such as EFFECTIVE_DATE, STATUS_CODE, and SETTLEMENT_CODE attached. This structure supports the interpretation that OZF_OFFER_ADJUSTMENTS_B behaves as a central hub for adjustment identities, with child tables (translations, lines, and tiers) acting as satellites or dependent details.

Key Information Stored

The most significant columns in OZF_OFFER_ADJUSTMENTS_B are:

Common Use Cases and Queries

Typical implementations query this table to report adjustment headers by offer, filter by status or effective date, or join to child tables to reconstruct the full adjustment definition. A common query retrieves all active adjustments for a specific offer:

  • SELECT oa.OFFER_ADJUSTMENT_ID, oa.STATUS_CODE, oa.SETTLEMENT_CODE, oa.EFFECTIVE_DATE FROM OZF.OZF_OFFER_ADJUSTMENTS_B oa WHERE oa.LIST_HEADER_ID = :offer_id AND oa.STATUS_CODE = 'APPROVED';
  • Reporting on approved adjustments over a date range: filter on APPROVED_DATE between period start and end.
  • Extracting settlement breakdowns by SETTLEMENT_CODE for accrual versus off-invoice reconciliation.
  • Retrieving descriptive text via the translation table OZF_OFFER_ADJUSTMENTS_TL, joined on OFFER_ADJUSTMENT_ID with the appropriate LANGUAGE column.
  • Data migration or integration extracts using CREATION_DATE and LAST_UPDATE_DATE as incremental watermarks.
  • Security-aware queries that constrain SECURITY_GROUP_ID against FND_SECURITY_GROUPS.

Related Objects

  • OZF_OFFERS — Parent table; joined via OZF_OFFER_ADJUSTMENTS_B.LIST_HEADER_ID = OZF_OFFERS.LIST_HEADER_ID.
  • OZF_OFFER_ADJUSTMENTS_TL — Translation table holding language-specific names and descriptions; joins on OFFER_ADJUSTMENT_ID.
  • OZF_OFFER_ADJUSTMENT_LINES — Child table defining adjustment lines; joins on OFFER_ADJUSTMENT_ID.
  • OZF_OFFER_ADJUSTMENT_TIERS — Child table defining tiered thresholds and rates; joins on OFFER_ADJUSTMENT_ID.
  • FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID for row-level access control.

The TL, LINES, and TIERS tables form the dependent hierarchy of an adjustment and must be queried together to fully resolve the business definition of an offer adjustment.