Search Results ozf_sd_request_hdrs_all_b_pk




Overview

OZF_SD_REQUEST_HEADERS_ALL_B is the base transaction table in the Oracle Trade Management (OZF) module that stores ship-and-debit request header information. Ship-and-debit requests are the mechanism by which suppliers and distributors reconcile accrued trade promotions: a partner submits a claim for a promotional allowance, the claim is tracked through its lifecycle, and it is ultimately settled against a budget or accrued liability. This table captures the header-level identity, classification, financial budget, workflow dates, and supplier/customer context for every such request across all operating units, as indicated by the presence of ORG_ID and the _ALL suffix.

The metadata classifies this object as hub-leaning under a heuristic Data Vault analysis. In modeling terms, it functions primarily as a hub: it holds the durable business key (REQUEST_HEADER_ID) around which descriptive and transactional attributes are organized, with foreign key links to FND_SECURITY_GROUPS and HZ_CUST_ACCOUNTS acting as supporting dimensions. A translator table (OZF_SD_REQUEST_HEADERS_ALL_TL) supplies the translated/display attributes.

Key Information Stored

The table contains 69 documented columns. The most significant grouping is as follows:

Standard EBS audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, OBJECT_VERSION_NUMBER) and the ATTRIBUTE1–15 flexfield set are also present.

Common Use Cases and Queries

Typical reporting needs include claim aging, budget-versus-approved variance, and supplier response cycle-time analysis. A common pattern joins the header to the translator table for display text:

SELECT h.request_number, t.request_description,
       h.requested_budget_amount, h.approved_budget_amount
  FROM ozf.ozf_sd_request_headers_all_b h,
       ozf.ozf_sd_request_headers_all_tl t
 WHERE h.request_header_id = t.request_header_id;

Other frequently used patterns include filtering on REQUEST_OUTCOME to identify declined claims, aggregating approved amounts by OFFER_ID to compare against promotion budgets, and joining to HZ_CUST_ACCOUNTS to report claims by trading partner. Because the table is an _ALL table, queries should generally constrain by ORG_ID for a specific operating unit unless a cross-org report is intended.

Related Objects

  • OZF_SD_REQUEST_HEADERS_ALL_TL — the translation table, joined on REQUEST_HEADER_ID; supplies language-dependent description fields.
  • HZ_CUST_ACCOUNTS — referenced via CUST_ACCOUNT_ID; provides the customer identity for each claim.
  • FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID; enforces data security partitioning.
  • OZF_SD_REQUEST_LINES_ALL — likely child table holding line-level detail for each header (standard Trade Management pattern; verify against release).
  • OZF_OFFERS_ALL — links via OFFER_ID to the originating promotion definition.
  • OZF_SD_REQUEST_HDRS_ALL_B_PK — the primary key constraint on REQUEST_HEADER_ID, the anchor for all joins.