Results for “iby_transmit_protocols_vl”

34 results




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

Overview

The IBY_TRANSMIT_PROTOCOLS_VL view is an Oracle E-Business Suite (EBS) dictionary object owned by the APPS schema within the IBY Payments product module. It exposes the list of payment transmission protocols configured in the system, presenting both the descriptive name of each protocol and the technical attributes that define how outbound payment files are generated and dispatched. The view is a party to the standard EBS "_VL" naming convention, meaning it joins a base ("_B") table with a translation ("_TL") table to yield a language-aware result set filtered by the session language.

In reporting and integration contexts, this view serves as the supported read interface for retrieving transmit protocol definitions. Users searching for transmit_code_package are typically investigating which PL/SQL package implements the file-generation logic for a given transmission method, such as a specific bank format, SWIFT, or EDI delivery channel. Because the view is anchored to the translated objects, it is safe for multilingual deployments and is preferred over direct base-table access.

Underlying Base Objects

The ETRM metadata documents the view as being defined over two referenced base objects: IBY_TRANSMIT_PROTOCOLS_B and IBY_TRANSMIT_PROTOCOLS_TL, both exposed to the APPS schema as synonyms. The _B table holds the language-independent protocol definition, including the code package and entry point that drive transmission execution. The _TL table holds the translated protocol name keyed by LANGUAGE.

The defining SQL joins the two on TRANSMIT_PROTOCOL_CODE and filters T.LANGUAGE = USERENV('LANG'), returning only the rows matching the current session language. Most columns are sourced from the _B table, while TRANSMIT_PROTOCOL_NAME is drawn from the _TL table, and ROW_ID is the row identifier of the base-table record.

Key Columns

  • TRANSMIT_PROTOCOL_CODE — The primary business key identifying the transmission protocol.
  • TRANSMIT_PROTOCOL_NAME — The language-specific display name of the protocol, sourced from the translation table.
  • TRANSMIT_CODE_LANGUAGE — The language in which the transmission code was authored.
  • TRANSMIT_CODE_PACKAGE — The PL/SQL package that implements the transmission logic for this protocol; the column most directly implicated in the user's search.
  • TRANSMIT_CODE_ENTRY_POINT — The specific program unit within TRANSMIT_CODE_PACKAGE invoked to perform the transmission.
  • ROW_ID — The row identifier of the underlying base-table record.
  • Audit columns — LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, and OBJECT_VERSION_NUMBER provide standard EBS concurrency and audit tracking.

Common Use Cases and Queries

A common investigative query is to identify which PL/SQL package and entry point implement a specific protocol, or to enumerate all protocols and their implementing code. The following sample retrieves the protocol code, name, and code-package binding:

  • SELECT transmit_protocol_code, transmit_protocol_name, transmit_code_package, transmit_code_entry_point FROM iby_transmit_protocols_vl ORDER BY transmit_protocol_code;

To locate the implementation for a searched package, a filtered variant is used:

  • SELECT transmit_protocol_code, transmit_code_package, transmit_code_entry_point FROM iby_transmit_protocols_vl WHERE transmit_code_package = :p_package;

These results support troubleshooting payment file generation, auditing custom protocol extensions, and driving integration logic that must map a configured protocol to its executing code. Because the view is language-filtered, querying it returns only the protocol names valid for the run-time language, making it suitable for both standard reports and programmatic lookups in concurrent programs and interfaces.