Search Results address_line4




Overview
Explore in AI Chat

Overview

The CE_BANKS_MERGE_V view is a Cash Management (CE) reporting object in Oracle E-Business Suite, defined in the APPS schema with a status of VALID in both release 12.1.1 and 12.2.2. It exposes a denormalized, flattened representation of bank and clearinghouse records drawn from the Trading Community Architecture (TCA) party model. The view presents each qualifying party — those whose usage assignment includes "BANK" or "CLEARINGHOUSE" — together with its identifying, descriptive, and address attributes in a single row. It is intended to support bank lookups, merger/duplicate-review operations, and downstream reporting where a consolidated bank profile is required without navigating the multiple TCA tables directly. Because it resides in the APPS schema, it is accessible to standard EBS responsibility users and to custom concurrent programs and integrations that read Cash Management master data.

Underlying Base Objects

The view text is defined over two documented base objects: HZ_PARTIES (accessed through a synonym) and HZ_PARTY_USG_ASSIGNMENTS (also accessed through a synonym). HZ_PARTIES is the master record for all TCA parties and supplies the bank name, alternate/phonetic name, short name, the four address lines, city, state, province, postal code, country, and description attributes. HZ_PARTY_USG_ASSIGNMENTS supplies the party usage code, which the view restricts to 'BANK' and 'CLEARINGHOUSE'. The join is an equality between BANKPARTY.PARTY_ID and BANKUSG.PARTY_ID. Notably, the address columns are sourced from HZ_PARTIES itself; the view does not join to HZ_LOCATIONS or HZ_PARTY_SITES for those attributes. The ORDER of the projection also includes BANKPARTY.ROWID as ROW_ID and a trailing BANKPARTY.PARTY_ID, with a documented PK_ID column and the BANK_INSTITUTION_TYPE alias for the usage code.

Key Columns

  • ROW_ID — the ROWID of the underlying HZ_PARTIES row.
  • BANK_PARTY_ID / PARTY_ID — the TCA party identifier; the effective primary key for linking to related bank records.
  • BANK_NAME — party name (PARTY_NAME); the primary bank display name.
  • BANK_NAME_ALT — organization name phonetic value.
  • SHORT_BANK_NAME — the known-as value.
  • ADDRESS_LINE1, ADDRESS_LINE2, ADDRESS_LINE3, ADDRESS_LINE4 — mapped from ADDRESS1 through ADDRESS4. ADDRESS_LINE2 corresponds directly to the HZ_PARTIES.ADDRESS2 column and is the field commonly sought when searching for secondary address information.
  • CITY, STATE, PROVINCE, ZIP, COUNTRY — geographic attributes (POSTAL_CODE is aliased as ZIP).
  • BANK_INSTITUTION_TYPE — the usage code, either 'BANK' or 'CLEARINGHOUSE'.
  • DESCRIPTION — mapped from MISSION_STATEMENT.
  • PK_ID — documented primary-key/identifier column.

Common Use Cases and Queries

Typical uses include validating bank master data during merger or de-duplication review, feeding bank lookups into payment or reconciliation processes, and searching by a specific address element such as ADDRESS_LINE2. The following query retrieves banks matching a partial second address line:

SELECT bank_party_id,
       bank_name,
       short_bank_name,
       address_line1,
       address_line2,
       city,
       state,
       zip,
       country,
       bank_institution_type
FROM   ce_banks_merge_v
WHERE  address_line2 IS NOT NULL
AND    UPPER(address_line2) LIKE UPPER('%&search_term%')
ORDER  BY bank_name;

To isolate clearinghouses only:

SELECT bank_party_id, bank_name, address_line2
FROM   ce_banks_merge_v
WHERE  bank_institution_type = 'CLEARINGHOUSE';

Because the view draws address data from HZ_PARTIES rather than the location model, results reflect the party-level address fields and should be cross-checked against HZ_LOCATIONS or HZ_PARTY_SITES when site-specific addressing is required.