Results for “ece_primary_customer_phone_v”

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

Overview

ECE_PRIMARY_CUSTOMER_PHONE_V is a view shipped within the Oracle E-Business Suite e-Commerce Gateway module (product code EC). Its purpose is to expose the single, primary general-purpose telephone number associated with a customer address, stripped down to the minimal column set required by e-Commerce Gateway inbound and outbound processing. In EBS 12.1.1 and 12.2.2 the e-Commerce Gateway relies on a family of interface views to stage trading-partner and customer data before it is loaded into the transaction interface tables. This particular view supplies the customer telephone attribute that appears on outbound documents and on certain inbound translation requirements.

ETRM metadata records that this view is not implemented in the reference database. That is a normal condition: EBS ships many "seed" views whose underlying SQL is documented for completeness but which are only created in a customer instance when the corresponding e-Commerce Gateway feature set is enabled or when the module is first used. The presence of the definition in ETRM confirms the view is part of the supported object inventory of the EC product even where no compiled object exists.

Underlying Base Objects

The documented definition references exactly one base object, the Oracle Receivables phones table, RA_PHONES, aliased as RAP. No other base tables, synonyms, or sequences are documented for this view. The relationship is a straightforward projection: the view reads rows from RA_PHONES and filters them, then publishes four values per qualifying row. No joins are performed; the view does not reach into RA_CUSTOMERS, HZ_CUST_ACCOUNTS, or any of the TCA party tables.

Key Columns

The documented column list exposes four attributes, each of which corresponds positionally to a value in the defining SELECT:

• CUSTOMER_ID — the Receivables customer identifier (RAP.CUSTOMER_ID) that owns the phone record. All rows are restricted to non-null values.
• ADDRESS_ID — the address for which the phone number is recorded (RAP.ADDRESS_ID); also constrained to be non-null.
• AREA_CODE — the area code component of the primary general phone number.
• PHONE_NUMBER — the telephone number itself, drawn from the row whose phone type and primary flag qualify.

Notably, the view returns only the primary general phone where the phone record is tied to an address rather than to a specific contact. The filter set is:

• RAP.CUSTOMER_ID IS NOT NULL — eliminates unassigned phone records.
• RAP.ADDRESS_ID IS NOT NULL — excludes contact-level or party-level numbers that carry no address context.
• RAP.CONTACT_ID IS NULL — ensures the number is address-level, not a personal contact number.
• RAP.PHONE_TYPE = 'GEN' — restricts to the "General" phone type.
• RAP.PRIMARY_FLAG = 'Y' — returns only the number flagged as primary.

Common Use Cases and Queries

This view is most useful when a customer's primary general telephone number must be retrieved by CUSTOMER_ID and ADDRESS_ID without navigating the full Oracle Trading Community Architecture (TCA) model. Typical scenarios include outbound e-Commerce Gateway document generation that requires a customer contact telephone, custom concurrent programs that enrich order or invoice data, and ad-hoc reporting that needs the primary address phone for a customer site.

A representative query retrieving the primary phone for a known customer and address is:

• SELECT customer_id, address_id, area_code, phone_number
• FROM   ece_primary_customer_phone_v
• WHERE  customer_id = :p_customer_id
• AND    address_id  = :p_address_id;

A broader listing for a set of customers can be produced by joining the view to RA_CUSTOMERS or HZ_CUST_ACCOUNTS on the customer identifier, or by filtering on the address identifier when the goal is to validate that an address carries a defined primary general phone. Because the view is not created in all instances, implementers should confirm its existence in the target database, or use the documented SQL against RA_PHONES directly where the view has not been deployed.