Results for “transmission_program”

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

Overview

AP_TRANSMISSIONS_SETUP is a table in the Oracle Payables (AP) schema that stores configuration information for payment and bank transmission processes. Historically, it held the connection parameters, credentials, file-naming conventions, and directory mappings required for transmitting payment files, confirmations, statements, and exception reports between Oracle EBS and banking partners. The ETRM documentation explicitly designates this object as "No Longer Used," indicating that its functional role has been superseded by later transmission technologies and payment formats. It remains present and VALID in the schema for backward compatibility and is preserved primarily because other objects within the E-Business Suite continue to reference it.

The documented schema exposes 56 columns and a single-column primary key, AP_TRANSMISSION_SETUP_PK, defined on TRANSMISSION_ID, with a corresponding unique index AP_TRANSMISSIONS_SETUP_U1 on the same column. A heuristic Data Vault classification derived from the foreign-key structure suggests a satellite-leaning model, since the table appears to hold descriptive configuration attributes attached to a transmission entity rather than serving as a pure transactional hub or associative link.

Key Information Stored

The table's most significant columns fall into three groups: identity, connectivity, and file-handling configuration.

• TRANSMISSION_ID — The surrogate primary key and unique business-key candidate, identifying each transmission setup record.
• TRANSMISSION_CODE — A descriptive code used to identify the transmission configuration.
• BANK_BRANCH_ID — Foreign key to AP_BANK_BRANCHES, associating the setup with a specific bank branch.
• TRANSMISSION_PROGRAM — Identifies the program or protocol invoked to perform the transmission.
• USERNAME / PASSWORD — Credentials used for outbound bank connectivity.
• PROTOCOL / PROTOCOL_ADDRESS — The communication protocol and its target address.
• TRANSMISSION_EMAIL, CONFIRMATION_EMAIL, STATEMENT_EMAIL, EXCEPTION_EMAIL — Email destinations for the corresponding file types.
• LOCAL_*_DIRECTORY and BANK_*_DIRECTORY — Paired source and destination directories for payments, confirmations, statements, and exceptions.
• PAY_FILE_EXT/PREFIX/SUFFIX and parallel CONF/STMT/EXCEPTION file attributes — Naming conventions that determine how each output file is constructed.
• INTRA_* and XTR_* columns — Variant configurations for intra-day statement handling and treasury-related transmission paths.

The audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) follow standard EBS conventions.

Common Use Cases and Queries

Because the table is documented as no longer used, its primary practical value is diagnostic and historical: confirming legacy configuration before migrations, auditing which bank branch was associated with a given transmission identifier, or retrieving file-naming conventions referenced by older data. A representative query joins the table to its parent bank branch:

SELECT ts.transmission_id, ts.transmission_code, ts.bank_branch_id,
       br.branch_name, ts.pay_file_prefix, ts.pay_file_ext
FROM  ap.ap_transmissions_setup ts,
       ap.ap_bank_branches br
WHERE  ts.bank_branch_id = br.branch_party_id;

Reporting use cases include identifying orphaned transmission configurations, reconciling the four dependent tables that still carry a TRANSMISSION_ID reference, and documenting legacy interface behavior prior to upgrade from 12.1.1 to 12.2.2.

Related Objects

The following objects are documented as referencing or being referenced by AP_TRANSMISSIONS_SETUP:

• AP_BANK_BRANCHES — Referenced through AP_TRANSMISSIONS_SETUP.BANK_BRANCH_ID.
• AR_TRANSMISSIONS_ALL — References TRANSMISSION_ID.
• AR_BATCHES_ALL — References TRANSMISSION_ID.
• AR_PAYMENTS_INTERFACE_ALL — References TRANSMISSION_ID.
• FV_LOCKBOX_IPA_TEMP — References TRANSMISSION_ID.

These dependencies explain the table's retention in the schema even though it is functionally obsolete: dropping it would break foreign-key integrity in the Receivables and Treasury-related objects that still point to it.