Search Results iby_acct_pmt_profiles_vl
Overview
IBY_ACCT_PMT_PROFILES_VL is an APPS-owned, valid database view in the Oracle Payments (IBY) module of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. It is a translated (_VL) view that exposes account payment profiles—the configuration records that determine how a specific bank account or payment system profile transmits, secures, and numbers payment instructions. The view presents a language-specific, denormalized read model of payment profile definitions, joining the base table to its translation table and filtering the translation by the session language through USERENV('LANG'), so that each user sees the descriptive name in their own language while the underlying identifiers remain consistent across locales.
Because payment profiles hold the operational parameters used by the payments engine—transmission configuration, security configuration, acknowledgment settings, and document numbering sequences—this view is a primary reference for reporting, data extraction, and integration. It is widely used in Oracle Payments setup validation, diagnostics of payment instruction formatting, and downstream ETL into data warehouses or reconciliation platforms.
Underlying Base Objects
The view is defined over two documented base objects:
- IBY_ACCT_PMT_PROFILES_B (SYNONYM) — the base table holding the language-independent attributes of each payment profile, including the primary key, system profile code, configuration identifiers, sequence counter values, and audit columns.
- IBY_ACCT_PMT_PROFILES_TL (SYNONYM) — the translation table holding the language-dependent PAYMENT_PROFILE_NAME, keyed by PAYMENT_PROFILE_ID and LANGUAGE.
The two are combined on PAYMENT_PROFILE_ID, with the translation restricted to the user's language. The "_VL" suffix confirms this is a view that presents translatable data for the current session locale. The synonyms resolve to the underlying application tables registered under the APPS schema.
Key Columns
- ROW_ID — the ROWID from the base table, used for direct row addressing.
- PAYMENT_PROFILE_ID — unique identifier and join key between the base and translation tables.
- PAYMENT_PROFILE_NAME — the user-facing, language-specific profile name.
- SYSTEM_PROFILE_CODE — the internal system identifier for the profile.
- BEP_ACCOUNT_ID — the bank account (BEP) associated with the profile.
- SECURITY_CONFIGURATION_ID and TRANSMIT_CONFIGURATION_ID — the security and transmission configurations applied when delivering payment instructions.
- ACK_SEC_CONFIG_ID and ACK_TRANSMIT_CONFIG_ID — the security and transmission configurations used for acknowledgment processing.
- RESET_VALUE_1/2/3, LAST_USED_NUMBER_1/2/3, RESET_REQUEST_1/2/3 — the document numbering model, capturing the reset threshold, the last used sequence number, and whether a reset has been requested for each of three numbering sequences.
- INACTIVE_DATE — the date on which the profile became inactive, if applicable.
- CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER — standard audit and optimistic locking columns.
Common Use Cases and Queries
Typical scenarios include listing active payment profiles for a given bank account, auditing numbering usage, and validating security/transmission configuration assignments.
List all active profiles with their names and system codes:
SELECT payment_profile_id, payment_profile_name, system_profile_code FROM iby_acct_pmt_profiles_vl WHERE inactive_date IS NULL;
Inspect numbering state for a profile:
SELECT payment_profile_name, last_used_number_1, reset_value_1, reset_request_1 FROM iby_acct_pmt_profiles_vl WHERE payment_profile_id = :p_profile_id;
Correlate profiles with transmission and security configurations:
SELECT payment_profile_name, transmit_configuration_id, security_configuration_id FROM iby_acct_pmt_profiles_vl ORDER BY payment_profile_name;
Because the view embeds the language filter, queries automatically return the profile name in the session language, simplifying multilingual reporting and integration extracts.
-
View: IBY_ACCT_PMT_PROFILES_VL
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:IBY.IBY_ACCT_PMT_PROFILES_VL, object_name:IBY_ACCT_PMT_PROFILES_VL, status:VALID, product: IBY - Payments , implementation_dba_data: APPS.IBY_ACCT_PMT_PROFILES_VL ,
-
View: IBY_ACCT_PMT_PROFILES_VL
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:IBY.IBY_ACCT_PMT_PROFILES_VL, object_name:IBY_ACCT_PMT_PROFILES_VL, status:VALID, product: IBY - Payments , implementation_dba_data: APPS.IBY_ACCT_PMT_PROFILES_VL ,
-
SYNONYM: APPS.IBY_ACCT_PMT_PROFILES_B
12.2.2
owner:APPS, object_type:SYNONYM, object_name:IBY_ACCT_PMT_PROFILES_B, status:VALID,
-
VIEW: APPS.IBY_PAYMENT_PROFILES
12.1.1
-
VIEW: APPS.IBY_PAYMENT_PROFILES
12.2.2
-
SYNONYM: APPS.IBY_ACCT_PMT_PROFILES_B
12.1.1
owner:APPS, object_type:SYNONYM, object_name:IBY_ACCT_PMT_PROFILES_B, status:VALID,
-
SYNONYM: APPS.IBY_ACCT_PMT_PROFILES_TL
12.2.2
owner:APPS, object_type:SYNONYM, object_name:IBY_ACCT_PMT_PROFILES_TL, status:VALID,
-
SYNONYM: APPS.IBY_ACCT_PMT_PROFILES_TL
12.1.1
owner:APPS, object_type:SYNONYM, object_name:IBY_ACCT_PMT_PROFILES_TL, status:VALID,
-
VIEW: APPS.IBY_ACCT_PMT_PROFILES_VL
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:IBY.IBY_ACCT_PMT_PROFILES_VL, object_name:IBY_ACCT_PMT_PROFILES_VL, status:VALID,
-
View: IBY_PAYMENT_PROFILES
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:IBY.IBY_PAYMENT_PROFILES, object_name:IBY_PAYMENT_PROFILES, status:VALID, product: IBY - Payments , implementation_dba_data: APPS.IBY_PAYMENT_PROFILES ,
-
12.2.2 FND Design Data
12.2.2
-
12.1.1 FND Design Data
12.1.1
-
View: IBY_PAYMENT_PROFILES
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:IBY.IBY_PAYMENT_PROFILES, object_name:IBY_PAYMENT_PROFILES, status:VALID, product: IBY - Payments , implementation_dba_data: APPS.IBY_PAYMENT_PROFILES ,
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1
-
VIEW: APPS.IBY_ACCT_PMT_PROFILES_VL
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:IBY.IBY_ACCT_PMT_PROFILES_VL, object_name:IBY_ACCT_PMT_PROFILES_VL, status:VALID,
-
VIEW: APPS.IBY_PAYMENT_PROFILES
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:IBY.IBY_PAYMENT_PROFILES, object_name:IBY_PAYMENT_PROFILES, status:VALID,
-
VIEW: APPS.IBY_PAYMENT_PROFILES
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:IBY.IBY_PAYMENT_PROFILES, object_name:IBY_PAYMENT_PROFILES, status:VALID,
-
eTRM - IBY Tables and Views
12.1.1
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 ,
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1
-
eTRM - IBY Tables and Views
12.1.1
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 ,