Results for “ece_contact_phone”

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

Overview

ECE_CONTACT_PHONE is a database view shipped with the Oracle E-Business Suite e-Commerce Gateway (EC) module. It exposes contact-level telephone information by joining Oracle Receivables contact records to a pre-built e-Commerce Gateway primary-contact-phone view. The object is classified under the EC product family, which handles inbound and outbound electronic business transactions such as EDI, XML, and flat-file exchanges between Oracle EBS and external trading partners. Because contact and phone information frequently accompanies outbound documents — purchase orders, invoices, advance ship notices, and remittance advice — this view serves as a flattened staging structure for extracting that information without re-deriving primary-contact logic at run time.

In both 12.1.1 and 12.2.2 the view is documented as not implemented in this database. This means the view definition exists in the ETRM data model but the physical object is created only when the relevant e-Commerce Gateway functionality is installed and active. Absence of the view therefore does not imply absence of the data; the underlying Receivables contact tables remain available regardless.

Underlying Base Objects

The documented view text is a straightforward outer join:

SELECT NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL
FROM   RA_CONTACTS RCO,
       ECE_PRIMARY_CONTACT_PHONE_V EPCP
WHERE  RCO.CONTACT_ID = EPCP.CONTACT_ID (+);

Two objects participate:

• RA_CONTACTS — the Oracle Receivables contact table, holding person records (names, job titles) associated with a customer or customer site.
• ECE_PRIMARY_CONTACT_PHONE_V — an e-Commerce Gateway view that resolves the designated primary phone number for a contact. This view encapsulates the logic of choosing which phone record to treat as "primary," so downstream consumers do not have to replicate that rule.

The join is on CONTACT_ID, with the outer-join symbol (+) applied to the phone side. Consequently every RA_CONTACTS row survives the join, and phone columns return NULL when no primary phone exists. Notably, the documentation excerpt shows the SELECT list as eight NULL literals, which is characteristic of a view whose projection was defined against a different or superseded column set, or whose runtime definition is generated dynamically by the e-Commerce Gateway concurrent programs. Implementers should inspect USER_VIEWS.TEXT or DBA_VIEWS.TEXT in the target instance rather than relying on the documented fragment.

Key Columns

• CONTACT_ID — primary key of the Receivables contact; the join key to RA_CONTACTS.
• CUSTOMER_ID — the customer or party with which the contact is associated.
• ADDRESS_ID — the site or address to which the contact is linked.
• LAST_NAME / FIRST_NAME — the contact's personal name fields.
• JOB_TITLE — the contact's role or title, often mapped to an EDI qualifier.
• AREA_CODE — the telephone area or dialing code.
• PHONE_NUMBER — the primary contact telephone number.

Together these columns form a compact contact-and-phone record suitable for direct mapping into EDI segments (for example, the PER segment) or into interface staging tables.

Common Use Cases and Queries

Typical scenarios include populating outbound partner-facing documents with a designated contact, validating that trading-partner contacts carry a reachable primary phone, and reconciling e-Commerce Gateway extracts against Receivables master data.

SELECT contact_id,
       customer_id,
       address_id,
       last_name,
       first_name,
       job_title,
       area_code,
       phone_number
FROM   ece_contact_phone
WHERE  customer_id = :customer_id
ORDER BY last_name, first_name;

To locate contacts with no primary phone:

SELECT rco.contact_id, rco.last_name
FROM   ra_contacts rco,
       ece_primary_contact_phone_v epcp
WHERE  rco.contact_id = epcp.contact_id (+)
AND    epcp.contact_id IS NULL;

For reconciliation, join the view back to RA_CUSTOMERS and HZ_PARTIES to confirm the customer identifier and party context. Because the view may not be physically implemented, always verify existence with SELECT view_name FROM all_views WHERE view_name = 'ECE_CONTACT_PHONE' before referencing it in custom code, and favour the base tables for reporting where the view is absent.