Search Results raw_phone_number




Overview
Explore in AI Chat

Overview

AR_CBA_BANK_BRANCH_CONTACTS_V is a Receivables (AR) view owned by the APPS schema that exposes contact information for banks and bank branches in Oracle E-Business Suite. As the name indicates, it derives its contents from the Customer/Bank Account (CBA) entity model and returns the people associated with a bank or branch party along with their telephone, fax, e-mail, and web contact points. The view is documented in ETRM as existing under Release 11.6 only, which means it appears in the reference material for the earlier Oracle applications generation rather than being newly introduced in 12.1.1 or 12.2.2. It is therefore a legacy compatibility object that persists in the APPS schema of Release 12 environments, including 12.1.1 and 12.2.2, where it can still be queried by custom reports and integrations that were written against the 11.6 data model.

The view's functional role is to bridge the Oracle Receivables contact assignment infrastructure (CE_CONTACT_ASSIGNMENTS) with the Trading Community Architecture (TCA) party and contact point tables (HZ_PARTIES, HZ_RELATIONSHIPS, HZ_CONTACT_POINTS). By restricting CCA.BANK_ACCOUNT_ID to NULL, it limits results to relationships defined at the bank or branch level rather than at the individual bank account level. This makes it a reporting convenience view for bank and branch contact directories, useful in payment and treasury reporting where the responsible contact person for a banking institution must be identified.

Underlying Base Objects

The ETRM 12.2.2 metadata lists four referenced base objects, all accessed through APPS synonyms: CE_CONTACT_ASSIGNMENTS, HZ_CONTACT_POINTS, HZ_PARTIES, and HZ_RELATIONSHIPS. The view text joins these as follows:

  • HZ_RELATIONSHIPS (BCREL) — the driving relationship record. The view requires RELATIONSHIP_ID to exist, STATUS to be 'A' (active), SUBJECT_TYPE to be 'PERSON', and SUBJECT_TABLE_NAME to be 'HZ_PARTIES'. The relationship's SUBJECT_ID identifies the contact person.
  • CE_CONTACT_ASSIGNMENTS (CCA) — supplies the bank or branch party. Its RELATIONSHIP_ID must match the relationship, and BANK_ACCOUNT_ID must be NULL to exclude account-level contacts.
  • HZ_PARTIES (PERSONPARTY) — the person party supplying name, title, prefix, and name adjunct columns.
  • HZ_PARTIES (RELPARTY) — the related party used as the owner of the contact points (PHONE, FAX, EMAIL, WEB).
  • HZ_CONTACT_POINTS — appears four times, aliased PHONE, FAX, EMAIL, and WEB, each outer-joined on OWNER_TABLE_NAME = 'HZ_PARTIES', OWNER_TABLE_ID = RELPARTY.PARTY_ID, STATUS = 'A', and the appropriate CONTACT_POINT_TYPE and, for the phone aliases, PHONE_LINE_TYPE.

The outer joins (+) ensure that a contact person is returned even when no phone, fax, e-mail, or web point is recorded.

Key Columns

Common Use Cases and Queries

Typical uses include producing contact directories for banking institutions, verifying that a bank or branch has an assigned contact, and validating e-mail or web addresses stored for bank contacts. A simple query returning bank contacts with their e-mail and web addresses is:

SELECT bank_or_branch_id, last_name, first_name, phone_number, fax_number, email_address, url FROM apps.ar_cba_bank_branch_contacts_v WHERE bank_or_branch_id = :p_party_id;

To find contacts with an e-mail or web presence only:

SELECT bank_or_branch_id, last_name, first_name, email_address, url FROM apps.ar_cba_bank_branch_contacts_v WHERE email_address IS NOT NULL OR url IS NOT NULL;

Because the view applies outer joins, consumers should always guard against NULL contact point columns in reports. Since it is a Release 11.6-era object, it should be treated as read-only and validated against the corresponding TCA views when migrating customizations to 12.2.2, where the underlying HZ model remains the authoritative source.