Results for “zip_code”

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

Overview

CEBV_BANK_BRANCHES is a business view owned by the APPS schema within the Cash Management (CE) product family of Oracle E-Business Suite. It exposes bank branch master data stored in the Cash Management bank model to reporting, integration, and query tools. The view carries a VALID status and is documented in the ETRM reference for both 12.1.1 and 12.2.2, indicating that its definition and column list are stable across these releases. Because it is defined as a simple projection over a single underlying view with a WITH READ ONLY clause, it is intended purely for read access; it cannot be used for DML against the underlying bank branch entities. Typical consumers include custom reports, Oracle Reports/BI Publisher data models, public APIs that need branch identifier and descriptive attributes, and third-party payment or treasury integrations that require bank and branch reference data such as routing numbers, SWIFT codes, and EDI identifiers.

Underlying Base Objects

Per the documented ETRM metadata, CEBV_BANK_BRANCHES is defined exclusively over one referenced base object: CE_BANK_BRANCHES_V, a view in the Cash Management schema. The wrapping view is therefore a thin, presentation-level projection. The SELECT statement references the base view with the alias BB and applies WITH READ ONLY. Notably, several columns in the outer view are not sourced from CE_BANK_BRANCHES_V at all but are emitted as typed NULL literals: TO_CHAR(NULL) for six text columns (including the alternate address lines and several contact-related fields), and TO_DATE(NULL) / TO_NUMBER(NULL) for creation/update audit columns. This design preserves a fixed column interface expected by downstream consumers while the physical source lacks those attributes, effectively padding the projection so the view remains compatible with a common bank/branch interface contract.

Key Columns

The view exposes the full bank and branch identification surface. Key columns include:

• BANK_BRANCH_ID — mapped from BB.BRANCH_PARTY_ID; the primary identifier for a branch record.
• BANK_NAME, ALTERNATE_BANK_NAME, BANK_NUMBER — bank legal and alternate names plus the bank number.
• BANK_BRANCH_NAME, ALTERNATE_BANK_BRANCH_NAME, BANK_BRANCH_NUMBER — branch descriptive and numbering attributes.
• BANK_BRANCH_TYPE, INSTITUTION_TYPE — classification of the branch and its financial institution.
• START_EFFECTIVE_DATE, END_EFFECTIVE_DATE — the validity window for the branch record.
• ADDRESS_LINE1 through ADDRESS_LINE4, CITY, COUNTY, STATE, ZIP_CODE, COUNTRY — geographic address detail.
• EFT_USER_NUMBER, EFT_SWIFT_CODE, EDI_ID_NUMBER — electronic payment and identification codes used for funds transfer and EDI.
• Nullable placeholder columns for alternate address lines and contact/phone/audit attributes, exposed as typed NULLs.

Common Use Cases and Queries

This view is commonly used to populate bank branch selection lists in payment setup, to feed SWIFT/EFT routing data into outbound payment files, and to reconcile branch master data across environments. A representative query retrieving active branches with their EFT identifiers is:

• SELECT bank_branch_id, bank_name, bank_branch_name, bank_branch_number, eft_swift_code, eft_user_number FROM cebv_bank_branches WHERE TRUNC(SYSDATE) BETWEEN start_effective_date AND NVL(end_effective_date, TRUNC(SYSDATE));
• SELECT bank_number, bank_branch_number, country, eft_swift_code FROM cebv_bank_branches WHERE eft_swift_code IS NOT NULL ORDER BY bank_number, bank_branch_number;
• Joining CEBV_BANK_BRANCHES to bank account or payment tables on BANK_BRANCH_ID to resolve branch names in payment reports.

Because the view is read only and defined over a single base view, queries are inexpensive relative to joins across multiple bank tables, making it suitable for high-volume reporting and integration extracts.