Results for “ozf_offer_products_temp”

24 results




Overview
Explore in AI Chat

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

Overview

OZF_OFFER_PRODUCTS_TEMP is a staging table within the Oracle Trade Management (OZF) module of Oracle E-Business Suite, holding nine documented columns in release 12.2.2. Per the ETRM metadata, the table stores all products defined for the request of only active offers created through Oracle Trade Management, temporarily populated when a full refresh is performed through the associated concurrent program. It therefore functions as a transient work area rather than a persistent transactional store; rows are meaningful only for the duration of the refresh cycle that created them.

The heuristic Data Vault classification mined from the foreign-key structure is standalone. In modeling terms this suggests the object does not participate in a classic hub-link-satellite constellation within the OZF warehouse model; it is a self-contained staging entity keyed on a single surrogate identifier. Its dependency edges point outward to shared reference tables rather than to other OZF transactional hubs, which reinforces the view that it is populated and consumed entirely within one concurrent program run.

Key Information Stored

  • OFFER_PRODUCT_ID — the surrogate primary key, enforced by OZF_OFFER_PRODUCTS_TEMP_PK. This is the column most frequently referenced in user searches and in downstream joins.
  • QP_LIST_HEADER_ID — identifies the associated price list header, linking the staged product row to the Oracle Advanced Pricing list definition that governs the offer.
  • PRODUCT_ID — the product or item identifier; a documented foreign key to FND_DM_PRODUCTS, and the principal business-key candidate for reconciling staged rows against the source product master.
  • SECURITY_GROUP_ID — a documented foreign key to FND_SECURITY_GROUPS, controlling multi-tenant visibility and data access segregation.
  • CREATION_DATE, CREATED_BY — standard WHO columns recording when and by whom the staged row was inserted during the refresh.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns tracking the most recent modification and the login under which it occurred.

No unique index other than the primary key is documented, so PRODUCT_ID combined with QP_LIST_HEADER_ID represents the natural business-key candidate for de-duplication logic in the staging load.

Common Use Cases and Queries

Typical usage centres on monitoring and validating the full-refresh concurrent program. Administrators count staged rows before and after the refresh to confirm completeness:

  • Row-count reconciliation: SELECT COUNT(*) FROM ozf.ozf_offer_products_temp;
  • Joining staged products to the product master for name and description enrichment: SELECT t.offer_product_id, t.product_id, p.product_name FROM ozf.ozf_offer_products_temp t, fnd_dm_products p WHERE t.product_id = p.product_id;
  • Detecting orphaned or stale staging data by comparing CREATION_DATE against the expected refresh window.
  • Security-scoped reporting by filtering on SECURITY_GROUP_ID for a given operating unit or group.

Because the table is temporary by design, it should not be used as a permanent reporting source; production reporting belongs against the base offer-products tables, with this object consulted only to validate refresh behaviour.

Related Objects

  • FND_DM_PRODUCTS — referenced via OZF_OFFER_PRODUCTS_TEMP.PRODUCT_ID; supplies product master attributes.
  • FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID; governs access control.
  • QP_LIST_HEADERS — implied parent of QP_LIST_HEADER_ID, providing the price list definition context.
  • OZF_OFFER_PRODUCTS — the permanent counterpart table into which staged rows are typically merged or compared.
  • OZF_OFFERS — the offer header entity whose active records drive population of this staging table.
  • The full-refresh concurrent program — the sole documented writer of this object, invoked from Trade Management.

Practitioners should treat OZF_OFFER_PRODUCTS_TEMP as a refresh-cycle artefact and always reconcile against OZF_OFFER_PRODUCTS before drawing conclusions from its contents.