Search Results ae_line_id

Overview

The OZF_AE_LINES_ALL table is a core data object within the Oracle E-Business Suite (EBS) Trade Management module (OZF). It functions as the detailed line-level repository for accounting entries, specifically storing individual accounting lines that are grouped under a parent accounting header. This table is integral to the financial accounting and settlement processes for trade promotions and funds within the Trade Management system. As a multi-org table (indicated by the "_ALL" suffix), it stores data for all operating units, with access typically controlled by a security profile. Its primary role is to hold the detailed debit and credit entries that constitute the complete accounting for a trade transaction, ensuring accurate financial posting and reconciliation.

Key Information Stored

The table's structure is designed to capture essential accounting line details. The most critical column is the AE_LINE_ID, which serves as the unique primary key identifier for each accounting line record. Another fundamental column is AE_HEADER_ID, a foreign key that links each line to its parent header record in the OZF_AE_HEADERS_ALL table, establishing the document structure. While the provided metadata does not list all columns, typical accounting line tables in EBS store data such as the accounting date (GL_DATE), code combination ID (CODE_COMBINATION_ID) for the general ledger account, entered debit (ENTERED_DR) and credit (ENTERED_CR) amounts, accounted debit (ACCOUNTED_DR) and credit (ACCOUNTED_CR) amounts, and a line description. These elements collectively define the financial impact of each line.

Common Use Cases and Queries

This table is central to financial reporting, audit trails, and reconciliation activities for trade funds. A common use case involves tracing the complete accounting entries for a specific trade promotion transaction or settlement batch. Analysts and accountants frequently query this table to verify that the sum of debits equals the sum of credits for a given header or to analyze account distributions. A typical query pattern retrieves all lines for a specific accounting header, often joining to the GL code combinations table for account segment details:

• SELECT ae_line_id, code_combination_id, entered_dr, entered_cr, line_description FROM ozf_ae_lines_all WHERE ae_header_id = &header_id ORDER BY ae_line_id;

Another critical reporting use case is generating a detailed audit report for a period, joining to OZF_AE_HEADERS_ALL to include header-level information like the document number and creation date.

Related Objects

The OZF_AE_LINES_ALL table exists within a defined hierarchy of related objects, primarily linked through foreign key relationships. As per the documented metadata, its most significant relationship is with the parent header table:

• OZF_AE_HEADERS_ALL: This is the primary foreign key relationship. Each record in OZF_AE_LINES_ALL references a single parent header via the AE_HEADER_ID column. The foreign key constraint ensures referential integrity, meaning an accounting line cannot exist without a valid header.

While not listed in the provided excerpt, this table would also be referenced by various Trade Management reports, interfaces, and potentially by the public Oracle APIs used for programmatic access and data extraction. It is also commonly joined to GL-related tables like GL_CODE_COMBINATIONS to resolve account flexfield values for reporting purposes.