Results for “iby_transmit_protocols_b”

50+ results




Overview
Explore in AI Chat

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

Overview

IBY_TRANSMIT_PROTOCOLS_B is the base (non-translated) table within the Oracle Payments (IBY) module of Oracle E-Business Suite, holding the definitive registry of transmit protocols used when payment instructions and settlement files are moved between Oracle EBS and external payment systems, clearing networks, or financial institutions. A transmit protocol in this context defines an executable transport mechanism — for example a file-based transmission, a host-to-host exchange, or a remote call — and is identified by a transport code that the payment engine resolves at runtime. The table is the code-owning parent for those mechanisms and is referenced extensively by payment system profiles, credit card, debit card, and EFT processing profile tables, and by runtime transmission records.

From a Data Vault modeling perspective, the metadata's FK topology classifies this object as hub-leaning. TRANSMIT_PROTOCOL_CODE serves as the business key of a hub, with the descriptive transport attributes and audit columns behaving as satellite-type payload. This is a modeling suggestion rather than a physical implementation characteristic.

Key Information Stored

The primary key is enforced by the constraint IBY_TRANSMIT_PROTOCOLS_B_PK over TRANSMIT_PROTOCOL_CODE, which is the surrogate, system-generated identifier for each protocol row. A second unique index, IBY_TRANSMIT_PROTOCOLS_B_PC_U1, spans TRANSMIT_PROTOCOL_CODE and ZD_EDITION_NAME, confirming that the protocol code is the business-key candidate and that multiple edition rows may exist for a single code under editioning.

  • TRANSMIT_PROTOCOL_CODE — the system-assigned key and code used throughout IBY to reference a specific transport mechanism.
  • TRANSMIT_CODE_LANGUAGE — identifies the language or platform context in which the protocol's procedural code is written and executed.
  • TRANSMIT_CODE_PACKAGE — the database package that encapsulates the business logic for performing the transmission.
  • TRANSMIT_CODE_ENTRY_POINT — the callable routine within the package that the payment engine invokes to execute the protocol.
  • ZD_EDITION_NAME — the edition segment that supports Edition-Based Redefinition, enabling online patching in release 12.2.x.
  • Standard WHO/audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER — record row ownership, timestamps, and optimistic locking.

Notably, the table stores only the identity and callable entry point of a protocol; descriptive, translatable names and user-facing text reside in the companion table IBY_TRANSMIT_PROTOCOLS_TL, which shares the same TRANSMIT_PROTOCOL_CODE key.

Common Use Cases and Queries

Typical uses include identifying which protocols are configured before enabling a new payment system profile, tracing a failed transmission back to the package and entry point that were executed, and auditing which protocols are referenced by credit card, debit card, or EFT processing profiles. A common lookup joins the base and translated tables to resolve user-visible protocol names:

  • Resolve code to displayed name: SELECT b.transmit_protocol_code, t.transmit_protocol_name FROM iby_transmit_protocols_b b, iby_transmit_protocols_tl t WHERE b.transmit_protocol_code = t.transmit_protocol_code AND t.language = USERENV('LANG');
  • Inspect the implementation entry point: SELECT transmit_protocol_code, transmit_code_package, transmit_code_entry_point FROM iby_transmit_protocols_b ORDER BY transmit_protocol_code;
  • Find profiles referencing a protocol: join IBY_FNDCPT_SYS_EFT_PF_B on FUNDS_XFER_TRANS_PRTCL_CODE, VERIFY_TRANS_PRTCL_CODE, or QUERY_TRANS_PRTCL_CODE, or IBY_SYS_PMT_PROFILES_B on TRANSMIT_PROTOCOL_CODE.
  • Trace runtime activity: join IBY_PMT_SYS_TRANSMISSIONS on TRANSMIT_PROTOCOL_CODE to see which protocol was used for a given transmission.

Because impact analysis is important, queries against the eleven dependent foreign-key relationships help determine whether a protocol can be safely disabled or edited.

Related Objects

The table is the parent in numerous foreign-key relationships, making these the most significant related objects:

  • IBY_TRANSMIT_PROTOCOLS_TL — translated/language rows keyed by TRANSMIT_PROTOCOL_CODE; supplies display names and descriptions.
  • IBY_TRANSMIT_CONFIGS_B — configuration definitions referencing TRANSMIT_PROTOCOL_CODE.
  • IBY_TRANSMIT_PARAMETERS_B — protocol-specific parameters referencing TRANSMIT_PROTOCOL_CODE.
  • IBY_PMT_SYS_TRANSMISSIONS — runtime transmission records referencing TRANSMIT_PROTOCOL_CODE.
  • IBY_SYS_PMT_PROFILES_B — payment system profiles referencing TRANSMIT_PROTOCOL_CODE.
  • IBY_FNDCPT_SYS_EFT_PF_B — EFT processing profiles referencing FUNDS_XFER_TRANS_PRTCL_CODE, VERIFY_TRANS_PRTCL_CODE, and QUERY_TRANS_PRTCL_CODE.
  • IBY_FNDCPT_SYS_CC_PF_B — credit card processing profiles referencing SETTLEMENT_TRANS_PRTCL_CODE and QUERY_TRANS_PRTCL_CODE.
  • IBY_FNDCPT_SYS_DC_PF_B — debit card processing profiles referencing ONLINE_DEB_TRANS_PRTCL_CODE, SETTLEMENT_TRANS_PRTCL_CODE, and QUERY_TRANS_PRTCL_CODE.