Search Results iby_delivery_channels_vl




Overview
Explore in AI Chat

Overview

IBY_DELIVERY_CHANNELS_VL is a bilingual (translated) view in the Oracle Payments (IBY) module, owned by the APPS schema. It exposes the delivery channel configuration used by Oracle Payments to determine how payment instructions, remittance advice, and other payment-related documents are transmitted to payees, banks, or external systems. A delivery channel defines a specific transport mechanism together with a formatting convention — for example, a particular file format delivered through a specific eBusiness Suite output channel. Because payment processing frequently needs to route documents differently by territory or trading partner, the delivery channel definition is a core reference object for the payment process profile and payment system configuration.

The view follows the standard Oracle EBS "_VL" pattern: it joins the base table to its translation table and filters the translation rows to the language of the current session, as established by USERENV('LANG'). This ensures that consumers see only the meaning and description in a single language while the underlying code values remain language-independent. The view is valid in release 12.2.2 and is a documented ETRM object for IBY Payments.

Underlying Base Objects

The view is defined over two documented base objects, referenced through synonyms:

  • IBY_DELIVERY_CHANNELS_B — the base (non-translated) table holding the delivery channel code, format value, territory code, inactive date, audit columns, object version number, and seeded flag.
  • IBY_DELIVERY_CHANNELS_TL — the translation table holding the language-specific MEANING and DESCRIPTION for each delivery channel code.

The join condition is B.DELIVERY_CHANNEL_CODE = T.DELIVERY_CHANNEL_CODE AND T.LANGUAGE = USERENV('LANG'), so each row of the view represents one delivery channel in the session language. Because the join is an inner join, delivery channels lacking a translation row in the current language would not be returned; in practice Oracle seeds translations for the installed languages.

Key Columns

  • ROW_ID — the ROWID of the underlying base table row; useful for direct DML locators but generally not used in reporting.
  • DELIVERY_CHANNEL_CODE — the primary business key and the value referenced by payment configuration objects.
  • MEANING — the translated display name of the delivery channel, sourced from IBY_DELIVERY_CHANNELS_TL.
  • DESCRIPTION — the translated longer description of the channel's purpose.
  • FORMAT_VALUE — the format associated with the channel, used by the payments engine when generating output.
  • TERRITORY_CODE — the territory to which the channel applies, enabling country- or region-specific delivery routing.
  • INACTIVE_DATE — the date from which the channel is no longer active; a NULL value indicates an active channel.
  • SEEDED_FLAG — indicates whether the row was seeded by Oracle (Y) or created by the customer (N), which governs upgrade behavior.
  • Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER support standard EBS audit and optimistic locking conventions.

Common Use Cases and Queries

Typical scenarios include validating which delivery channels are available in a given territory, listing only active channels for payment configuration review, and joining the view to payment process profiles or payment systems to trace how documents will be routed. Because the view is translated, it is the preferred source for reports and LOVs that must display the channel name in the user's language.

List active delivery channels with their translated names:

  • SELECT delivery_channel_code, meaning, description, format_value, territory_code FROM iby_delivery_channels_vl WHERE inactive_date IS NULL ORDER BY meaning;

Identify customer-defined (non-seeded) channels:

  • SELECT delivery_channel_code, meaning, seeded_flag FROM iby_delivery_channels_vl WHERE seeded_flag = 'N';

Restrict to a specific territory for regional configuration checks:

  • SELECT delivery_channel_code, meaning, territory_code FROM iby_delivery_channels_vl WHERE territory_code = 'US' AND (inactive_date IS NULL OR inactive_date > SYSDATE);

These queries are read-only and safe for reporting. As with all _VL views, the result set reflects only rows translated into the session language, so concurrent-language reporting should explicitly set the language environment before execution.