Results for “ap_check_transmissions”

6 results




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

Overview

AP_CHECK_TRANSMISSIONS is a Payables (AP) module table in Oracle E-Business Suite 12.1.1 and 12.2.2. Per the ETRM metadata, its documented purpose is to hold temporary payment information used for posting to the General Ledger. In practice, this table functions as a staging area during the payment accounting and GL transfer process. During the Create Accounting and Transfer to General Ledger programs, payment records (primarily check and electronic payment distributions) are accumulated here and subsequently consumed to generate journal entries into GL_INTERFACE or to populate GL_JE_BATCHES and GL_JE_HEADERS. Because the data is transient, the ETRM entry explicitly notes that the table is Not implemented in this database — meaning it may be absent, empty, or populated only intermittently depending on the environment and patching level.

The heuristic Data Vault classification derived from the foreign key structure is link. This is a modeling suggestion: the table behaves as an associative link resolving relationships between a Payables-side payment event (implied by the check/payment context) and General Ledger accounting entities — specifically journal batches, journal headers, sets of books, and currencies. It captures the intersection rather than describing a single business entity in isolation.

Key Information Stored

The documented foreign key columns define the principal data content and join semantics of the table:

  • JE_BATCH_ID — References GL_JE_BATCHES; the journal batch to which the transmitted payment accounting is assigned.
  • JE_HEADER_ID — References GL_JE_HEADERS; the specific journal header for the payment accounting line set.
  • SET_OF_BOOKS_ID — References GL_SETS_OF_BOOKS; identifies the ledger (set of books) targeted by the posting process.
  • CURRENCY_CODE — References FND_CURRENCIES; the currency of the amounts being transmitted for posting.

The four FK columns form the meaningful business content: they tie a payment to its GL destination, ledger, and currency. The ETRM metadata does not document a surrogate primary key or unique index; the underlying unique identifier (if present in the physical table) would be an internal transmission identifier. Practitioners should treat JE_BATCH_ID / JE_HEADER_ID / SET_OF_BOOKS_ID as the business-key candidates, since they collectively disambiguate a posting occurrence. Absent full column documentation, administrators should inspect USER_TAB_COLUMNS to confirm supplementary amount and date columns before writing queries.

Common Use Cases and Queries

Because the table is temporary, its primary uses are reconciliation and troubleshooting during and immediately after the payables accounting cycle:

  • Verifying that payment records were staged correctly before GL transfer.
  • Diagnosing stuck or unposted payments by locating rows with a JE_BATCH_ID but no corresponding accounted journal.
  • Reconciling Payables to GL by tracing payment transmissions to their journal batch and header.

A typical diagnostic query joins the transmission staging rows to their GL targets:

SELECT act.je_batch_id, act.je_header_id, act.set_of_books_id, act.currency_code
FROM ap_check_transmissions act
WHERE act.set_of_books_id = :ledger_id;

For auditing, joining to GL_JE_HEADERS confirms whether the transmitted header actually posted:

SELECT act.je_header_id, gjh.name, gjh.status
FROM ap_check_transmissions act, gl_je_headers gjh
WHERE act.je_header_id = gjh.je_header_id;

Related Objects

The ETRM foreign key metadata identifies the objects this table depends on:

  • GL_JE_BATCHES — joined via AP_CHECK_TRANSMISSIONS.JE_BATCH_ID.
  • GL_JE_HEADERS — joined via AP_CHECK_TRANSMISSIONS.JE_HEADER_ID.
  • GL_SETS_OF_BOOKS — joined via AP_CHECK_TRANSMISSIONS.SET_OF_BOOKS_ID.
  • FND_CURRENCIES — joined via AP_CHECK_TRANSMISSIONS.CURRENCY_CODE.

Functionally, the table interacts with the Payables payment workbench objects (AP_CHECKS, AP_INVOICE_PAYMENTS) and the GL posting programs. Consult the Payables and General Ledger transfer programs to understand the lifecycle that populates and purges this staging table. Given its transient nature, no reliable long-term reporting should depend on its contents.