Results for “payment_profile_id”

50+ results




Overview
Explore in AI Chat

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

Overview

IBY.IBY_ACCT_PMT_PROFILES_TL is the translation table for payment profile definitions within the Oracle Payments (IBY) module of Oracle E-Business Suite, applicable to releases 12.1.1 and 12.2.2. Payment profiles describe how disbursements and receipts are processed for a given payer, payee, or internal organization — capturing parameters such as payment method assignment, bank account sourcing, remittance delivery, and format selection. The base entity resides in IBY_ACCT_PMT_PROFILES_B, while the _TL table stores the language-dependent textual attributes, chiefly the profile name. One row exists per payment profile per installed language, which allows a single logical profile to be presented in multiple languages without duplicating the underlying configuration.

From a Data Vault modeling perspective, the mined foreign-key structure classifies this object as satellite-leaning. It behaves as a descriptive, language-qualified satellite attached to the payment profile hub: it carries no independent identity of its own and derives its grain entirely from the parent profile and the language code. The primary key, IBY_ACCT_PMT_PROFILES_TL_PK, is composite over PAYMENT_PROFILE_ID and LANGUAGE, reinforcing this dependent relationship.

Key Information Stored

The table comprises eleven columns. The most significant are listed below.

  • PAYMENT_PROFILE_ID — Surrogate foreign key to the parent payment profile in IBY_ACCT_PMT_PROFILES_B. This is the join column that binds the translation row to its base entity.
  • LANGUAGE — The installed language code for the translated text; part of the composite primary key.
  • PAYMENT_PROFILE_NAME — The descriptive name of the payment profile as displayed to users in the given language.
  • SOURCE_LANG — The language of the source (usually the creation language), used by the translation framework to track lineage.
  • CREATED_BY, CREATION_DATE — Standard audit columns recording the creating user and timestamp.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard audit columns capturing the most recent modification context.
  • OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle Application Framework to control concurrent updates.
  • ZD_EDITION_NAME — Editioning column introduced with E-Business Suite 12.2 online patching; it participates in the unique index IBY_ACCT_PMT_PROFILES_TL_U1.

The composite primary key (PAYMENT_PROFILE_ID, LANGUAGE) provides row uniqueness, while the unique index IBY_ACCT_PMT_PROFILES_TL_U1 over (PAYMENT_PROFILE_ID, LANGUAGE, ZD_EDITION_NAME) is the documented business-key candidate, ensuring one translation per profile, language, and edition.

Common Use Cases and Queries

Typical reporting scenarios involve resolving the human-readable profile name in the session language while restricting to the active edition. A common pattern joins the translation table to the base table:

  • Retrieve localized profile names: SELECT b.payment_profile_id, t.payment_profile_name FROM iby_acct_pmt_profiles_b b, iby_acct_pmt_profiles_tl t WHERE b.payment_profile_id = t.payment_profile_id AND t.language = USERENV('LANG');
  • Audit translation coverage across languages by grouping on LANGUAGE and counting distinct PAYMENT_PROFILE_ID values.
  • Edition-aware queries in 12.2.x filter on ZD_EDITION_NAME to avoid retrieving rows from inactive editions during online patching.
  • Concurrent-update diagnostics examine OBJECT_VERSION_NUMBER, LAST_UPDATED_BY, and LAST_UPDATE_DATE to trace who modified a profile name and when.

These queries underpin payment configuration reports, localization validation, and troubleshooting of profile display issues in the Payments setup user interface.

Related Objects

  • IBY_ACCT_PMT_PROFILES_B — The base (non-translated) payment profile table; joined on PAYMENT_PROFILE_ID, and the principal parent of this translation row.
  • IBY_ACCT_PMT_PROFILES_VL — The translated view layered over the _B and _TL tables, commonly queried instead of the raw tables.
  • IBY_ACCT_PMT_PROFILES_TL_PK — The composite primary key constraint (PAYMENT_PROFILE_ID, LANGUAGE).
  • IBY_ACCT_PMT_PROFILES_TL_U1 — The unique index providing the business-key candidate, including ZD_EDITION_NAME in 12.2.
  • IBY_PAYMENT_PROFILES / IBY_FNDCPT_PMT_PROFILES — Related profile configuration entities that consume the profile identifier for payment processing.
  • FND_LANGUAGES — Source of valid LANGUAGE and SOURCE_LANG values used by the translation framework.
  • FND_TERRITORIES — Frequently joined for locale-specific reporting of profile configuration.

Together these objects form the payment profile configuration layer that Oracle Payments relies on to drive disbursement and receipt processing consistently across languages.