Results for “iby_fndcpt_user_eft_pf_vl”

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

Overview

The IBY_FNDCPT_USER_EFT_PF_VL view is a validated, multilingual (VL) view owned by the APPS schema within the Oracle Payments (IBY) module. It exposes user-defined Electronic Funds Transfer (EFT) payment profiles, combining their translatable descriptive attributes with their underlying configuration data. In Oracle EBS 12.1.1 and 12.2.2, this view is a key reporting and integration surface for administrators, implementation consultants, and support analysts who need to inspect how EFT payment profiles are wired to transaction configuration identifiers. The view is especially relevant to the column VERIFY_TRANS_CONFIG_ID, which represents the transaction configuration used when a payment profile performs a verification (pre-note or account validation) transaction. Because the view resolves the language-specific profile name through USERENV('LANG'), queries return the description in the session's current language, making it suitable for both user-facing reports and language-aware integrations.

Underlying Base Objects

Per the ETRM metadata, the view is defined over two documented synonyms: IBY_FNDCPT_USER_EFT_PF_B (the base table holding non-translatable columns) and IBY_FNDCPT_USER_EFT_PF_TL (the translation table holding the language-specific profile name). The two are joined on USER_EFT_PROFILE_CODE, with the translation restricted to the session language via T.LANGUAGE = USERENV('LANG'). The view therefore inherits all operational columns from the _B table and adds a single descriptive column, USER_EFT_PROFILE_NAME, from the _TL table. As a VL view, it is the standard, language-aware access point for these payment profiles and should be preferred over querying the base tables directly.

Key Columns

• USER_EFT_PROFILE_CODE – Primary business key identifying the user EFT payment profile; used to join the base and translation tables.
• USER_EFT_PROFILE_NAME – Language-specific, user-friendly name sourced from the translation table.
• VERIFY_TRANS_CONFIG_ID – Transaction configuration identifier applied to the payment profile's verification transaction, the column most commonly searched in this context.
• FUNDS_XFER_TRANS_CONFIG_ID – Transaction configuration used for the funds transfer (payment) transaction.
• QUERY_TRANS_CONFIG_ID – Transaction configuration used for query or status-check transactions.
• BEP_ACCOUNT_ID – Identifier of the bank account (BEP account) associated with the profile.
• SYS_EFT_PROFILE_CODE – Reference to the system-level EFT profile from which the user profile may derive defaults.
• INACTIVE_DATE – Date on which the profile became inactive; null indicates an active profile.
• ROW_ID, OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard audit and row-versioning columns.

Common Use Cases and Queries

The most frequent scenario is verifying which transaction configuration a profile uses for verification, particularly when troubleshooting EFT processing errors. The following query returns all active profiles with their verification configuration:

SELECT user_eft_profile_code,
       user_eft_profile_name,
       verify_trans_config_id,
       funds_xfer_trans_config_id,
       query_trans_config_id
FROM   apps.iby_fndcpt_user_eft_pf_vl
WHERE  inactive_date IS NULL;

To isolate a specific verification configuration—for example, after identifying VERIFY_TRANS_CONFIG_ID from an error log—the view can be filtered directly:

SELECT user_eft_profile_code, user_eft_profile_name
FROM   apps.iby_fndcpt_user_eft_pf_vl
WHERE  verify_trans_config_id = :verify_trans_config_id;

Because the view already joins the translation table, it is well suited to reporting that must display the profile name in the user's language, and to integration extracts that require both the configuration identifiers and the descriptive name in a single result set.