Search Results iby_delivery_channels_b




Overview
Explore in AI Chat

Overview

The IBY_DELIVERY_CHANNELS_B table is a core reference data object within the Oracle E-Business Suite Payments (IBY) module. It functions as a lookup repository for valid delivery channel codes, which define the method by which payment-related information is transmitted to an external payee or for a payable document. This table is architecturally similar to the standard FND_LOOKUPS table but is specialized for payments with the inclusion of a territory-specific identifier. Its primary role is to provide a controlled, validated list of delivery mechanisms—such as Electronic Data Interchange (EDI), email, or print—that can be assigned during the setup of external payees and the processing of payments and documents payable. This ensures data integrity and consistency across the payment execution flow in both EBS 12.1.1 and 12.2.2.

Key Information Stored

The table's structure is centered on the delivery channel code and its associated territory. The primary key is the DELIVERY_CHANNEL_CODE column, which stores the unique, short identifier for the channel (e.g., 'EFT', 'CHECK'). A critical column is TERRITORY_CODE, which references the FND_TERRITORIES table. This allows for the definition and validation of delivery channels that may be specific to a particular country or region, enabling localized payment practices. While the base table stores the core code and territory, descriptive, translatable information (like the channel name and description) is typically stored in the related translation table, IBY_DELIVERY_CHANNELS_TL.

Common Use Cases and Queries

A primary use case is validating the delivery channel during the creation or update of an external payee record. The application uses this table to present a list of valid channels for a payee's country. For reporting and data validation, common queries include listing all available channels for a specific territory or identifying which payees are set up for a particular channel. For instance, to find all electronic delivery channels valid for the United States, one might use:

SELECT dc.delivery_channel_code, dctl.meaning
FROM iby_delivery_channels_b dc,
    iby_delivery_channels_tl dctl,
    fnd_territories t
WHERE dc.delivery_channel_code = dctl.delivery_channel_code
AND dc.territory_code = t.territory_code
AND t.iso_territory_code = 'US'
AND dctl.language = USERENV('LANG');

Another critical scenario is troubleshooting payment batch issues by verifying the delivery channel codes assigned to documents payable or payment instructions, ensuring they align with the payee's setup.

Related Objects

The IBY_DELIVERY_CHANNELS_B table is a central reference point for several key transactional and setup tables in the Payments module, as documented by its foreign key relationships:

  • Referenced by (Parent): FND_TERRITORIES via the TERRITORY_CODE column.
  • Referenced from (Child Tables):
    • IBY_DELIVERY_CHANNELS_TL (DELIVERY_CHANNEL_CODE) – Stores translated descriptions.
    • IBY_EXTERNAL_PAYEES_ALL (DELIVERY_CHANNEL_CODE) – Defines the preferred payment delivery method for a payee.
    • IBY_DOCS_PAYABLE_ALL (DELIVERY_CHANNEL_CODE) – Specifies the delivery channel for an individual payable document.
    • IBY_PAYMENTS_ALL (DELIVERY_CHANNEL_CODE) – Stores the delivery channel for a specific payment instruction.
    • IBY_TEMP_EXT_PAYEES (DELIVERY_CHANNEL_CODE) – Used during the temporary staging of external payee data.

These relationships underscore the table's integral role in ensuring that delivery channel references are consistent and enforceable from payee setup through to payment execution.