Results for “phone_area_code”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AR_CBA_BANK_ACCOUNT_CONTACTS_V is an APPS-owned database view in the Oracle E-Business Suite Receivables (AR) module. The ETRM metadata records its status as VALID and associates it with Release 11.6, indicating it originated in an early multi-org architecture and has been carried forward through 12.1.1 and 12.2.2. The view flattens contact information for parties associated with customer bank accounts held in Oracle Receivables, presenting a single denormalized row per bank account contact. Rather than requiring callers to navigate the many-to-one relationships across trading community and cash management tables, the view resolves party names, telephone numbers, fax numbers, email addresses, URLs, and the owning bank account identifier into one projection. This makes it suitable for reporting on remit-to contacts, generating customer-facing documents such as direct debit or ACH authorization letters, and for integration interfaces that must export bank account contact details to external payment or treasury systems.

Underlying Base Objects

The ETRM metadata documents four referenced base synonyms: CE_CONTACT_ASSIGNMENTS, HZ_CONTACT_POINTS, HZ_PARTIES, and HZ_RELATIONSHIPS. The view text joins these through HZ_RELATIONSHIPS (aliased ACREL) to CE_CONTACT_ASSIGNMENTS (CCA) on RELATIONSHIP_ID, and requires CCA.BANK_ACCOUNT_ID to be non-null, which restricts output to contacts explicitly assigned to a bank account. ACREL.SUBJECT_ID, where SUBJECT_TYPE is 'PERSON' and SUBJECT_TABLE_NAME is 'HZ_PARTIES', resolves to the contact person's party record (PERSONPARTY). ACREL.PARTY_ID links to RELPARTY, the organization or party with which the contact is associated. Four outer joins to HZ_CONTACT_POINTS supply telephone, fax, email, and web contact points, each qualified by OWNER_TABLE_NAME 'HZ_PARTIES', OWNER_TABLE_ID equal to RELPARTY.PARTY_ID, an appropriate CONTACT_POINT_TYPE or PHONE_LINE_TYPE, and STATUS 'A'. Only active relationships and active person parties are returned.

Key Columns

• LAST_NAME, FIRST_NAME, MIDDLE_NAME, TITLE, PREFIX — name components and title of the contact person, taken from HZ_PARTIES.
• PHONE_COUNTRY_CODE, PHONE_AREA_CODE, PHONE_NUMBER, RAW_PHONE_NUMBER — the general telephone contact point (PHONE_LINE_TYPE 'GEN').
• FAX_COUNTRY_CODE, FAX_AREA_CODE, FAX_NUMBER, RAW_FAX_NUMBER — the facsimile contact point (PHONE_LINE_TYPE 'FAX'). RAW_FAX_NUMBER corresponds directly to the user search term "raw_fax_number" and stores the unformatted fax value from HZ_CONTACT_POINTS.RAW_PHONE_NUMBER.
• EMAIL_ADDRESS — email contact point where CONTACT_POINT_TYPE is 'EMAIL'.
• URL — web contact point where CONTACT_POINT_TYPE is 'WEB'.
• BANK_ACCOUNT_ID — identifier from CE_CONTACT_ASSIGNMENTS linking the contact to the customer bank account.

Common Use Cases and Queries

The view supports remit-to and bank account maintenance reporting where users need both formatted and raw fax data. A typical query returns the primary contact details for a specific bank account:

• SELECT last_name, first_name, phone_number, raw_fax_number, email_address FROM ar_cba_bank_account_contacts_v WHERE bank_account_id = :p_bank_account_id;
• SELECT bank_account_id, last_name, fax_number, raw_fax_number FROM ar_cba_bank_account_contacts_v ORDER BY bank_account_id; — used to audit fax data quality, since RAW_FAX_NUMBER retains the unformatted value while FAX_NUMBER may be assembled from country and area codes.
• SELECT last_name, email_address, url FROM ar_cba_bank_account_contacts_v WHERE email_address IS NOT NULL; — for electronic notification and direct debit correspondence.

Because the view is defined over HZ and CE base objects with outer joins, consumers should apply restrictive predicates such as BANK_ACCOUNT_ID to avoid full-table scans over the contact point tables. The view exposes no organization identifier beyond BANK_ACCOUNT_ID, so multi-org filtering must be derived by joining to CE_BANK_ACCOUNTS in downstream queries.