Search Results bank_institution_type




Overview
Explore in AI Chat

Overview

CE_BANKS_V is a Cash Management (CE) view owned by the APPS schema that exposes the master list of banks registered in Oracle E-Business Suite. It consolidates bank identification, address, and classification data sourced from the Trading Community Architecture (TCA) model into a single reportable structure. Rather than storing data itself, the view projects columns from the HZ_PARTIES, HZ_ORGANIZATION_PROFILES, HZ_CODE_ASSIGNMENTS, HZ_PARTY_SITES, and HZ_LOCATIONS entities. Its principal purpose is to provide a stable, denormalized interface for bank selection lists, payment instruction lookups, cash management reporting, and integrations that need to resolve a bank party and its institution type. Because it is named with a _V suffix, it is intended for query and read-only integration consumption.

Underlying Base Objects

The view joins five TCA base objects through APPS synonyms. HZ_PARTIES supplies the core party record and is restricted to organizations with an active status. HZ_ORGANIZATION_PROFILES contributes the bank or branch number, home country, and the effective-dated profile row filtered with SYSDATE. HZ_CODE_ASSIGNMENTS resolves the bank classification and drives the BANK_INSTITUTION_TYPE column. HZ_PARTY_SITES and HZ_LOCATIONS are joined with outer (+) syntax to bring in the identifying address for the party. The classification join is constrained to CLASS_CATEGORY = 'BANK_INSTITUTION_TYPE' with CLASS_CODE values limited to 'BANK' and 'CLEARINGHOUSE', and OWNER_TABLE_NAME fixed to 'HZ_PARTIES'. This is the join that answers a search for "bank_institution_type" directly.

Key Columns

  • BANK_PARTY_ID — the HZ_PARTIES party identifier for the bank organization.
  • BANK_NAME / SHORT_BANK_NAME — the party name and the known-as short name.
  • BANK_NUMBER — the bank or branch number from the organization profile.
  • BANK_INSTITUTION_TYPE — mapped from HZ_CODE_ASSIGNMENTS.CLASS_CODE; the value is 'BANK' or 'CLEARINGHOUSE'.
  • START_DATE / END_DATE — active date range of the bank code assignment.
  • ADDRESS_LINE1–4, CITY, STATE, PROVINCE, ZIP, COUNTRY — bank address from HZ_PARTIES.
  • SITE_ADDRESS_LINE1, SITE, LOCATION_ID — identifying address retrieved from HZ_PARTY_SITES / HZ_LOCATIONS.
  • HOME_COUNTRY — home country from the organization profile.
  • ROW_ID — the ROWID of the underlying HZ_PARTIES row.

Common Use Cases and Queries

A frequent requirement is listing all banks of a given institution type, which is the exact scenario implied by the "bank_institution_type" search:

SELECT bank_party_id, bank_name, bank_number, bank_institution_type
FROM   ce_banks_v
WHERE  UPPER(bank_institution_type) = 'BANK'
ORDER BY bank_name;

A second scenario resolves a single bank by its party identifier or bank number for payment validation:

SELECT bank_name, bank_number, address_line1, city, country
FROM   ce_banks_v
WHERE  bank_number = :p_bank_number;

A third common pattern drives LOVs and reconciliation reports that need the active institution type filter:

SELECT bank_name, bank_institution_type, start_date, end_date
FROM   ce_banks_v
WHERE  bank_institution_type IN ('BANK','CLEARINGHOUSE');

Because the profile join is effective-dated against SYSDATE, queries return only currently valid bank records. Report authors should treat the view as read-only and avoid relying on its ROW_ID for updates.