Search Results ap_invoice_transmissions

Overview

The AP_INVOICE_TRANSMISSIONS table is a temporary data structure within Oracle E-Business Suite Payables (AP). Its primary role is to act as a staging area for invoice-related accounting information during the critical process of posting transactions to the General Ledger (GL). This table facilitates the transfer and validation of summarized invoice data—such as liability and expense distributions—before the creation of final journal entries in GL. The metadata explicitly notes it is "Not implemented in this database," indicating it is a legacy or transient table that may not be directly populated or accessible in a standard EBS 12.1.1 or 12.2.2 instance, but its defined relationships are essential for understanding the GL posting architecture.

Key Information Stored

Based on the documented foreign key relationships, the table stores key identifiers that link Payables transactions to General Ledger entities. Important columns include JE_BATCH_ID and JE_HEADER_ID, which reference the journal entry batch and header in GL that the invoice data will ultimately post to. The SET_OF_BOOKS_ID column defines the accounting context, while CURRENCY_CODE holds the transaction currency. A critical accounting column is ACCTS_PAY_CODE_COMBINATION_ID, which stores the code combination identifier for the accounts payable liability account. The table likely also holds summarized amounts and invoice identifiers to be transmitted.

Common Use Cases and Queries

Direct interaction with this table is uncommon for functional users or reports, as it is a temporary working table. Its primary use case is during the "Transfer to General Ledger" process run from Payables. Technically, one might query it to diagnose stalled or failed GL transfer processes, though this would typically be managed by standard concurrent program diagnostics. A sample diagnostic query, leveraging its foreign keys, might join to GL tables to check for untransmitted data:

• SELECT ait.* FROM ap_invoice_transmissions ait WHERE NOT EXISTS (SELECT 1 FROM gl_je_batches gjb WHERE gjb.je_batch_id = ait.je_batch_id);

This would identify records that appear to be staged but for which a corresponding GL batch does not exist.

Related Objects

The foreign keys define this table's core dependencies within the financials schema. It is directly related to key General Ledger tables: GL_JE_BATCHES, GL_JE_HEADERS, and GL_SETS_OF_BOOKS. It also references FND_CURRENCIES for currency validation and GL_CODE_COMBINATIONS for the liability account. In Payables, this table is logically associated with the AP_INVOICES and AP_INVOICE_DISTRIBUTIONS tables, from which its source data is derived during the posting process. The creation and management of records in this table are driven by internal Payables posting programs and APIs.