Results for “transmission_code”

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

Overview

AP_TRANSMISSION_CODES_V is a reporting view owned by the APPS schema within the Oracle E-Business Suite Payables (AP) module. As documented in the ETRM metadata for releases 12.1.1 and 12.2.2, its purpose is to display transmission codes alongside the names of the associated banks and their branches. The view carries a VALID status and is defined over a small, purpose-built join that consolidates bank master reference data with Payables transmission setup data.

Transmission codes in Oracle Payables identify the bank and bank branch to which payment instructions are routed when electronic payment formats are generated. Because the raw setup tables store this relationship as internal numeric identifiers (party and branch IDs), the view exists to translate those surrogate keys into human-readable bank and branch names. This makes it particularly useful for reporting, reconciliation, and integration scenarios where a readable description of the payment routing destination is required, rather than an internal ID. The view contains no application logic beyond the join itself; it is a pure presentation layer over persisted configuration data.

Underlying Base Objects

The documented metadata identifies two referenced base objects: AP_TRANSMISSIONS_SETUP (accessed through a synonym) and CE_BANK_BRANCHES_V (a view). AP_TRANSMISSIONS_SETUP is the Payables setup object that stores transmission code definitions and the associated bank branch identifier. CE_BANK_BRANCHES_V is a Cash Management (CE) view that resolves bank and branch parties into bank name and branch name attributes.

Per the documented view text, the relationship is established by joining AP_TRANSMISSIONS_SETUP.BANK_BRANCH_ID to CE_BANK_BRANCHES_V.BRANCH_PARTY_ID. The result set is ordered by bank name and then bank branch name. This join design means the transmission code acts as the driving key, with bank and branch descriptions supplied by the Cash Management layer. Because CE_BANK_BRANCHES_V is itself a view, any change in bank or branch configuration will be reflected dynamically in AP_TRANSMISSION_CODES_V without additional maintenance.

Key Columns

• TRANSMISSION_CODE — The Payables transmission code, sourced from AP_TRANSMISSIONS_SETUP. This is the identifier used when configuring payment formats and payment routing.
• BANK_NAME — The name of the bank, sourced from CE_BANK_BRANCHES_V. Provides the readable institution name associated with the transmission code.
• BANK_BRANCH_NAME — The name of the bank branch, sourced from CE_BANK_BRANCHES_V. Identifies the specific branch tied to the transmission code.

Common Use Cases and Queries

The view is typically used to validate payment transmission setup, to produce reports listing which banks and branches are configured for electronic payments, and to enrich payment or remittance extracts with readable routing descriptions. The following query lists all configured transmission codes:

SELECT transmission_code, bank_name, bank_branch_name
FROM   apps.ap_transmission_codes_v
ORDER BY bank_name, bank_branch_name;

A targeted lookup by code is equally common:

SELECT transmission_code, bank_name, bank_branch_name
FROM   apps.ap_transmission_codes_v
WHERE  transmission_code = :p_transmission_code;

Because the view exposes only three columns and no filterable identifiers beyond the transmission code, most integrations either consume the full result set or join it back to transmission setup data by TRANSMISSION_CODE. It is well suited to LOV definitions, concurrent program report sources, and interface enrichment where bank and branch names must accompany payment routing information.