Results for “eft_user_number”
22 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
AP_BANK_BRANCHES is the Oracle Payables (AP) master table that stores bank and bank branch information used throughout Oracle E-Business Suite. In releases 12.1.1 and 12.2.2, this table acts as the primary repository of bank institution and branch records that support payment processing, EFT transmissions, bank account definitions, and cash management activities. Each row represents a distinct bank entity or branch, capturing its identity, address, contact information, EFT routing details, and associations to payment programs and trading partners.
From a Data Vault modeling perspective, the metadata's heuristic classification places AP_BANK_BRANCHES as a hub. This suggests the table primarily serves as a durable catalog of business keys (bank/branch identities), with descriptive attributes that could be modeled as related satellites. The table is owned by the AP schema and is marked VALID, containing 88 documented columns.
Key Information Stored
The surrogate primary key is BANK_BRANCH_ID, defined by the index AP_BANK_BRANCHES_PK. Two unique indexes represent business-key candidates: AP_BANK_BRANCHES_U1 (BANK_BRANCH_ID) and AP_BANK_BRANCHES_U2 (BANK_NAME, BANK_BRANCH_NAME), the latter enforcing that a given branch name is unique within its bank.
- BANK_BRANCH_ID — Surrogate primary key identifying each branch record.
- BANK_NAME — Institution name; part of the U2 business key.
- BANK_BRANCH_NAME — Branch identifier; part of the U2 business key.
- BANK_NUM / BANK_NUMBER — Bank routing or institution numbers.
- DESCRIPTION — Free-text description of the bank or branch.
- ADDRESS_LINE1–4, CITY, STATE, PROVINCE, ZIP, COUNTRY, COUNTY — Mailing and physical address fields.
- EFT_SWIFT_CODE, EFT_USER_NUMBER — EFT routing identifiers for electronic payment transmission.
- INSTITUTION_TYPE, BANK_BRANCH_TYPE — Classification of the institution and branch.
- CLEARING_HOUSE_ID — Self-referencing link to a clearing house branch.
- TRANSMISSION_PROGRAM_ID, PRINTING_PROGRAM_ID — References to AP_PAYMENT_PROGRAMS used in payment formatting.
- TP_HEADER_ID / ECE_TP_LOCATION_CODE — Trading partner references via ECE_TP_HEADERS.
- PAYROLL_BANK_ACCOUNT_ID — Link to PAY_EXTERNAL_ACCOUNTS for payroll.
- ACTIVE_DATE, END_DATE — Date-bounded validity of the branch record.
Common Use Cases and Queries
AP_BANK_BRANCHES is frequently joined to AP_BANK_ACCOUNTS_ALL to resolve the branch for a given internal or supplier bank account. A typical reporting query lists active branches with their associated accounts:
- Resolving the branch and bank name for a payment or EFT transmission.
- Reporting all active branches filtered by ACTIVE_DATE and END_DATE for a given institution.
- Retrieving EFT routing information (EFT_SWIFT_CODE, BANK_NUM) for electronic payment setup.
- Auditing branch-to-program assignments for payment formatting and printing.
Sample pattern: SELECT b.bank_branch_id, b.bank_name, b.bank_branch_name FROM ap_bank_branches b WHERE b.end_date IS NULL. Joining to AP_BANK_ACCOUNTS_ALL on BANK_BRANCH_ID yields the account-to-branch mapping used in payment batch reporting.
Related Objects
The table participates in a broad network of foreign key relationships:
- AP_BANK_ACCOUNTS_ALL — references BANK_BRANCH_ID; the primary consumer for account-to-branch mapping.
- AP_BANK_CHARGES — references TRANSFERRING_BANK_BRANCH_ID and RECEIVING_BANK_BRANCH_ID.
- AP_BANK_TRANSMISSIONS and AP_TRANSMISSIONS_SETUP — reference BANK_BRANCH_ID for payment transmission.
- AP_BANK_BRANCHES (self) — CLEARING_HOUSE_ID links to another branch acting as clearing house.
- AP_PAYMENT_PROGRAMS — referenced via TRANSMISSION_PROGRAM_ID and PRINTING_PROGRAM_ID.
- ECE_TP_HEADERS — referenced via TP_HEADER_ID for trading partner integration.
- AR_CASH_RECEIPTS_ALL and AR_BATCHES_ALL — legacy remittance/customer/issuer bank branch references.
- POS_SUP_BANK_ACCOUNT_REQUESTS and POS_ACCT_ADDR_REL — Procurement references via BANK_BRANCH_ID.
-
Payables system defaults and parameters
-
Payables system defaults and parameters
-
Not implemented in this database·Explore AP module →
-
View: APFV_BANK_ACCOUNTS 12.2.2
Business view
Not implemented in this database·Explore AP module →
-
Not implemented in this database·Explore AP module →
-
View: APBV_BANK_ACCOUNTS 12.2.2
Business view
Not implemented in this database·Explore AP module →
-
View: APFV_BANK_ACCOUNTS 12.1.1
Business view
Not implemented in this database·Explore AP module →
-
View: APBV_BANK_ACCOUNTS 12.1.1
Business view
Not implemented in this database·Explore AP module →
-
View: APBV_BANK_BRANCHES 12.1.1
Business view
Not implemented in this database·Explore AP module →
-
View: APFV_BANK_BRANCHES 12.1.1
Business view
Not implemented in this database·Explore AP module →
-
MULTI-ORG MRC view
Not implemented in this database·Explore AP module →
-
View: APBV_BANK_BRANCHES 12.2.2
Business view
Not implemented in this database·Explore AP module →
-
View: AP_XML_BATCHLEVEL2_V 12.1.1
Not implemented in this database·Explore AP module →
-
View: APFV_BANK_BRANCHES 12.2.2
Business view
Not implemented in this database·Explore AP module →
-
SINGLE-ORG view
Not implemented in this database·Explore AP module →
-
SINGLE-ORG view
Not implemented in this database·Explore AP module →
-
MULTI-ORG MRC view
Not implemented in this database·Explore AP module →
-
View: AP_XML_BATCHLEVEL2_V 12.2.2
Not implemented in this database·Explore AP module →