Search Results iby_acct_pmt_profiles_b




Overview
Explore in AI Chat

Overview

The table IBY_ACCT_PMT_PROFILES_B is a core data object within the Oracle E-Business Suite Payments (IBY) module, serving as the foundation for account-specific payment processing configurations. It stores the account-related information required to complete the specification for handling payment instructions. Each record in this table is based on a corresponding entry in the IBY_SYS_PMT_PROFILES_B table, which defines system-level payment profile settings. The combination of these two tables creates a fully defined payment profile, linking a specific bank account, transmission method, and other financial details to a system-level payment process. This table is critical for the execution of payment batches, as it determines the exact funding account and disbursement mechanism for generated payments.

Key Information Stored

While the specific column list is not detailed in the provided metadata, the foreign key relationships and description indicate the table's primary purpose is to associate a payment profile with concrete banking and transmission details. The key column is PAYMENT_PROFILE_ID, which serves as the primary key and uniquely identifies each account-level profile. Based on the foreign key constraints, other crucial columns likely include SYSTEM_PROFILE_CODE (linking to the system profile), BEP_ACCOUNT_ID (identifying the specific bank account within a payment system), and TRANSMIT_CONFIGURATION_ID (defining the electronic transmission setup, such as FTP details). The table essentially operationalizes a generic system payment profile by attaching the specific bank account from which funds will be disbursed.

Common Use Cases and Queries

This table is central to payment execution and troubleshooting. A common use case is identifying the bank account and transmission method used for a specific payment instruction or batch. System administrators and payment processors query this table to validate profile setups or diagnose payment failures. For instance, to find the complete setup for a payment profile referenced on an invoice, one would join this table to the system profile and bank account tables.

  • Profile Lookup: SELECT * FROM iby_acct_pmt_profiles_b WHERE payment_profile_id = :1;
  • Join to System Profile: SELECT acc.*, sys.* FROM iby_acct_pmt_profiles_b acc, iby_sys_pmt_profiles_b sys WHERE acc.system_profile_code = sys.system_profile_code;
  • Link to Payments: SELECT p.payment_id, prof.* FROM iby_payments_all p, iby_acct_pmt_profiles_b prof WHERE p.payment_profile_id = prof.payment_profile_id;

Related Objects

The IBY_ACCT_PMT_PROFILES_B table sits at a critical junction, referenced by numerous transactional and setup tables within the Payments module, as evidenced by its extensive foreign key relationships.

  • Parent/Dependency Tables:
    • IBY_SYS_PMT_PROFILES_B: Linked via SYSTEM_PROFILE_CODE. Provides the system-level profile definition.
    • IBY_BEPKEYS: Linked via BEP_ACCOUNT_ID. Identifies the specific bank account.
    • IBY_TRANSMIT_CONFIGS_B: Linked via TRANSMIT_CONFIGURATION_ID. Defines the electronic file transmission parameters.
  • Child/Referencing Tables: