Results for “iby_bep_acct_opt_vals”

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

Overview

IBY.IBY_BEP_ACCT_OPT_VALS is a Payments module configuration table that stores payment account option values associated with a Biller Payment (BEP) account. In Oracle EBS 12.1.1 and 12.2.2, this table supports the Payments workbench and payment-batch processing engine by defining the behavioral attributes and control settings that govern how funds captured against a given BEP key account are processed, disbursed, and formatted.

The table has a narrow role but is structurally significant: it acts as an attribute repository that qualifies a parent BEP account. The documented physical schema lists 11 columns, with a composite primary key IBY_BEP_ACCT_OPT_VALS_PK defined on (ACCOUNT_OPTION_CODE, BEP_ACCOUNT_ID). A second unique index, IBY_BEP_ACCT_OPT_VALS_AIAC_U1, is defined on (BEP_ACCOUNT_ID, ACCOUNT_OPTION_CODE) — effectively the same business key in reversed order. Because the FK relationship points outward only (to IBY_BEPKEYS), the heuristic Data Vault classification is satellite-leaning: this table is best modeled as a satellite carrying descriptive attributes keyed to the BEP account hub.

Key Information Stored

• BEP_ACCOUNT_ID — the foreign key to IBY_BEPKEYS; the parent identifier linking each option value to a specific BEP account. It is part of the composite PK and the leading column of the unique index.
• ACCOUNT_OPTION_CODE — the code identifying which configurable option (e.g., formatting, processing, or routing behavior) is being set. It forms the other half of the composite PK.
• ACCOUNT_OPTION_VALUE — the value assigned to the code; this is the payload column that applications and payment programs actually read.
• BEPID — the BEP identifier, correlating the record to the BEP registration within the Payments engine.
• VAL_SEC_SEGMENT_ID — a segment identifier used for validation or security-segment scoping of the option value.
• OBJECT_VERSION_NUMBER — the optimistic-locking column used by the OA Framework to detect concurrent updates.

The remaining documented columns are standard WHO audit attributes: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN. No surrogate single-column primary key is documented; identity is fully composite.

Common Use Cases and Queries

The dominant query pattern is lookup-by-account, since the business key BEP_ACCOUNT_ID is what users search on. A typical reporting query retrieves all configured options for one BEP account:

• SELECT account_option_code, account_option_value FROM iby_bep_acct_opt_vals WHERE bep_account_id = :bep_account_id;
• Joining to the parent to surface the account name: SELECT b.bep_account_id, v.account_option_code, v.account_option_value FROM iby_bepkeys b, iby_bep_acct_opt_vals v WHERE b.bep_account_id = v.bep_account_id;
• Audit/history queries filtering on last_update_date to find options changed after a specific date, useful during payment-issue troubleshooting.

Diagnostic scenarios include verifying that a mandatory option code is present, comparing option values across environments using a MINUS against a reference instance, and validating uniqueness of the (BEP_ACCOUNT_ID, ACCOUNT_OPTION_CODE) pair. Because the table is configurational and low-volume, it is also a frequent target in setup migration and clone-validation reports.

Related Objects

• IBY_BEPKEYS — the parent table referenced by the documented foreign key IBY_BEP_ACCT_OPT_VALS.BEP_ACCOUNT_ID → IBY_BEPKEYS. This is the primary join.
• IBY_BEP_ACCT — companion setup table providing account-level attributes that, together with option values, fully describe a BEP account.
• IBY_PAY_SERVICE_REQUESTS — payment service requests whose behavior is influenced by the configured option values.
• IBY_PAYMENTS / IBY_PAY_INSTRUCTIONS_ALL — transactional objects that consume BEP account and option configuration.
• OA Framework pages in the Payments workbench that read and write ACCOUNT_OPTION_VALUE entries for a selected BEP account.

Together these objects form the BEP account configuration cluster; IBY_BEP_ACCT_OPT_VALS is the attribute side, while IBY_BEPKEYS provides the identity anchor.