Search Results iby_acct_pmt_profiles

Overview

The table IBY_ACCT_PMT_PROFILES_TL is a core translation table within the Oracle E-Business Suite Payments module (IBY). It stores the translated, language-specific descriptions and names for payment profile records defined in its base table. In Oracle EBS, a payment profile is a configuration entity that groups a set of payment instructions and defines how they are processed, formatted, and transmitted. The primary role of this table is to support the multilingual capabilities of the application, allowing the descriptive attributes of a payment profile to be displayed in a user's preferred language, such as US English, French, or Japanese. This is a standard pattern in Oracle EBS, where '_TL' suffix tables hold translatable seed and user data, enabling global deployments.

Key Information Stored

The table's structure is designed to hold translated text linked to a specific payment profile and language. The primary key is a composite of PAYMENT_PROFILE_ID and LANGUAGE, ensuring a unique translation entry per profile per language. The PAYMENT_PROFILE_ID column is a foreign key that references the unique identifier in the base payment profile table. The LANGUAGE column stores the standard Oracle language code (e.g., 'US', 'F', 'JA'). The most critical data columns typically include PROFILE_NAME and DESCRIPTION (or similarly named columns, though not explicitly listed in the brief metadata), which contain the translated text for the profile's name and explanatory description. These columns are populated during installation with seed data for supported languages and can be extended via translation tools.

Common Use Cases and Queries

The primary use case is the dynamic presentation of payment profile information in the user interface and reports based on the session language. A common operational query retrieves the translated name and description for a specific profile ID in the current session language. For example, a report listing all active payment profiles would join this table to the base profile table, filtering on the USERENV('LANG') function. Administrators may also query this table to audit or manage translation coverage, identifying profiles missing translations for a required language. Sample SQL to fetch translated data often follows this pattern:

• SELECT tl.profile_name, tl.description FROM iby_acct_pmt_profiles_tl tl WHERE tl.payment_profile_id = :p_profile_id AND tl.language = USERENV('LANG');

Related Objects

This translation table has a direct and critical relationship with its base table, as indicated by the provided foreign key metadata. The primary related object is the table IBY_ACCT_PMT_PROFILES (the base table without the '_TL' suffix). The foreign key in IBY_ACCT_PMT_PROFILES_TL on the PAYMENT_PROFILE_ID column references the primary key of IBY_ACCT_PMT_PROFILES. This is a master-detail relationship where the base table holds the operational and non-translatable attributes, and the '_TL' table holds the translatable attributes. Any application form, API, or report that displays a payment profile's name or description will perform a join to this translation table using the PAYMENT_PROFILE_ID and the session's LANGUAGE to present the correct text.