Search Results iby_fndcpt_sys_dc_pf_b




Overview
Explore in AI Chat

Overview

The table IBY_FNDCPT_SYS_DC_PF_B is a core data object within the Oracle Payments (IBY) module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It functions as the base table for storing system-defined direct debit profile configurations. These profiles are critical for automating and standardizing the processing of direct debit transactions, which involve the collection of funds from a payer's bank account. The table defines the operational rules, communication protocols, and document formats required for electronic interactions between the EBS system and external financial institutions or payment networks. Its role is to provide a centralized, system-level repository for the technical and process parameters that govern the entire lifecycle of a direct debit payment instruction.

Key Information Stored

The table's primary key, SYS_DC_PROFILE_CODE, uniquely identifies each system-defined direct debit profile. The stored data encompasses the complete technical setup for payment processing. Key columns include PAYMENT_SYSTEM_ID, which links to the Business Event Processor (BEP) in table IBY_BEPINFO, defining the processing engine. The table extensively stores format and protocol codes for different transaction phases, referencing the IBY_FORMATS_B and IBY_TRANSMIT_PROTOCOLS_B tables. These include SETTLEMENT_FORMAT_CODE, SETTLEMENT_TRANS_PRTCL_CODE, QUERY_FORMAT_CODE, QUERY_TRANS_PRTCL_CODE, ONLINE_DEB_TRANS_PRTCL_CODE, and PAYER_NOTIFICATION_FORMAT. Additional columns like SETTLEMENT_ACK_RDR_CODE, QUERY_ACK_RDR_CODE, and ONLINE_DEB_ACK_RDR_CODE manage the acknowledgment reader processes for settlement, query, and online debit operations, respectively.

Common Use Cases and Queries

This table is primarily referenced during the setup and execution of direct debit payment processes. Common administrative use cases include auditing the configuration of active direct debit profiles or troubleshooting transmission failures by verifying protocol and format assignments. A typical query might join this table with related lookup tables to generate a comprehensive profile report. For example:

  • To list all system direct debit profiles with their associated BEP and settlement format: SELECT pf.sys_dc_profile_code, pf.payment_system_id, bep.bep_name, fmt.format_name AS settlement_format FROM iby_fndcpt_sys_dc_pf_b pf, iby_bepinfo bep, iby_formats_b fmt WHERE pf.payment_system_id = bep.payment_system_id AND pf.settlement_format_code = fmt.format_code(+);
  • To identify profiles using a specific transmission protocol for queries: SELECT sys_dc_profile_code FROM iby_fndcpt_sys_dc_pf_b WHERE query_trans_prtcl_code = '&PROTOCOL_CODE';

Direct application user interaction is minimal, as the table is maintained through dedicated Oracle Payments administration interfaces.

Related Objects

The IBY_FNDCPT_SYS_DC_PF_B table is central to the Payments schema, with defined relationships to several key tables. As per the provided metadata, its primary foreign key relationships are:

  • IBY_BEPINFO: Links via PAYMENT_SYSTEM_ID to define the Business Event Processor.
  • IBY_FORMATS_B: Linked for multiple format codes (PAYER_NOTIFICATION_FORMAT, SETTLEMENT_FORMAT_CODE, QUERY_FORMAT_CODE).
  • IBY_TRANSMIT_PROTOCOLS_B: Linked for transmission protocol codes (SETTLEMENT_TRANS_PRTCL_CODE, QUERY_TRANS_PRTCL_CODE, ONLINE_DEB_TRANS_PRTCL_CODE).
  • Self-Reference: Columns like QUERY_ACK_RDR_CODE and SETTLEMENT_ACK_RDR_CODE appear to reference the table itself, likely pointing to other profile codes that define acknowledgment reader processes, indicating a hierarchical or component-based profile structure.

This network of relationships underscores the table's role as a configuration hub, integrating processor, format, and protocol definitions into a single executable direct debit profile.