Results for “transmit_protocol_code”

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

Overview

IBY_TRANSMIT_PARAMETERS_TL is a translation (TL) table within the IBY — Payments module of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. It stores the language-specific, user-facing descriptions for the transmit parameters defined by payment transmission protocols. A transmission protocol (for example, a bank file delivery mechanism such as FTP or a payment gateway) can require one or more configurable parameters, and this table holds the translatable name of each such parameter so that the configuration UI and reports can present parameter labels in the session language.

In Data Vault modeling terms, the mined foreign-key structure classifies this object as satellite-leaning. This is a suggestion only: the table carries descriptive, language-dependent attributes attached to a business key rather than serving as a hub or a pure link. In EBS terms, it functions as the translated child of the base transmit-parameter definition, and the documented unique index (IBY_TRANSMIT_PARAMETERS_TL_U1) confirms that it is keyed by business attributes rather than by an opaque surrogate alone.

Key Information Stored

The table contains 12 documented columns. The most important are:

• TRANSMIT_PROTOCOL_CODE — identifies the transmission protocol to which the parameter belongs; a key component of the unique index.
• TRANSMIT_PARAMETER_CODE — the internal, language-independent identifier for the transmission parameter; combined with the protocol code it forms the core business key.
• LANGUAGE — the language of the translated row, part of the unique business key.
• SOURCE_LANG — the source language from which the translation was derived, used by the EBS translation framework.
• TRANSMIT_PARAMETER_NAME — the translated, displayable parameter name shown to users.
• ZD_EDITION_NAME — the edition marker used in 12.2.x edition-based redefinition; it participates in the unique index.
• OBJECT_VERSION_NUMBER — optimistic-locking column maintained by the framework.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS WHO columns providing audit lineage.

The documented unique business-key candidate is IBY_TRANSMIT_PARAMETERS_TL_U1, defined on (LANGUAGE, TRANSMIT_PROTOCOL_CODE, TRANSMIT_PARAMETER_CODE, ZD_EDITION_NAME). No separate surrogate single-column primary key is documented in this metadata excerpt; the business key therefore governs uniqueness.

Common Use Cases and Queries

The principal use case is resolving a parameter's display name in a given language for configuration screens, payment-format setup, and operational reporting. A typical query joins the translated name to the protocol and parameter codes:

• List all parameters and their names for a protocol in the current language.
• Audit missing translations by comparing LANGUAGE rows against SOURCE_LANG.
• Feed a report of bank-transmission configuration for reconciliation or SOX documentation.

A representative SQL pattern follows:

SELECT tp.transmit_protocol_code, tp.transmit_parameter_code, tp.transmit_parameter_name
FROM iby_transmit_parameters_tl tp
WHERE tp.language = USERENV('LANG')
AND tp.zd_edition_name = 'SET1'
ORDER BY tp.transmit_parameter_code;

Because the table is date-effective and edition-aware, queries should constrain LANGUAGE and ZD_EDITION_NAME to return a single deterministic name per parameter.

Related Objects

The following objects are significant to working with this table:

• IBY_TRANSMIT_PARAMETERS_B — the base (non-translated) definition table that owns the parameter metadata; join on TRANSMIT_PROTOCOL_CODE and TRANSMIT_PARAMETER_CODE.
• IBY_TRANSMIT_PROTOCOLS_B / _TL — the protocol definitions that this parameter's protocol code references.
• IBY_TRANSMIT_PARAMETERS_TL_U1 — the unique index enforcing the business key (LANGUAGE, TRANSMIT_PROTOCOL_CODE, TRANSMIT_PARAMETER_CODE, ZD_EDITION_NAME).
• IBY_FNDCPT_* configuration tables — payment setup objects that consume transmit parameters when defining payment processing profiles.
• Foreign-key relationships: the documented FK links TRANSMIT_PROTOCOL_CODE and TRANSMIT_PARAMETER_CODE back to the transmit-parameter definition, confirming the satellite relationship to the base entity.