Search Results iby_fndcpt_user_cc_pf_b_pk

Overview

The table IBY_FNDCPT_USER_CC_PF_B is a core data object within the Oracle E-Business Suite (EBS) Payments (IBY) module. It serves as the base table for storing user-defined credit card payment profiles. These profiles are critical configuration entities that define the processing rules, security settings, and transaction handling parameters for credit card payments initiated by a specific user or responsibility. The table's role is to enable secure, flexible, and configurable credit card transaction processing by linking user-specific payment instructions to system-wide configurations for authorization, settlement, and query transactions.

Key Information Stored

The table's primary key, USER_CC_PROFILE_CODE, uniquely identifies each user-defined profile. Its structure is designed to link user configurations to broader system setups through foreign key relationships. Key columns include USER_CC_PROFILE_CODE, which holds the unique identifier for the profile, and SYS_CC_PROFILE_CODE, which likely references a system-level template or default profile. Crucially, the table stores references to specific transaction configurations via IDs for ONLINE_AUTH_TRANS_CONFIG_ID, SETTLEMENT_TRANS_CONFIG_ID, and QUERY_TRANS_CONFIG_ID, dictating how different types of credit card transactions are processed. The BEP_ACCOUNT_ID column links the profile to a specific Business Event Processing (BEP) account, connecting payment instructions to the appropriate financial institution or payment gateway setup.

Common Use Cases and Queries

A primary use case is the administration and auditing of user-specific credit card payment setups. System administrators may query this table to verify configurations or troubleshoot transaction errors. A common reporting need is to list all active user-defined profiles along with their associated system profile and BEP account. A sample query for this would be: SELECT USER_CC_PROFILE_CODE, SYS_CC_PROFILE_CODE, BEP_ACCOUNT_ID FROM IBY.IBY_FNDCPT_USER_CC_PF_B WHERE END_DATE IS NULL;. Another critical scenario involves joining to transaction configuration tables to validate the end-to-end setup for a payment flow, ensuring that the authorization, settlement, and inquiry services are correctly mapped for a given user profile before processing live transactions.

Related Objects

The table maintains several documented foreign key relationships, integrating it deeply into the Payments architecture. Its primary key is enforced by the IBY_FNDCPT_USER_CC_PF_B_PK constraint. Key related objects include:

• IBY_BEPKEYS: Related via the BEP_ACCOUNT_ID column, this join connects the user profile to the specific bank account or payment processor key details.
• Self-referencing Foreign Keys: The table references itself for columns SYS_CC_PROFILE_CODE, ONLINE_AUTH_TRANS_CONFIG_ID, SETTLEMENT_TRANS_CONFIG_ID, and QUERY_TRANS_CONFIG_ID. This indicates these columns likely store codes or IDs that point to other records within the same table, representing system-level profile templates and shared transaction configuration records that user profiles inherit or utilize.

These relationships underscore the table's function as a central hub linking user-specific payment instructions to shared system configurations and external payment processing accounts.