Results for “routing_number”

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

Overview

AR_BANK_DIRECTORY is a Receivables (AR) module table in the Oracle E-Business Suite that stores bank routing and address information used by the bank directory feature. In EBS 12.1.1 and 12.2.2 it functions as a reference repository of banks identified by their routing number, providing the descriptive attributes — name, address, phone, and postal details — that supplement the routing number itself. It is the table behind the "Banks" lookup in Receivables and is queried by the bank directory forms, concurrent programs, and any process that needs to resolve a routing number to a human-readable bank record.

The heuristic Data Vault classification mined from the foreign key structure is standalone, meaning no parent/child FK relationships were detected. As a modeling suggestion, this makes AR_BANK_DIRECTORY a natural candidate for a hub-style reference table: the business key (routing number) is stable, self-contained, and not dependent on any other entity in the mined relationship graph. Its descriptive columns (name, address, phone) could alternatively be treated as satellite attributes keyed by that hub.

Key Information Stored

The documented physical schema contains 18 columns. The most significant are:

• ROUTING_NUMBER — the primary business identifier for the bank. It forms both the primary key index (AR_BANK_DIRECTORY_PK) and the unique business-key index (AR_BANK_DIRECTORY_U1). In the Data Vault sense this is the hub key.
• BANK_NAME — the legal or commonly used name of the financial institution.
• ADDRESS, CITY, STATE, POSTAL_CODE, POSTAL_CODE_EXTENSION, COUNTRY — the mailing/location address of the bank, used for correspondence and check printing.
• PHONE_COUNTRY_CODE, PHONE_AREA_CODE, PHONE_NUMBER — the bank's contact telephone number split into its component parts.
• NEW_ROUTING_NUMBER, CHANGE_DATE — capture a routing-number change event, allowing historical correlation between an old and a new routing number.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — standard EBS WHO columns providing audit traceability.

Note that the surrogate key and the business-key candidate are the same physical column, ROUTING_NUMBER; there is no separate technical ID column in the documented schema.

Common Use Cases and Queries

The primary use case is resolving a routing number to a bank name for payment and remittance processing. A typical query pattern is:

• SELECT bank_name, city, state FROM ar_bank_directory WHERE routing_number = :p_routing_number;
• SELECT routing_number, bank_name FROM ar_bank_directory WHERE bank_name LIKE :pattern ORDER BY bank_name;
• SELECT routing_number, new_routing_number, change_date FROM ar_bank_directory WHERE new_routing_number IS NOT NULL; — to audit banks whose routing numbers have been reassigned.

Reporting scenarios include bank master listings, address validation for check stock, and reconciliation of payment records against the bank directory. Because the table is small and reference-oriented, it is well suited to being cached in a lookup or extracted into a reporting aggregate. Note that only the ROUTING_NUMBER, NEW_ROUTING_NUMBER, and CHANGE_DATE columns are typically joined against external payment data; the address and phone columns are for display and correspondence.

Related Objects

The mined metadata records no outgoing foreign keys, so the object is standalone. Nonetheless, in practice the following objects reference or depend on routing numbers established by this table:

• AR_BANK_ACCOUNTS_ALL / AR_BANK_ACCOUNTS — the bank account records that reference the directory by routing number.
• IBY_BANKACCT_BANKS — the Payments (IBY) bank account repository that resolves external bank accounts against routing numbers.
• AR_CASH_RECEIPTS / AP_CHECKS — payment records that carry the bank routing number for disbursement.
• AP_BANK_ACCOUNTS / CE_BANK_ACCOUNTS — Accounts Payable and Cash Management bank account definitions that reference the directory.

Because no FK constraints exist in AR_BANK_DIRECTORY itself, joins to these objects are performed on ROUTING_NUMBER as a logical (not enforced) key, and integrity depends on application-level validation at entry time.