Results for “iby_transmit_protocols_tl”

49 results




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

Overview

IBY.IBY_TRANSMIT_PROTOCOLS_TL is the translation table for Oracle Payments (IBY) transmit protocols in Oracle E-Business Suite 12.1.1 and 12.2.2. A transmit protocol defines the delivery mechanism used when payment instructions, payment files, or remittance advice documents are dispatched to a payment system or financial institution — for example FTP-based transmission, electronic data interchange, or vendor-specific secure channels. The base (non-translated) definition is held in IBY_TRANSMIT_PROTOCOLS_B, while this table stores the language-dependent descriptive attributes, principally the user-facing protocol name per installed language.

In an ETRM-style Data Vault model, the metadata classifies this object as satellite-leaning. That is a modeling suggestion: the table behaves like a descriptive satellite attached to the TRANSMIT_PROTOCOL_CODE business key, carrying attributes that vary by language context rather than representing an independent hub of business entities. Treating it as a satellite of the base transmit-protocol hub is the most natural interpretation of its foreign key relationship.

Key Information Stored

The table contains eleven documented columns. The most significant are listed below.

  • TRANSMIT_PROTOCOL_CODE — the business key inherited from the base table; together with language it identifies the translated row.
  • LANGUAGE — the language code for which the translated description applies.
  • SOURCE_LANG — the language from which the current translation was derived, used in the standard EBS multilingual framework.
  • TRANSMIT_PROTOCOL_NAME — the translated, user-visible name of the transmit protocol; this is the primary payload attribute of the table.
  • CREATED_BY, CREATION_DATE — standard audit columns recording row creation.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns recording the most recent modification and session context.
  • OBJECT_VERSION_NUMBER — optimistic locking column used by the EBS framework to detect concurrent updates.
  • ZD_EDITION_NAME — editioning support column associated with the E-Business Suite online patching / editioning framework in Release 12.2.x.

There is no separate surrogate primary key column exposed beyond the unique index IBY_TRANSMIT_PROTOCOLS_TL_U1, which covers LANGUAGE, TRANSMIT_PROTOCOL_CODE, and ZD_EDITION_NAME. This composite unique index is the documented business-key candidate and also serves as the effective primary key for the translated row set.

Common Use Cases and Queries

Typical usage centers on joining the base table to its translation to retrieve a language-appropriate protocol name for reports, setup pages, and payment configuration inquiries. A representative query pattern is:

  • Join IBY_TRANSMIT_PROTOCOLS_B to IBY_TRANSMIT_PROTOCOLS_TL on TRANSMIT_PROTOCOL_CODE, filtering LANGUAGE to the desired locale such as 'US'.
  • Filter by ZD_EDITION_NAME to select the correct edition row in a 12.2.x multi-edition environment, typically excluding the internal seed edition where patch history is retained.
  • Reporting use cases include listing available transmit protocols for a given operating unit or payment system, validating that a translation exists for each installed language, and auditing custom or seeded protocol descriptions.

Because the table is small and largely static, queries are inexpensive and typically executed as simple indexed lookups on the composite key.

Related Objects

The most significant related object is the base table referenced through the documented foreign key.

  • IBY_TRANSMIT_PROTOCOLS_B — joined via IBY_TRANSMIT_PROTOCOLS_TL.TRANSMIT_PROTOCOL_CODE = IBY_TRANSMIT_PROTOCOLS_B.TRANSMIT_PROTOCOL_CODE; holds the language-independent protocol definition.
  • Payments setup and configuration views and pages that present transmit protocol options to users, which resolve the display name from this translation table.
  • Payment system and payment process profile configuration objects that reference transmit protocols when determining how payment files are delivered.
  • Public IBY APIs and concurrent programs that query protocol definitions during file transmission and payment instruction dispatch.

In practice, IBY_TRANSMIT_PROTOCOLS_TL should always be accessed in conjunction with its base table, since the translation alone conveys no business meaning without the underlying protocol definition.