Search Results iby_bep_acct_opt_vals_pk




Overview
Explore in AI Chat

Overview

The table IBY_BEP_ACCT_OPT_VALS is a core data object within the Oracle E-Business Suite Payments (IBY) module, present in both releases 12.1.1 and 12.2.2. It functions as a junction table that stores specific configuration values for bank account options. Its primary role is to link bank account details, managed as Business Entity Process (BEP) accounts, with configurable account-level options. This table is essential for defining and maintaining the precise operational parameters and attributes required for electronic payment processing and fund disbursements within the Oracle EBS financial architecture.

Key Information Stored

The table stores a combination of an account identifier and a specific option code, forming its primary key. The key columns are:

  • BEP_ACCOUNT_ID: A foreign key that uniquely identifies the bank account record in the related IBY_BEPKEYS table. This links the option value to a specific payment bank account.
  • ACCOUNT_OPTION_CODE: A code representing a specific configurable attribute or option for the linked bank account. The combination of this code and the BEP_ACCOUNT_ID must be unique, as enforced by the primary key constraint IBY_BEP_ACCT_OPT_VALS_PK.
While the provided metadata does not list value columns explicitly, such a structure typically includes a column (e.g., ACCOUNT_OPTION_VALUE) to hold the actual setting or data for the specified option code for the given account.

Common Use Cases and Queries

This table is primarily accessed for configuration management and troubleshooting during payment setup. A common use case is querying all configured options for a specific bank account to verify setup completeness or to audit parameters. For example, to retrieve all option codes and their values for a known BEP account ID, a technical consultant might use: 

SELECT account_option_code, account_option_value
FROM iby.iby_bep_acct_opt_vals
WHERE bep_account_id = <account_id>
ORDER BY account_option_code;
Another critical scenario involves validating the integrity of account setup by joining with the parent IBY_BEPKEYS table to list options for accounts of a certain type or belonging to a specific legal entity, ensuring configurations align with business requirements for payment processing.

Related Objects

The table has a documented, direct foreign key relationship with the IBY_BEPKEYS table, which is the master table for storing bank account information within the Payments module.

  • IBY_BEPKEYS: This table is referenced via the foreign key on the column IBY_BEP_ACCT_OPT_VALS.BEP_ACCOUNT_ID. The join condition is typically IBY_BEP_ACCT_OPT_VALS.BEP_ACCOUNT_ID = IBY_BEPKEYS.BEP_ACCOUNT_ID. IBY_BEPKEYS stores fundamental account details such as account number, bank, currency, and owner, making the relationship crucial for enriching option data with core account attributes.
This relationship is fundamental, indicating that every record in IBY_BEP_ACCT_OPT_VALS must correspond to a valid, existing bank account definition in IBY_BEPKEYS.