Search Results iby_payment_methods




Overview
Explore in AI Chat

Overview

IBY_PAYMENT_METHODS_TL is the translation (language) table for Oracle Payments payment methods in Oracle E-Business Suite Release 12.1.1 and 12.2.2. A payment method is a payment attribute on a document payable that indicates how the first party payer intends to make the payment; examples include check, electronic funds transfer, wire, and clearing. The base definition of each payment method is held in IBY_PAYMENT_METHODS_B, while IBY_PAYMENT_METHODS_TL carries the language-dependent descriptive text — specifically the translated payment method name and description — for each defined method. Every row is uniquely identified by the combination of PAYMENT_METHOD_CODE and LANGUAGE, which forms the primary key IBY_PAYMENT_METHODS_TL_PK.

From a Data Vault modeling perspective, the mined relationship structure classifies this object as satellite-leaning. In practice this is appropriate: IBY_PAYMENT_METHODS_TL behaves as a descriptive satellite attached to the IBY_PAYMENT_METHODS_B hub, since it stores descriptive, language-qualified attributes keyed by the business code PAYMENT_METHOD_CODE rather than introducing new independent business entities or many-to-many associations.

Key Information Stored

The table contains twelve documented columns. The most significant are:

  • PAYMENT_METHOD_CODE — the business identifier of the payment method; the leading column of the primary key and of the unique index IBY_PAYMENT_METHODS_TL_U1.
  • LANGUAGE — the language code of the translated row; paired with PAYMENT_METHOD_CODE in the primary key.
  • SOURCE_LANG — the language the row's text originated from, used by the translation framework.
  • PAYMENT_METHOD_NAME — the translated display name of the payment method.
  • DESCRIPTION — the translated free-text description of the payment method.
  • OBJECT_VERSION_NUMBER — optimistic locking/versioning column used by the Oracle Applications framework.
  • ZD_EDITION_NAME — the editioning column used for the 12.2 online patching (edition-based redefinition) model; it also appears in the unique index IBY_PAYMENT_METHODS_TL_U1 alongside PAYMENT_METHOD_CODE and LANGUAGE.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO columns recording audit and responsibility information.

The primary key is a composite of PAYMENT_METHOD_CODE and LANGUAGE. The unique index IBY_PAYMENT_METHODS_TL_U1 extends that with ZD_EDITION_NAME. Note that PAYMENT_METHOD_CODE functions as a foreign-key reference to the base table rather than as an independent surrogate key.

Common Use Cases and Queries

This table is the standard source for reporting payment method names and descriptions in a specific language. A typical lookup joins the translation to the base table:

  • Localized payment method lists — SELECT m.payment_method_code, t.payment_method_name, t.description FROM iby_payment_methods_b m, iby_payment_methods_tl t WHERE m.payment_method_code = t.payment_method_code AND t.language = USERENV('LANG').
  • Enumeration for LOVs or validation — supplying the set of valid payment method codes and their display names on payment forms and setup pages.
  • Audit and reconciliation reporting — filtering on CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE and LAST_UPDATED_BY to trace changes to payment method setup, particularly useful for financial controls.
  • Multi-language analysis — grouping by LANGUAGE to verify that every payment method has the required translated rows across enabled languages.

Related Objects

The most significant related object is the base table that holds the language-independent definition:

  • IBY_PAYMENT_METHODS_B — referenced via the foreign key IBY_PAYMENT_METHODS_TL.PAYMENT_METHOD_CODE → IBY_PAYMENT_METHODS_B. This is the mandatory join partner for any query returning the base definition alongside a translation.
  • IBY_PAYMENT_METHODS_VL — the conventional translated view pattern that joins the _B and _TL tables and is typically queried instead of the underlying tables directly.
  • IBY_PAYMENT_METHODS_TL_PK / IBY_PAYMENT_METHODS_TL_U1 — the primary key constraint and unique index enforcing uniqueness of code, language, and edition.
  • Payment processing objects in the IBY and AP modules (such as payment instrument and document payable definitions) that consume the payment method code when configuring or executing payments.

When querying this object, always constrain or join on LANGUAGE to avoid returning one row per enabled locale.

  • Table: IBY_PAYMENT_METHODS_TL 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_PAYMENT_METHODS_TL,  object_name:IBY_PAYMENT_METHODS_TL,  status:VALID,  product: IBY - Payments ,  description: IBY_PAYMENT_METHODS stores the payment methods that Oracle Payments supports. A payment method is a payment attribute on a document payable that indicates how the first party payer is going to make the payment. Examples of payment methods i ,  implementation_dba_data: IBY.IBY_PAYMENT_METHODS_TL , 

  • Table: IBY_PAYMENT_METHODS_B 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_PAYMENT_METHODS_B,  object_name:IBY_PAYMENT_METHODS_B,  status:VALID,  product: IBY - Payments ,  description: IBY_PAYMENT_METHODS stores the payment methods that Oracle Payments supports. A payment method is a payment attribute on a document payable that indicates how the first party payer is going to make the payment. Examples of payment methods i ,  implementation_dba_data: IBY.IBY_PAYMENT_METHODS_B , 

  • TABLE: IBY.IBY_PMT_MTHD_ATTRIB_APPL 12.1.1

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_PMT_MTHD_ATTRIB_APPL,  object_name:IBY_PMT_MTHD_ATTRIB_APPL,  status:VALID, 

  • TABLE: IBY.IBY_PMT_MTHD_ATTRIB_APPL 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_PMT_MTHD_ATTRIB_APPL,  object_name:IBY_PMT_MTHD_ATTRIB_APPL,  status:VALID, 

  • TABLE: IBY.IBY_PAYMENT_METHODS_TL 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_PAYMENT_METHODS_TL,  object_name:IBY_PAYMENT_METHODS_TL,  status:VALID, 

  • TABLE: IBY.IBY_PAYMENT_METHODS_TL 12.1.1

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_PAYMENT_METHODS_TL,  object_name:IBY_PAYMENT_METHODS_TL,  status:VALID, 

  • TABLE: IBY.IBY_PAYMENT_METHODS_B 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_PAYMENT_METHODS_B,  object_name:IBY_PAYMENT_METHODS_B,  status:VALID, 

  • TABLE: IBY.IBY_PAYMENT_METHODS_B 12.1.1

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_PAYMENT_METHODS_B,  object_name:IBY_PAYMENT_METHODS_B,  status:VALID, 

  • eTRM - IBY Tables and Views 12.2.2

    description: Stores the user privilege settings for viewing sensitive data in iPayment operations UI , 

  • eTRM - IBY Tables and Views 12.2.2

    description: Stores the user privilege settings for viewing sensitive data in iPayment operations UI , 

  • eTRM - IBY Tables and Views 12.1.1

    description: Stores the user privilege settings for viewing sensitive data in iPayment operations UI ,