Results for “iby_bep_acct_opt_name_b”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IBY.IBY_BEP_ACCT_OPT_NAME_B is a Payments module table that defines the account option names available to a specific payment system. In Oracle EBS, a "BEP" (Banking and Payment System Entity Profile, resolved via IBY_BEPINFO) represents the configuration of a payment system connection, such as a bank integration or payment processor. This table links each BEP to a set of named account options—configurable fields that further qualify how a payment is sourced or applied, for example an internal bank account reference, a batch-specific option, or a secured parameter.

Because the table holds descriptive and behavioral attributes keyed to a parent BEP entity, the ETRM heuristic classifies it as satellite-leaning in a Data Vault model. This is a modeling suggestion only: the table behaves as a descriptive satellite hanging off the IBY_BEPINFO hub, with BEPID and ACCOUNT_OPTION_CODE forming the natural business key.

Key Information Stored

The table carries 13 documented columns. The most significant are:

• BEPID — Foreign key to IBY_BEPINFO; identifies the payment system entity profile to which the option belongs.
• ACCOUNT_OPTION_CODE — The short code identifying the account option. Together with BEPID, it forms the business key captured by unique index IBY_BEP_ACCT_OPT_NAME_B_BA_U1.
• ACCOUNT_OPTION_DATATYPE — Declares the expected data type of the option value, telling consumers how to interpret and validate the option at payment time.
• DISPLAY_ORDER — Controls the sequence in which options are presented in the Payments user interface.
• SECURED_FLAG — Indicates whether the option is treated as a secured/sensitive parameter, which affects masking and access control.
• UNIQUE_PER_BATCH_FLAG — Signals whether the option value must be unique within a payment batch, governing batch-level validation logic.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle Application Object Library (OAF/AOL) framework to detect concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard "WHO" audit columns populated by the EBS framework on every insert and update.
• ZD_EDITION_NAME — Editioning column supporting Oracle EBS 12.2 online patching, separating rows across editions of the application.

The physical surrogate keys are the unique indexes IBY_BEP_ACCT_OPT_NAME_B_BA_U1 (BEPID, ACCOUNT_OPTION_CODE, ZD_EDITION_NAME) and the primary key IBY_BEP_ACCT_OPT_NAME_B_PK. The _B suffix denotes this table stores base (language-independent) attributes, while the translatable text lives in IBY_BEP_ACCT_OPT_NAME_TL.

Common Use Cases and Queries

Typical reporting retrieves the options configured for a given payment system, often joined to the language table to surface the display name.

SELECT b.BEPID, b.ACCOUNT_OPTION_CODE,
       t.ACCOUNT_OPTION_NAME,
       b.ACCOUNT_OPTION_DATATYPE, b.DISPLAY_ORDER,
       b.SECURED_FLAG, b.UNIQUE_PER_BATCH_FLAG
  FROM IBY.IBY_BEP_ACCT_OPT_NAME_B  b,
       IBY.IBY_BEP_ACCT_OPT_NAME_TL t
 WHERE b.BEPID = :p_bepid
   AND b.ACCOUNT_OPTION_CODE = t.ACCOUNT_OPTION_CODE
   AND t.LANGUAGE = USERENV('LANG');

Common scenarios include auditing which BEPs expose secured options, verifying display ordering for UI customization, and diagnosing payment creation failures caused by type mismatches or non-unique batch values. Administrators may cross-reference this table before enabling a new payment system connection to confirm all required options are defined.

Related Objects

• IBY_BEPINFO — The parent BEP definition. Join on IBY_BEP_ACCT_OPT_NAME_B.BEPID = IBY_BEPINFO.BEPID.
• IBY_BEP_ACCT_OPT_NAME_TL — Translatable names/descriptions. Join on ACCOUNT_OPTION_CODE and BEPID.
• IBY_BEP_ACCT_OPTIONS — Stores the actual option values assigned to payments and payment batches for each BEP.
• IBY_PAY_SYSTEM_ACCT_OPTS — Links payment systems to their configured account options.
• IBY_PAYMENTS — Payment records whose account options are validated against the definitions held here.
• IBY_BEPINFO_ALL — Multi-org/secured view over the BEP header used in runtime queries.

Together these objects form the Payments configuration layer in the IBY schema, with IBY_BEP_ACCT_OPT_NAME_B serving as the metadata definition of account options and the _TL table supplying localized display text.