Results for “iby_pmt_sys_transmissions”

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

Overview

IBY_PMT_SYS_TRANSMISSIONS is a configuration table in the Oracle Payments (IBY) module of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It defines the permissible combinations of a payment system transmission protocol and a payment system (BEP), effectively controlling which transmission protocols may be used to deliver payment instructions to a given payment system. Each row authorizes one protocol-to-payment-system relationship.

Under the heuristic Data Vault classification derived from its foreign-key structure, this table is modeled as a link table. Its composite primary key, IBY_PMT_SYS_TRANSMISSIONS_PK, consists of the two foreign-key columns TRANSMIT_PROTOCOL_CODE and BEPID, making it a classic association (junction) entity that resolves a many-to-many relationship between transmission protocols and payment systems.

Key Information Stored

The documented physical schema for 12.2.2 identifies nine columns. The most significant are:

• TRANSMIT_PROTOCOL_CODE — Part of the composite primary key; foreign key to IBY_TRANSMIT_PROTOCOLS_B, identifying the transmission protocol (for example, a delivery mechanism such as file transfer, FTP, or other supported protocol).
• BEPID — Part of the composite primary key; foreign key to IBY_BEPINFO, identifying the payment system (BEP) to which the protocol applies.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle Payments framework to detect concurrent updates.
• ZD_EDITION_NAME — Editioning column supporting Oracle EBS online patching (Edition-Based Redefinition) in 12.2.x; appears in the unique index IBY_PMT_SYS_TRANSMISSIONS_U1.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns recording insert and update metadata.

The surrogate primary key is IBY_PMT_SYS_TRANSMISSIONS_PK (TRANSMIT_PROTOCOL_CODE, BEPID). Business-key uniqueness is additionally enforced by IBY_PMT_SYS_TRANSMISSIONS_U1 (BEPID, TRANSMIT_PROTOCOL_CODE, ZD_EDITION_NAME), which extends the natural key with the editioning column under EBR.

Common Use Cases and Queries

Typical usage centers on determining which transmission protocols are enabled for a given payment system, and on validating configuration during implementation or troubleshooting of payment instruction delivery.

• Listing all protocols configured for a specific payment system:

  SELECT t.TRANSMIT_PROTOCOL_CODE, t.BEPID
  FROM   IBY.IBY_PMT_SYS_TRANSMISSIONS t
  WHERE  t.BEPID = :bepid;

• Joining to the protocol definition table to retrieve protocol details:

  SELECT s.BEPID, p.TRANSMIT_PROTOCOL_CODE, p.PROTOCOL_TYPE
  FROM   IBY.IBY_PMT_SYS_TRANSMISSIONS s,
         IBY.IBY_TRANSMIT_PROTOCOLS_B p
  WHERE  s.TRANSMIT_PROTOCOL_CODE = p.TRANSMIT_PROTOCOL_CODE;

• Validating that a payment system has at least one transmission protocol defined before enabling it.
• Reporting on payment system configuration, often combined with IBY_BEPINFO to show payment system names alongside their authorized protocols.

Related Objects

The following objects are most significant in relation to this table, based on the documented foreign-key relationships:

• IBY_TRANSMIT_PROTOCOLS_B — Referenced by TRANSMIT_PROTOCOL_CODE; holds the transmission protocol definitions.
• IBY_BEPINFO — Referenced by BEPID; holds payment system (BEP) information.
• IBY_PMT_SYS_TRANSMISSIONS_PK — Primary key constraint on (TRANSMIT_PROTOCOL_CODE, BEPID).
• IBY_PMT_SYS_TRANSMISSIONS_U1 — Unique index on (BEPID, TRANSMIT_PROTOCOL_CODE, ZD_EDITION_NAME).
• Oracle Payments configuration and setup flows that consume these relationships when creating or enabling payment systems.