Results for “branch_id”

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

Overview

IBY_TEMP_EXT_BANK_ACCTS is a transient staging table in the Oracle Payments (IBY) module of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It holds interim bank account and bank branch records for external payees that are being created, validated, or migrated into the Payments schema before they are committed to the permanent IBY_EXT_BANK_ACCOUNTS table. It is populated during supplier banking setup, payment batch preparation, and bulk data conversion routines, and it carries the full transactional context of the creator — request ID, program ID, program application ID, and the standard WHO columns.

The documented schema exposes 73 columns and a single-column primary key, IBY_TEMP_EXT_BANK_ACCTS_PK on TEMP_EXT_BANK_ACCT_ID. The metadata supplies no Data Vault classification; heuristically the table behaves as a staging satellite (or a link table where it stitches together the external bank account, branch, and payee relationships) rather than a durable hub, and it is best modeled as transient landing data that is periodically purged or promoted. Its short-lived nature means it should not be treated as an authoritative source in reporting.

Key Information Stored

The surrogate primary key TEMP_EXT_BANK_ACCT_ID uniquely identifies each staging row and is mirrored by the unique index IBY_TEMP_EXT_BANK_ACCTS_U1, the principal business-key candidate. Foreign-key columns tie each row to its permanent parent: EXT_BANK_ACCOUNT_ID references IBY_EXT_BANK_ACCOUNTS, BRANCH_ID references AMS_DLG_BRANCHES_B, and EXT_PAYEE_ID references IBY_EXTERNAL_PAYEES_ALL. Banking detail is carried in BANK_NAME, BANK_NUMBER, BANK_INSTITUTION_TYPE, BRANCH_NAME, BRANCH_NUMBER, BIC, and IBAN, while the account itself is described by BANK_ACCOUNT_NAME, BANK_ACCOUNT_NUM, BANK_ACCOUNT_TYPE, ACCOUNT_SUFFIX, CHECK_DIGITS, and CURRENCY_CODE. Payee contact data appears in CONTACT_NAME, CONTACT_PHONE, CONTACT_FAX, and CONTACT_EMAIL. Lifecycle columns include STATUS, START_DATE, END_DATE, and the WHO audit set (LAST_UPDATE_DATE, CREATED_BY, and so on).

Common Use Cases and Queries

Typical uses include auditing in-flight payee bank data, tracing a failed payment setup back to its staging row, and verifying that records were promoted to the permanent table. A reconciliation pattern compares staging rows to their permanent counterparts:

• SELECT t.temp_ext_bank_acct_id, t.bank_account_num, t.status FROM iby.iby_temp_ext_bank_accts t WHERE t.ext_payee_id = :payee_id;
• SELECT t.* FROM iby.iby_temp_ext_bank_accts t WHERE t.ext_bank_account_id IS NULL; — rows not yet matched to a permanent account.
• SELECT t.* FROM iby.iby_temp_ext_bank_accts t WHERE t.creation_date > SYSDATE - 7; — recently staged records for monitoring or purge.
• SELECT t.request_id, COUNT(*) FROM iby.iby_temp_ext_bank_accts t GROUP BY t.request_id; — volume by concurrent program invocation.

Related Objects

Relationships center on the three documented foreign keys and the permanent Payments entities they support:

• IBY_EXT_BANK_ACCOUNTS — joined on EXT_BANK_ACCOUNT_ID; the durable target of promotion.
• IBY_EXTERNAL_PAYEES_ALL — joined on EXT_PAYEE_ID; the supplier/payee owner.
• AMS_DLG_BRANCHES_B — joined on BRANCH_ID; bank branch definition.
• IBY_EXT_BANK_ACCT_USES_ALL — account usage by payment purpose.
• IBY_PAYEE_ACCT_SITES / IBY_ACCT_SITES — settlement account hierarchy.
• Payments concurrent programs and the IBY payment APIs that populate and consume this staging table during setup and payment processing.