Results for “iby_fndcpt_user_cc_pf_vl”

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

Overview

IBY_FNDCPT_USER_CC_PF_VL is a seeded, VALID view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the IBY (Payments) product family and exposes user-defined credit card profile definitions in a language-translated, descriptive form. Functionally it is the "_VL" (view with translation joined) presentation layer over the user credit card profile base table, combining the technical attributes of the base entity with the user-facing profile name drawn from the translation table. It is used by the Payments foundation (FNDCPT) infrastructure whenever a user credit card profile must be resolved to the transaction configuration identifiers that govern how the profile communicates with a payment processor. Because the view filters the translation table by the session language (USERENV('LANG')), it returns each profile name in the language of the connected user session. The view is read-only and should be treated as an inquiry and reporting object rather than a maintenance interface; inserts and updates are performed directly against the underlying base and translation tables by the Payments setup forms.

Underlying Base Objects

The view is defined over two documented base objects, both exposed to APPS as synonyms:

• IBY_FNDCPT_USER_CC_PF_B — the base table holding one row per user credit card profile, including the profile code, the associated BEP account, the inactivity date, and the three transaction configuration identifiers (query, online authorization, settlement). The view text selects all columns from this alias B, including ROWID as ROW_ID and the standard WHO columns.
• IBY_FNDCPT_USER_CC_PF_TL — the translation table holding the profile name in each installed language. The join predicate is B.USER_CC_PROFILE_CODE = T.USER_CC_PROFILE_CODE AND T.LANGUAGE = USERENV('LANG').

The relationship is a one-to-one join on USER_CC_PROFILE_CODE restricted to the current session language, so the view returns exactly one row per active-language profile definition.

Key Columns

• ROW_ID — the ROWID of the base table row; useful as a unique row identifier in queries.
• BEP_ACCOUNT_ID — identifier of the BEP (Bank Exchange Profile / payment account) record to which the user credit card profile is attached.
• USER_CC_PROFILE_CODE — the unique code identifying the user credit card profile; the join key between base and translation tables.
• SYS_CC_PROFILE_CODE — the system credit card profile on which the user profile is patterned.
• QUERY_TRANS_CONFIG_ID — the transaction configuration used for query (inquiry) operations against the processor.
• ONLINE_AUTH_TRANS_CONFIG_ID — the transaction configuration that governs online authorization requests, i.e., the real-time approval flow for a card transaction.
• SETTLEMENT_TRANS_CONFIG_ID — the transaction configuration used for settlement (capture) processing.
• INACTIVE_DATE — date from which the profile is no longer effective; NULL indicates an active profile.
• USER_CC_PROFILE_NAME — the translated, user-facing profile name returned by the view layer.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard concurrency-control and audit columns inherited from the base table.

The column the user searched for, ONLINE_AUTH_TRANS_CONFIG_ID, is the specific attribute that maps a user credit card profile to the IBY transaction configuration used for online authorization; resolving it is a common diagnostic step when authorization requests fail or route to the wrong processor settings.

Common Use Cases and Queries

Typical uses include reporting the transaction configuration assigned to each user credit card profile, verifying that online authorization is configured before enabling a payment method, and diagnosing mismatches between query, authorization, and settlement processing.

• List all active profiles with their authorization configuration:

  SELECT user_cc_profile_code, user_cc_profile_name,
         online_auth_trans_config_id
  FROM   apps.iby_fndcpt_user_cc_pf_vl
  WHERE  inactive_date IS NULL;

• Find the profile tied to a specific authorization transaction configuration:

  SELECT user_cc_profile_code, user_cc_profile_name, bep_account_id
  FROM   apps.iby_fndcpt_user_cc_pf_vl
  WHERE  online_auth_trans_config_id = :p_trans_config_id;

• Audit profiles where any of the three configuration identifiers is missing:

  SELECT user_cc_profile_code, query_trans_config_id,
         online_auth_trans_config_id, settlement_trans_config_id
  FROM   apps.iby_fndcpt_user_cc_pf_vl
  WHERE  query_trans_config_id IS NULL
     OR  online_auth_trans_config_id IS NULL
     OR  settlement_trans_config_id IS NULL;

Because the view applies the session-language filter automatically, queries executed through the EBS application return profile names in the user's current language without additional join logic.