Search Results iby_fndcpt_user_eft_pf_b




Overview
Explore in AI Chat

Overview

The IBY_FNDCPT_USER_EFT_PF_B table is a core repository for user-defined Electronic Funds Transfer (EFT) profile configurations within Oracle E-Business Suite Payments (IBY). It stores the master definitions for payment instruction formats and transmission setups that are customized by an implementation, as opposed to seeded system profiles. This table is fundamental to the payment execution process, enabling organizations to define specific parameters for verifying, transferring funds, and querying transactions with their banking partners. Its role is critical in the payment flow, linking payment instructions to the appropriate banking infrastructure and communication protocols.

Key Information Stored

The table's primary key is the USER_EFT_PROFILE_CODE, a unique identifier for each custom EFT profile. Key foreign key columns define the profile's operational behavior by linking to other critical setup entities. The SYS_EFT_PROFILE_CODE links to a base system profile. The BEP_ACCOUNT_ID references the IBY_BEPKEYS table to identify the specific Bank Enterprise Partner (BEP) account used for transactions. Crucially, the table stores separate configuration IDs for different transaction types: VERIFY_TRANS_CONFIG_ID for payment verification, FUNDS_XFER_TRANS_CONFIG_ID for the actual funds transfer, and QUERY_TRANS_CONFIG_ID for transaction status inquiries. These IDs point to detailed transmission setups governing communication protocols and data formats.

Common Use Cases and Queries

This table is primarily accessed during payment process submission and for administrative reporting on payment configurations. A common operational query involves fetching the complete setup for a specific user-defined profile to validate its configuration before launching a payment batch. For troubleshooting, one might join this table to transaction history to identify which profile was used for a problematic payment. Administrators often run reports to audit all custom EFT profiles, their associated BEP accounts, and linked configurations to ensure setup consistency and completeness across the payment system.

  • Retrieve a full profile definition: SELECT * FROM iby.iby_fndcpt_user_eft_pf_b WHERE user_eft_profile_code = '&PROFILE_CODE';
  • List all custom profiles with their linked BEP account: SELECT pf.user_eft_profile_code, k.bep_account_name FROM iby.iby_fndcpt_user_eft_pf_b pf, iby.iby_bepkeys k WHERE pf.bep_account_id = k.bep_account_id(+);

Related Objects

The IBY_FNDCPT_USER_EFT_PF_B table maintains defined relationships with several other key Payments tables, primarily through foreign key constraints. The most significant relationship is with the IBY_BEPKEYS table via the BEP_ACCOUNT_ID column, linking the profile to a specific bank account setup. Furthermore, the table references other configuration entities through the VERIFY_TRANS_CONFIG_ID, FUNDS_XFER_TRANS_CONFIG_ID, and QUERY_TRANS_CONFIG_ID columns, though the specific target tables for these IDs are not fully detailed in the provided metadata. The table also has a self-referencing relationship through the SYS_EFT_PROFILE_CODE, likely connecting user-defined profiles to their base system profile templates.

  • IBY_BEPKEYS: Joined via IBY_FNDCPT_USER_EFT_PF_B.BEP_ACCOUNT_ID = IBY_BEPKEYS.BEP_ACCOUNT_ID.
  • Referenced Configuration Tables: Joined via the ID columns for verification, funds transfer, and query transaction configurations.