Search Results site_county

Overview

APPS.CE_BANKS_V is a seed data view in the Oracle E-Business Suite Cash Management (CE) module. It presents a denormalized, reporting-friendly projection of bank records that are physically stored in the Oracle Trading Community Architecture (TCA) registry. Rather than maintaining bank master data in a standalone CE table, Oracle EBS 12.1.1 and 12.2.2 model banks, branches, and clearinghouses as TCA parties, party sites, and organization profiles. CE_BANKS_V joins those normalized TCA entities back together and exposes a flat, queryable structure that resembles the pre-R12 bank definition.

The view is registered in FND Design Data as CE.CE_BANKS_V with a status of VALID. ETRM explicitly classifies it as Internal / Oracle Internal Use Only, with the standard warning that Oracle does not support direct data access except through standard Oracle Applications programs. Consequently, the view should be treated as a read-only reporting and integration surface, not as a data entry point.

Underlying Base Objects

Per the documented view metadata, CE_BANKS_V is defined over the following referenced base objects, all accessed through public synonyms:

• HZ_PARTIES (SYNONYM) — supplies the bank party record, including BANK_PARTY_ID and the party-level name columns.
• HZ_ORGANIZATION_PROFILES (SYNONYM) — supplies organization-specific attributes such as bank number, institution type, and bank classification.
• HZ_PARTY_SITES (SYNONYM) — links the party to its physical locations and furnishes SITE_LOCATION_ID and the site-level address block.
• HZ_LOCATIONS (SYNONYM) — supplies the actual address elements (ADDRESS_LINE1 through ADDRESS_LINE4, CITY, STATE, PROVINCE, ZIP, COUNTRY) for both the bank and the site.
• HZ_CODE_ASSIGNMENTS (SYNONYM) — supplies classification and code assignment data used to identify institution type and related bank attributes.

The view therefore acts as a compatibility and convenience layer over the TCA data model, shielding report developers from the multi-table join logic required to reconstruct a bank.

Key Columns

The view exposes dual address blocks. The ADDRESS_LINE1–4, CITY, STATE, PROVINCE, ZIP, and COUNTRY columns represent the bank-level address, while the SITE_ADDRESS_LINE1–4, SITE_CITY, SITE_STATE, SITE_COUNTY, SITE_ZIP, SITE_COUNTRY, and SITE_PROVINCE columns represent the address of the specific party site. Users searching on "site_address_line1" are typically targeting the site-level address of the bank, branch, or clearinghouse location, which is where operational addresses such as remittance or branch locations are usually stored.

Other key columns include ROW_ID (ROWID), HOME_COUNTRY, BANK_PARTY_ID, BANK_NAME, BANK_NAME_ALT, SHORT_BANK_NAME, BANK_NUMBER, START_DATE, END_DATE, BANK_INSTITUTION_TYPE (BANK or CLEARINGHOUSE), DESCRIPTION, PK_ID, and SITE_LOCATION_ID. START_DATE and END_DATE support effective-dated reporting, while BANK_INSTITUTION_TYPE distinguishes banks from clearinghouses.

Common Use Cases and Queries

Typical usages include bank master extracts, reconciliation reports, payment format validation, and integration feeds into treasury or third-party systems. A representative query retrieving site addresses is:

• SELECT bank_name, bank_number, site_address_line1, site_city, site_state, site_zip, site_country FROM apps.ce_banks_v WHERE site_address_line1 IS NOT NULL;
• SELECT bank_name, bank_number, bank_institution_type FROM apps.ce_banks_v WHERE bank_institution_type = 'BANK';
• SELECT bank_party_id, bank_name, site_location_id, site_address_line1 FROM apps.ce_banks_v WHERE bank_party_id = :p_party_id;

Because the view is documented as internal and unsupported for direct DML, all queries should be read-only, and any inserts, updates, or deletes must be performed through supported CE or TCA application APIs.