Results for “iby_transmit_configs_b”

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

Overview

IBY_TRANSMIT_CONFIGS_B is a foundational configuration table within the Oracle Payments (IBY) module of Oracle E-Business Suite, present in both release 12.1.1 and 12.2.2. It stores the transmission configuration definitions that govern how payment instructions, payment files, and related documents are dispatched from Oracle EBS to external payment systems, banks, and clearing networks. Each row defines an outbound transmission path by binding a transmission protocol to a specific configuration identity and, optionally, to another transmission configuration through a tunneling relationship.

The table sits at the center of the payment transmission framework, working in conjunction with protocol definitions and format mappings to determine how a payment process request is delivered. Because configuration records are versioned and tagged with standard WHO audit columns, the table supports controlled change management across the payment lifecycle.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign key structure is satellite-leaning. This suggests that IBY_TRANSMIT_CONFIGS_B is best modeled as a descriptive satellite attached to a transmission protocol or configuration hub, rather than as an independent hub or a transactional link. The recursive self-reference reinforces this interpretation: tunneling relationships capture configuration-dependent descriptor detail rather than new business entities.

Key Information Stored

The table contains ten documented columns. The most significant are summarized below.

• TRANSMIT_CONFIGURATION_ID — The surrogate primary key, enforced by IBY_TRANSMIT_CONFIGS_B_PK and additionally protected by the unique index IBY_TRANSMIT_CONFIGS_B_CID_U1. This is the identifier referenced throughout the payment transmission subsystem.
• TRANSMIT_PROTOCOL_CODE — The foreign key to IBY_TRANSMIT_PROTOCOLS_B, identifying which transmission protocol (for example, FTP, WebSphere MQ, or a payment gateway adapter) the configuration uses.
• TUNNELING_TRANS_CONFIG_ID — A self-referencing foreign key to IBY_TRANSMIT_CONFIGS_B that links one configuration to another when a tunneling transmission path is required.
• INACTIVE_DATE — The date on which the configuration becomes inactive, enabling soft retirement of obsolete transmission paths without physical deletion.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns recording creation and modification history for each configuration record.
• OBJECT_VERSION_NUMBER — The optimistic locking column used by the Oracle Application Framework to detect concurrent updates.

Note that TRANSMIT_CONFIGURATION_ID is both the documented primary key and the single documented business-key candidate, making it the canonical join column for downstream consumers.

Common Use Cases and Queries

Typical usage centers on configuration validation, impact analysis, and integration diagnostics. A common reporting pattern joins the configuration to its protocol definition to produce a readable inventory of outbound transmission paths:

• Listing all active configurations for a protocol: select from IBY_TRANSMIT_CONFIGS_B where TRANSMIT_PROTOCOL_CODE equals a given protocol and INACTIVE_DATE is null.
• Identifying tunneling chains by following TUNNELING_TRANS_CONFIG_ID recursively, useful when diagnosing nested transmission routes.
• Auditing configuration changes by filtering on LAST_UPDATE_DATE and LAST_UPDATED_BY to support SOX and internal control reviews.
• Feeding downstream payment extracts that resolve the correct protocol and tunneling behavior for each payment process request.

Related Objects

The following objects are most directly coupled to IBY_TRANSMIT_CONFIGS_B through documented relationships:

• IBY_TRANSMIT_PROTOCOLS_B — joined on TRANSMIT_PROTOCOL_CODE; supplies protocol-level attributes and is the principal parent reference.
• IBY_TRANSMIT_CONFIGS_B (self) — joined on TUNNELING_TRANS_CONFIG_ID; resolves tunneling relationships between configurations.
• IBY_TRANSMIT_CONFIGS_TL — the translated companion table holding language-specific descriptive text for each configuration.
• IBY_PAYMENT_SYSTEMS and related payment system configuration tables — consume transmission configuration identifiers when defining outbound payment channels.
• IBY_FD_PAYMENT_INSTRUCTIONS and payment instruction consumers — depend on the resolved configuration to determine transmission behavior at runtime.
• IBY_TRANSMIT_CONFIGS_B_PK and IBY_TRANSMIT_CONFIGS_B_CID_U1 — the enforcing constraints and unique index that guarantee configuration identity integrity.