Results for “phone_contact_point_id”

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

Overview

The IBY_F_LENDER_CONTACTS_V view is a reporting and integration object owned by the APPS schema within the Oracle E-Business Suite IBY – Payments product. Its status is VALID in both EBS 12.1.1 and 12.2.2. The view exposes the contact information of lenders (financial institutions) registered as business partners in the payments infrastructure, denormalizing data that is otherwise distributed across the Oracle Trading Community Architecture (TCA) and the Payments business partner repository.

In practical terms, the view answers the question: "For a given payment business partner (lender), who are the associated contacts, and what are their e-mail addresses, phone numbers, job titles, and addresses?" It is primarily used for reporting, for outbound payment integration extracts, and for validating contact data used during payment processing. Because the view joins multiple TCA entities, it provides a single flattened row per lender-contact combination, which simplifies downstream reporting and avoids re-implementing the complex TCA join logic.

Underlying Base Objects

The view is defined over eight documented base objects. The primary driver is IBY_BEPINFO (synonym), which holds the payments business partner identifier (BEPID) — the BEP is the lender in this context. HZ_PARTIES (synonym) is referenced twice: once as the lender party (HPE1, aliased to expose LENDER_PARTY_ID and LENDER_PARTY_NAME) and once as the contact party (HPE, exposing CONTACT_NAME, PERSON_FIRST_NAME, and PERSON_LAST_NAME).

Contact attributes are derived from HZ_ORG_CONTACTS (synonym), which supplies JOB_TITLE and DEPARTMENT, and from HZ_CONTACT_POINTS (synonym), which is referenced twice — once for the e-mail contact point (HCPE) and once for the phone contact point (HCPP). Location data is drawn from HZ_LOCATIONS (synonym) through HZ_PARTY_SITES and HZ_PARTY_SITE_USES (synonyms), while AR_LOOKUPS (view) is used in the join logic to resolve lookup-coded values (such as contact point purpose).

Key Columns

• BEPID — Business partner identifier linking the row back to the lender's payments business partner record.
• LENDER_PARTY_ID / LENDER_NAME — The TCA party identifier and name of the lending institution.
• CONTACT_PARTY_ID / CONTACT_NAME — The TCA party identifier and display name of the individual contact.
• PERSON_FIRST_NAME, PERSON_LAST_NAME — The personal name components of the contact.
• EMAIL_CONTACT_POINT_ID, EMAIL_FORMAT, EMAIL_ADDRESS — The contact's e-mail contact point details.
• PHONE_COUNTRY_CODE, PHONE_AREA_CODE, PHONE_NUMBER, PHONE_EXTENSION, PHONE_LINE_TYPE — The contact's telephone contact point details.
• JOB_TITLE, DEPARTMENT — Organizational attributes of the contact from HZ_ORG_CONTACTS.
• LOCATION_ID, ADDRESS1, ADDRESS2, CITY, STATE, POSTAL_CODE, PROVINCE, COUNTRY — The composed address of the contact.
• The *_OVN columns (PERSON_PARTY_OVN, EMAIL_ADDR_OVN, PHONE_OVN, LOCATION_OVN) are hard-coded to -1, serving as object version numbers for the corresponding TCA entities.

Common Use Cases and Queries

Typical scenarios include extracting lender contacts for payment settlement notifications, building remittance-advice distribution lists, or auditing contact completeness for lenders. A representative query retrieves all contacts for a specific lender:

• Lender-specific contact extract:

  SELECT bepid, lender_name, contact_name,
         email_address, phone_number,
         job_title, city, country
  FROM   apps.iby_f_lender_contacts_v
  WHERE  lender_party_id = :p_lender_party_id
  AND    email_address IS NOT NULL;

• Contacts missing e-mail or phone:

  SELECT bepid, lender_name, contact_name, email_address, phone_number
  FROM   apps.iby_f_lender_contacts_v
  WHERE  email_address IS NULL
  OR     phone_number IS NULL;

• Lender-by-lender summary count:

  SELECT lender_party_id, lender_name, COUNT(*) contact_count
  FROM   apps.iby_f_lender_contacts_v
  GROUP  BY lender_party_id, lender_name
  ORDER  BY lender_name;

Because the view is read-only and joins multiple TCA objects, queries should be restricted by BEPID or LENDER_PARTY_ID wherever possible to limit execution cost. Applications should treat the view as a reporting interface and not attempt DML against it.