Search Results iby_fndcpt_user_dc_pf_b




Overview
Explore in AI Chat

Overview

The IBY_FNDCPT_USER_DC_PF_B table is a core data object within the Oracle E-Business Suite Payments (IBY) module, specifically for versions 12.1.1 and 12.2.2. It serves as the base table for storing user-defined Direct Debit (DD) profile configurations. A Direct Debit profile defines the operational and technical parameters required to initiate and process direct debit transactions through a specific Bank Enterprise Payment (BEP) service. This table is central to the setup and execution of automated payment collection, enabling organizations to configure unique processing rules and bank account linkages for different business scenarios.

Key Information Stored

The table's primary key is USER_DC_PROFILE_CODE, a unique identifier for each user-defined profile. Critical foreign key columns establish essential relationships to other payment setup entities. The BEP_ACCOUNT_ID links the profile to a specific bank account defined in the IBY_BEPKEYS table. Transaction configuration IDs—ONLINE_DEB_TRANS_CONFIG_ID, SETTLEMENT_TRANS_CONFIG_ID, and QUERY_TRANS_CONFIG_ID—define the technical setups for initiating debits, settlement processes, and transaction queries, respectively. The SYS_DC_PROFILE_CODE column may reference a system-defined profile template. Additional columns, inferred from standard EBS design patterns, typically store control attributes such as active status, start and end dates, and creation/modification audit information.

Common Use Cases and Queries

This table is primarily accessed during the implementation and ongoing administration of direct debit functionality. Common operational scenarios include troubleshooting payment initiation failures by verifying profile configurations or generating a list of active profiles for audit purposes. A typical reporting query would join this table to its descriptive translation table (IBY_FNDCPT_USER_DC_PF_TL) and bank account details. For example:

  • SELECT b.USER_DC_PROFILE_CODE, tl.NAME, k.BANK_ACCOUNT_NUM FROM IBY_FNDCPT_USER_DC_PF_B b, IBY_FNDCPT_USER_DC_PF_TL tl, IBY_BEPKEYS k WHERE b.USER_DC_PROFILE_CODE = tl.USER_DC_PROFILE_CODE AND b.BEP_ACCOUNT_ID = k.BEP_ACCOUNT_ID AND b.END_DATE IS NULL;

Direct data manipulation (DML) on this table is strongly discouraged; configurations should be created and maintained exclusively through the Oracle Payments Manager (OPM) user interface or dedicated public APIs to maintain data integrity.

Related Objects

The table maintains defined relationships with several other IBY objects, as documented in the ETRM metadata. The primary key is referenced by the translation table for multilingual support:

  • IBY_FNDCPT_USER_DC_PF_TL: References IBY_FNDCPT_USER_DC_PF_B.USER_DC_PROFILE_CODE to store translated names and descriptions for the profile.

This table references the following objects via foreign keys:

  • IBY_BEPKEYS: Via BEP_ACCOUNT_ID, linking the profile to a specific bank account setup.
  • IBY_FNDCPT_USER_DC_PF_B: Self-referencing foreign keys (for SYS_DC_PROFILE_CODE, ONLINE_DEB_TRANS_CONFIG_ID, SETTLEMENT_TRANS_CONFIG_ID, QUERY_TRANS_CONFIG_ID) indicate relationships to other rows within the same table, typically for inheriting settings from system-defined templates or other configuration sets.