Results for “iby_default_bep”

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

Overview

IBY_DEFAULT_BEP is a table in the IBY (Payments) product schema of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. It stores the default payment system account and funds capture process profile assignments that the payment engine falls back on when normal routing rules fail to yield a result for a transaction. In practice, the table acts as a residual configuration layer: a transaction that cannot be matched to a specific routing rule is resolved against the rows defined here, allowing payment processing to complete rather than terminate with error.

Under a heuristic Data Vault classification derived from the foreign key structure, IBY_DEFAULT_BEP is best modeled as a link. It does not describe an independently identifiable business entity; instead it associates a Bill of Exchange / payment format definition (BEPID), a payee, a payment channel, and a backing account key, which is the characteristic signature of a link table connecting several hubs.

Key Information Stored

The table contains 14 documented columns. The most significant are:

• BEPID — Identifier of the payment format or Bill of Exchange definition; part of the primary key and a foreign key to IBY_BEPINFO.
• INSTRTYPE — Instrument type (for example, a specific payment instrument classification); the second component of the primary key.
• MPAYEEID — Payee identifier, referencing IBY_PAYEE; allows defaults to be scoped to a specific payee.
• BEP_ACCOUNT_ID — The account key used for the default, referencing IBY_BEPKEYS.
• PAYMENT_CHANNEL_CODE — The channel through which the payment flows, used to narrow default selection.
• FNDCPT_USER_PROFILE_CODE — The funds capture process profile, either the profile identifier or its defining code, controlling how the capture process behaves.
• SECURITY_GROUP_ID — Organizational security grouping, referencing FND_SECURITY_GROUPS.
• ZD_EDITION_NAME — Editioning column supporting online patching, introduced for the 12.2.x AD/TXK editioning architecture.
• Standard WHO/audit columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER.

The surrogate primary key is enforced by the unique constraint IBY_DEFAULT_BEP_UK, defined on (BEPID, INSTRTYPE). A second unique index, IBY_DEFAULT_BEP_U1, is defined on (BEPID, INSTRTYPE, MPAYEEID, PAYMENT_CHANNEL_CODE, ZD_EDITION_NAME); this composite is the strongest business-key candidate, since it captures the full set of attributes that uniquely qualify a default row in the editioning model.

Common Use Cases and Queries

The primary use case is diagnostics: when a transaction fails to route correctly, the default resolution path is inspected. A representative query joins the defaults to their parent format and payee:

• SELECT d.bepid, d.instrtype, d.mpayeeid, d.payment_channel_code, d.fndcpt_user_profile_code, b.bep_name FROM iby_default_bep d, iby_bepinfo b WHERE d.bepid = b.bepid AND d.mpayeeid = :payee_id
• Reporting on which channels and capture process profiles are in use as fallbacks, to identify configurations that mask missing routing rules.
• Validating uniqueness of (BEPID, INSTRTYPE) before inserting a new default, and auditing against IBY_DEFAULT_BEP_U1 in 12.2.x environments where editioning is active.
• Data migration and reconciliation scripts that compare defaults across instances using BEPID, INSTRTYPE, MPAYEEID, and PAYMENT_CHANNEL_CODE as the matching key.

Related Objects

The table's foreign keys establish the following principal relationships:

• IBY_BEPINFO — joined on IBY_DEFAULT_BEP.BEPID = IBY_BEPINFO.BEPID; the parent payment format definition.
• IBY_PAYEE — joined on IBY_DEFAULT_BEP.MPAYEEID = IBY_PAYEE.PAYEE_ID; scopes the default to a payee.
• IBY_BEPKEYS — joined on IBY_DEFAULT_BEP.BEP_ACCOUNT_ID = IBY_BEPKEYS.BEP_ACCOUNT_ID; supplies the backing account key for the default.
• FND_SECURITY_GROUPS — joined on IBY_DEFAULT_BEP.SECURITY_GROUP_ID; enforces organizational data security.

These dependents, together with the routing rule tables in the IBY schema, form the fallback chain consulted by the payment and funds capture processing engine.