Search Results iby_bep_acct_opt_name_b




Overview
Explore in AI Chat

Overview

The table IBY_BEP_ACCT_OPT_NAME_B is a core reference table within the Oracle Payments (IBY) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It functions as the base table for defining and storing the valid account options available for configuration with specific Business Event Processors (BEPs). A BEP is a payment system adapter that handles the formatting and transmission of payment instructions to external banking or payment networks. This table establishes the master list of configurable account-level parameters (e.g., payment method, currency, account type) that can be assigned to a given BEP, forming a critical link between payment system capabilities and the internal financial account setup.

Key Information Stored

The table's structure is defined by two primary key columns, reflecting its role in mapping options to processors. The column ACCOUNT_OPTION_CODE is the unique identifier for a specific configurable account parameter. The column BEPID stores the unique identifier for the Business Event Processor, as defined in the IBY_BEPINFO table. The combination of these two columns is enforced as a unique key (IBY_BEP_ACCT_OPT_NAME_B_BA_U1), ensuring that a given account option is not duplicated for the same BEP. The standalone primary key (IBY_BEP_ACCT_OPT_NAME_B_PK) on ACCOUNT_OPTION_CODE and BEPID further enforces this critical relationship. The table itself holds the structural definition, while translated names and descriptions are stored in the related IBY_BEP_ACCT_OPT_NAME_TL table.

Common Use Cases and Queries

This table is primarily accessed during the setup and administration of payment systems. Common scenarios include validating which account attributes are available for a selected payment bank or system, and generating lists of configurable options for user interfaces. A typical diagnostic or setup query would join to the BEP info and translation tables. For example, to list all account options for a specific BEP:

  • SELECT bopt.ACCOUNT_OPTION_CODE, tl.NAME FROM IBY_BEP_ACCT_OPT_NAME_B bopt JOIN IBY_BEP_ACCT_OPT_NAME_TL tl ON bopt.ACCOUNT_OPTION_CODE = tl.ACCOUNT_OPTION_CODE AND bopt.BEPID = tl.BEPID JOIN IBY_BEPINFO bep ON bopt.BEPID = bep.BEPID WHERE bep.BEP_CODE = '&BEP_CODE' AND tl.LANGUAGE = USERENV('LANG');

Another critical use case is data validation during the creation of payment instructions, where the system verifies that the account details provided are compatible with the chosen BEP's supported options.

Related Objects

The table maintains defined foreign key relationships with other core Payments tables, as documented in the ETRM metadata.

  • IBY_BEPINFO: The table references IBY_BEPINFO via the BEPID column. This ensures every account option record is associated with a valid, defined Business Event Processor.
  • IBY_BEP_ACCT_OPT_NAME_TL: This is the translation table that references IBY_BEP_ACCT_OPT_NAME_B. It holds the translated name and description for each account option code, joined on the composite key of ACCOUNT_OPTION_CODE and BEPID. This supports multilingual implementations of EBS.