Results for “payment_channel_code”

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

Overview

The view IBY_FNDCPT_ALL_PMT_CHANNELS_V is an Oracle Applications (APPS) owned database object residing in the IBY – Payments product module. It exposes payment channel definitions used throughout Oracle Payments (IBY) and consumes them in Oracle Payables, Receivables, and related subledgers. In Oracle EBS 12.1.1 and 12.2.2, payment channels represent the delivery mechanisms by which funds are disbursed or collected — for example, check, wire, ACH, or electronic funds transfer. The view presents the language-translated channel name, its functional code, and the associated instrument type, giving reporting and integration layers a navigation-friendly presentation of the underlying payment channel configuration without requiring callers to know the internal base/tl table split.

The object is documented as a VALID view with the purpose of exposing active payment channels for a given user language. It filters out channels that have been deactivated, so consumers see only currently effective channels. This makes the view a natural reference point for LOV queries, concurrent program parameters, and integration payloads that must be populated with valid payment channel values.

Underlying Base Objects

The view is defined over two documented base objects:

• IBY_FNDCPT_PMT_CHNNLS_B (SYNONYM) — the base table holding the canonical, language-independent payment channel records, including the payment channel code, the instrument type association, and the inactivation date.
• IBY_FNDCPT_PMT_CHNNLS_TL (SYNONYM) — the translation table holding the language-specific payment channel name.

In the documented view text, the two sources are joined on PAYMENT_CHANNEL_CODE, with the translation table restricted by LANGUAGE = USERENV('LANG'). This is the standard Oracle EBS multilingual pattern: the translation table supplies the descriptive name in the session language while _B supplies the stable code and attributes. The _ALL naming prefix reflects that both base and translated rows are combined. An NVL(INACTIVE_DATE, ...) predicate in the view filter is used to exclude deactivated channels from the result set.

Key Columns

• ROW_ID — the ROWID of the underlying base table row, exposing a physical row identifier useful for direct row addressing.
• PAYMENT_CHANNEL_NAME — the language-translated descriptive name of the payment channel, suitable for display in LOVs and reports.
• PAYMENT_CHANNEL_CODE — the language-independent internal code used to key the payment channel in transactional tables and integration interfaces.
• INSTRUMENT_TYPE — the instrument type associated with the payment channel, such as check, wire transfer, or electronic. This is the column most commonly searched by implementers, because instrument type determines downstream behavior for payment formatting, transmission, and bank file generation.

The presence of INSTRUMENT_TYPE is significant: it links the payment channel to the physical payment instrument and drives how the payment instruction is built in Oracle Payments.

Common Use Cases and Queries

Typical uses include populating a report or LOV with valid payment channels, and driving integration logic based on the instrument type. A sample query is:

• SELECT payment_channel_code, payment_channel_name, instrument_type FROM iby_fndcpt_all_pmt_channels_v ORDER BY payment_channel_name;
• SELECT payment_channel_name FROM iby_fndcpt_all_pmt_channels_v WHERE instrument_type = 'CHECK';

Because the view already filters deactivated channels and applies the session-language translation filter, custom queries should generally select from this view rather than the base tables directly to remain consistent with Oracle Payments presentation rules.