Search Results ozf_request_lines_all




Overview
Explore in AI Chat

Overview

The OZF_REQUEST_LINES_ALL table is a core data object within the Oracle E-Business Suite (EBS) Trade Management module (OZF). It functions as the detailed transactional repository for request lines associated with soft funds and special pricing. In the context of Oracle Trade Management, these requests are fundamental for managing promotional funds, discounts, and custom pricing agreements between a business and its channel partners or customers. The table stores the individual line-level details of such requests, with each record linked to a parent header in the OZF_REQUEST_HEADERS_ALL_B table. Its role is critical for capturing the granular financial and product-specific data required for the approval, execution, and accounting of trade promotions and pricing agreements.

Key Information Stored

The table's primary purpose is to store line-level attributes for funding and pricing requests. The most critical column is the primary key, REQUEST_LINE_ID, which uniquely identifies each request line. The foreign key column, REQUEST_HEADER_ID, is essential as it links each line to its corresponding parent request header, establishing the document structure. While the provided metadata does not list all columns, typical data stored in such a table includes product identifiers, requested discount or funding amounts, quantities, unit of measure, accrual account codes, status, and line-level approval information. This structure allows multiple products or conditions to be managed under a single promotional request header.

Common Use Cases and Queries

This table is central to reporting and operational processes within Trade Management. Common use cases include generating detailed line-item reports for a specific promotional fund request, auditing approved discounts by product, and reconciling accrual amounts. A fundamental query pattern involves joining to the header table to retrieve a complete request document. For example, to list all lines for a specific request header, one would use:

  • SELECT line.* FROM ozf_request_lines_all line WHERE line.request_header_id = <HEADER_ID>;

For analytical reporting, a join to product and customer tables is typical to aggregate requested funds by product category or partner. Data from this table also feeds into downstream financial processes for accrual journal generation and settlement calculations.

Related Objects

The OZF_REQUEST_LINES_ALL table has documented relationships with several key objects, primarily through foreign key constraints. The most critical relationship is with the request header table, as defined in the provided metadata.

  • OZF_REQUEST_HEADERS_ALL_B: This is the primary parent table. Each record in OZF_REQUEST_LINES_ALL must reference a valid header via the REQUEST_HEADER_ID column. This relationship defines the core document structure.
  • OZF_REQUEST_LINES_ALL_PK: This is the primary key constraint on the REQUEST_LINE_ID column, ensuring each line is uniquely identifiable.

In a full implementation, this table would also relate to product tables (like MTL_SYSTEM_ITEMS_B), customer tables (like HZ_CUST_ACCOUNTS), and likely other OZF transactional tables such as OZF_CLAIM_LINES_ALL for settlement, though these specific relationships are not detailed in the provided excerpt.