Search Results eft_swift_code




Overview
Explore in AI Chat

Overview

CE_BANK_BRANCHES_V is a Cash Management (CE) reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. As documented in the ETRM metadata, the view "stores bank branch information" and exposes a denormalized, query-ready projection of bank and bank branch data held in the Oracle Trading Community Architecture (TCA) model. Because banks and their branches are modeled in EBS 12.x as TCA parties, party relationships, organization profiles, and code assignments rather than as a single flat table, this view spares report developers and integrators from reconstructing that multi-table join logic manually.

The view returns one row per active bank branch, supplementing branch identity and address details with the associated bank's name, number, and home country. It serves as a stable read-only interface for cash management reporting, bank directory listings, payment-file generation, and third-party integration extracts. It carries status VALID in the ETRM catalog and is classified under the CE - Cash Management product.

Underlying Base Objects

The documented base objects referenced by CE_BANK_BRANCHES_V are all TCA synonyms: HZ_CODE_ASSIGNMENTS, HZ_CONTACT_POINTS, HZ_ORGANIZATION_PROFILES, HZ_PARTIES, and HZ_RELATIONSHIPS. The view joins these objects twice over, once for the bank and once for the branch:

  • HZ_ORGANIZATION_PROFILES — aliased as BANKORGPROFILE for the bank and BRANCHORGPROFILE for the branch; supplies organization names, phonetic names, known-as names, bank/branch numbers, and home country.
  • HZ_PARTIES — aliased as BRANCHPARTY; supplies the branch party identifier, party name, address lines, city, state, province, postal code, country, and description.
  • HZ_CODE_ASSIGNMENTS — used for bank institution type (BANKCA), branch type (BRANCHTYPECA), and branch status/dates (BRANCHCA).
  • HZ_RELATIONSHIPS — aliased as BRREL; links the branch party to its parent bank party.
  • HZ_CONTACT_POINTS — used for EFT/SWIFT details (BRANCHCP) and EDI identifiers (EDICP).

Filtering restricts results to active bank institution types ('BANK', 'CLEARINGHOUSE'), organizations, and currently effective organization profiles, so the view presents only live branch records.

Key Columns

Common Use Cases and Queries

Typical uses include bank directory reports, payment instruction validation, and integration extracts feeding treasury or banking systems.

  • List all branches for a given bank: SELECT bank_branch_name, branch_number, city, country FROM ce_bank_branches_v WHERE bank_party_id = :p_bank_party_id;
  • Retrieve SWIFT details for a payment file: SELECT bank_branch_name, eft_swift_code FROM ce_bank_branches_v WHERE branch_party_id = :p_branch_party_id;
  • Produce a bank/branch directory: SELECT bank_name, bank_number, bank_branch_name, branch_number, address_line1, city, country FROM ce_bank_branches_v ORDER BY bank_name, bank_branch_name;

Because the view is read-only and defined over TCA synonyms, it should be used for query and reporting purposes only; DML against it is not supported.