Search Results iby_fndcpt_sys_cc_pf_b




Overview
Explore in AI Chat

Overview

The table IBY_FNDCPT_SYS_CC_PF_B is a core configuration table within the Oracle Payments (IBY) module of Oracle E-Business Suite, versions 12.1.1 and 12.2.2. It functions as the master repository for defining system-level credit card payment processing profiles. These profiles are critical for orchestrating the technical communication and data exchange between Oracle Payments and external credit card processors or payment gateways. Each profile encapsulates a complete set of protocols, formats, and handlers required for settlement, inquiry, and notification operations, enabling a standardized and configurable interface for diverse payment service providers.

Key Information Stored

The table's primary key, SYS_CC_PROFILE_CODE, uniquely identifies each credit card processing profile. The essential data stored pertains to the linkage of a profile to specific technical components for different transaction flows. While the full column list is not detailed in the provided metadata, the foreign key relationships explicitly reveal the critical columns. These include SETTLEMENT_FORMAT_CODE, SETTLEMENT_TRANS_PRTCL_CODE, and SETTLEMENT_ACK_RDR_CODE, which define the data format, transmission protocol, and acknowledgment reader for settlement batches. Similarly, QUERY_FORMAT_CODE, QUERY_TRANS_PRTCL_CODE, and QUERY_ACK_RDR_CODE configure these components for transaction inquiry processes. The PAYER_NOTIFICATION_FORMAT column links to the format used for payer communications.

Common Use Cases and Queries

This table is primarily accessed during the setup and administration of credit card payment processing. Common operational scenarios include validating the configuration for a new payment gateway or troubleshooting transmission errors by verifying the assigned protocols and formats. A typical diagnostic query would join this table to its referenced lookup tables to list all configured profiles with their technical components:

  • SELECT pf.sys_cc_profile_code, f_sett.format_name AS settlement_format, tp_sett.protocol_name AS settlement_protocol FROM iby_fndcpt_sys_cc_pf_b pf, iby_formats_b f_sett, iby_transmit_protocols_b tp_sett WHERE pf.settlement_format_code = f_sett.format_code AND pf.settlement_trans_prtcl_code = tp_sett.protocol_code;

Reporting use cases focus on auditing payment system configurations to ensure compliance and consistency across different operating units or legal entities that may use distinct credit card processors.

Related Objects

The table IBY_FNDCPT_SYS_CC_PF_B has a defined dependency on several key lookup tables in the IBY schema, as documented by its foreign keys. These relationships are fundamental to its purpose of centralizing configuration:

  • IBY_FORMATS_B: Referenced three times for defining data formats.
    • Join Column: SETTLEMENT_FORMAT_CODE
    • Join Column: QUERY_FORMAT_CODE
    • Join Column: PAYER_NOTIFICATION_FORMAT
  • IBY_TRANSMIT_PROTOCOLS_B: Referenced twice for defining communication protocols.
    • Join Column: SETTLEMENT_TRANS_PRTCL_CODE
    • Join Column: QUERY_TRANS_PRTCL_CODE
  • IBY_ACK_READERS: Referenced twice for defining acknowledgment handlers.
    • Join Column: SETTLEMENT_ACK_RDR_CODE
    • Join Column: QUERY_ACK_RDR_CODE

This table is likely referenced by payment processing engine programs and setup UIs, positioning it as a central hub in the credit card payment infrastructure.