Search Results ozf_request_headers_all_b




Overview
Explore in AI Chat

Overview

The OZF_REQUEST_HEADERS_ALL_B table is a core transactional entity within Oracle E-Business Suite Release 12.1.1 and 12.2.2, specifically for the Trade Management (OZF) module. It serves as the master header table for storing information related to requests for soft funds and special pricing. These requests are fundamental to managing trade promotions, funds, and pricing agreements between an organization and its channel partners. The table's "ALL" suffix and "B" designation indicate it is the base transactional table that stores multi-organization data, forming the central point for a request's lifecycle from initiation through approval and subsequent financial settlement.

Key Information Stored

While the provided metadata does not list all columns, the primary and foreign key relationships reveal critical data points. The central identifier is the REQUEST_HEADER_ID, which is the primary key for the table. The OFFER_ID column links the request to a specific trade promotion or offer defined in the OZF_OFFERS table. The LINKED_REQUEST_HEADER_ID column enables hierarchical relationships between different request headers, allowing for complex request structures. Other essential columns typically found in such a header table would include attributes for the request's status, type (e.g., soft fund, special pricing), currency, total amount, date ranges, associated customer or internal sales organization, and audit information such as CREATED_BY and CREATION_DATE.

Common Use Cases and Queries

This table is central to reporting and process flows within Trade Management. Common use cases include generating summaries of all pending fund requests, tracking the history of pricing agreements for a specific customer, and auditing the volume and value of requests by period or sales organization. A typical reporting query would join this table to its descriptive TL (translation) table and related lines table to retrieve a comprehensive request view. For example, to list active special pricing requests, a query might filter on request type and status while joining to OZF_REQUEST_LINES_ALL for detail. Integration with the approval engine (via OZF_APPROVAL_ACCESS) and the claims process (via OZF_CLAIMS_ALL) also means this table is frequently accessed during automated workflow and settlement procedures.

Related Objects

The table maintains integral relationships with several other key Trade Management objects, as documented by its foreign keys:

  • OZF_OFFERS: Joined via OFFER_ID, linking the request to its originating trade promotion.
  • OZF_REQUEST_HEADERS_ALL_B (Self-Referential): Joined via LINKED_REQUEST_HEADER_ID, establishing links between related requests.
  • OZF_APPROVAL_ACCESS: Joined where OZF_APPROVAL_ACCESS.OBJECT_ID = REQUEST_HEADER_ID, connecting the request to the approval workflow.
  • OZF_CLAIMS_ALL: Joined where OZF_CLAIMS_ALL.SOURCE_OBJECT_ID = REQUEST_HEADER_ID, linking the request to subsequent claims for payment.
  • OZF_REQUEST_HEADERS_ALL_TL: Joined via REQUEST_HEADER_ID, providing translated descriptive information for the header.
  • OZF_REQUEST_LINES_ALL: Joined via REQUEST_HEADER_ID, providing the detailed line items of the request.