Results for “ap_invoice_transmissions”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AP_INVOICE_TRANSMISSIONS is a Payables (AP) module object documented in the Oracle E-Business Suite eTRM repository for releases 12.1.1 and 12.2.2. Its documented description identifies it as a "temporary table for the invoice information used for posting to the general ledger." This characterization is significant: the table is a transient staging structure populated during the Payables accounting and transfer-to-GL process, not a permanent transactional store. Records are written as invoices are accounted and either purged after the Create Accounting or Transfer Journal Entries to GL programs complete, or retained only briefly within a processing window. It therefore should not be treated as a system of record for invoice accounting lines; the authoritative ledger impact resides in GL_JE_HEADERS and GL_JE_BATCHES.

The ETRM record notes that the object is "Not implemented in this database," indicating that the table is created and maintained dynamically by the Payables accounting engine rather than as a static, always-present repository object. Its column set is aligned with the columns required to construct general ledger journal entries, including the journal batch, header, ledger, currency, and payables account references.

Under the heuristic Data Vault classification mined from the foreign-key structure, AP_INVOICE_TRANSMISSIONS is categorized as a link entity. As a modeling suggestion, this reflects its role as an associative construct connecting invoice accounting activity to general ledger journal artifacts (batches and headers), to the ledger definition, to currency, and to the payables account in the chart of accounts. It is not a hub (it does not own a durable business key with independent identity) nor a satellite (it does not merely describe an existing hub).

Key Information Stored

The documented metadata exposes a focused set of columns, all of which are foreign-key references. The most important are:

• JE_BATCH_ID — foreign key to GL_JE_BATCHES, identifying the journal batch created for the invoice accounting event.
• JE_HEADER_ID — foreign key to GL_JE_HEADERS, identifying the specific journal entry header generated.
• SET_OF_BOOKS_ID — foreign key to GL_SETS_OF_BOOKS, the ledger (set of books) into which the invoice is accounted.
• CURRENCY_CODE — foreign key to FND_CURRENCIES, the currency of the accounting distribution.
• ACCTS_PAY_CODE_COMBINATION_ID — foreign key to GL_CODE_COMBINATIONS, the payables liability account combination used on the invoice.

These five columns constitute the view of the table provided in the ETRM data. Consistent with a link classification, the table does not expose a documented surrogate primary key or a documented unique business key in the metadata; identity is expressed through the composite of the referenced GL and ledger foreign keys. Invoice-level identifiers (such as an invoice ID or invoice number) are implied by the table's purpose but are not enumerated in the provided metadata and should be confirmed against the deployed table definition in each instance.

Common Use Cases and Queries

Typical use cases center on diagnosing invoice-to-GL posting and reconciling Payables accounting output.

• Posting exception diagnosis: Join AP_INVOICE_TRANSMISSIONS to GL_JE_HEADERS on JE_HEADER_ID to review journal lines produced for invoices and identify entries that failed to post or remain unposted in GL.
• Batch reconciliation: Aggregate transmissions by JE_BATCH_ID and SET_OF_BOOKS_ID to compare Payables accounting volume against GL_JE_BATCHES control totals.
• Account analysis: Group by ACCTS_PAY_CODE_COMBINATION_ID to verify that invoice liabilities hit the intended payables account.
• Multi-currency reporting: Filter by CURRENCY_CODE and join FND_CURRENCIES for currency-specific posting analysis.

A representative pattern is: SELECT t.je_header_id, t.set_of_books_id, t.currency_code, t.accts_pay_code_combination_id FROM ap_invoice_transmissions t WHERE t.je_batch_id = :batch_id; Because the table is temporary and may be empty in steady state, query results depend on the timing of the accounting run; analysts should capture data during or immediately after the transfer process.

Related Objects

• GL_JE_BATCHES — joined on JE_BATCH_ID.
• GL_JE_HEADERS — joined on JE_HEADER_ID.
• GL_JE_LINES — the line-level detail for headers created from transmissions.
• GL_SETS_OF_BOOKS — joined on SET_OF_BOOKS_ID.
• GL_CODE_COMBINATIONS — joined on ACCTS_PAY_CODE_COMBINATION_ID.
• FND_CURRENCIES — joined on CURRENCY_CODE.
• AP_INVOICES_ALL and AP_INVOICE_DISTRIBUTIONS_ALL — source invoice and distribution rows whose accounting feeds this table.
• Payables accounting programs such as Create Accounting and Transfer Journal Entries to GL, which populate and subsequently purge the table.