Results for “ece_primary_contact_phone_v”

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

Overview

ECE_PRIMARY_CONTACT_PHONE_V is a database view shipped as part of the Oracle e-Commerce Gateway (EC) module in Oracle E-Business Suite 12.1.1 and 12.2.2. Its purpose is to expose a single, primary, general-purpose telephone number for a given contact, drawn from the Receivables phone repository. Within the e-Commerce Gateway integration layer, the view serves as a simplified projection that downstream extraction programs, interface tables, and outbound transaction generators can query when a primary contact phone is required without needing to resolve the primary-flag logic themselves.

The view is intentionally narrow. Rather than presenting the full set of phone records attached to a contact, it filters to records that satisfy three conditions simultaneously: the record must be associated with a non-null contact, the phone type must be 'GEN' (general), and the record must be flagged as primary. The result is a view that returns at most one row per qualifying contact — the designated primary general phone.

Underlying Base Objects

The view is defined over a single documented base object, RA_PHONES, aliased as RAP in the view definition. RA_PHONES is the Receivables phone table that stores telephone numbers for parties, contacts, customers, and related entities. The view's definition is expressed as a SELECT with three NULL placeholders projected against RA_PHONES, with the filtering predicate applied in the WHERE clause.

• RA_PHONES RAP — the sole documented source table, containing contact IDs, phone type classifications, primary flags, area codes, and phone numbers.
• No joins to other tables are documented in the view text.
• No additional referenced base objects are documented in the ETRM metadata for 12.2.2.

Because the view projects literal NULL values in place of column expressions, its role is largely structural: it establishes a queryable object with a stable column list (CONTACT_ID, AREA_CODE, PHONE_NUMBER) over which integration logic can be layered or which can be redefined or extended at implementation time. The ETRM metadata notes the view as "Not implemented in this database," indicating that in the documented environment the object was not deployed to the database schema at the time of extraction.

Key Columns

• CONTACT_ID — the identifier of the contact with whom the phone number is associated. In the view's WHERE clause this column is constrained to be non-null, ensuring only phones tied to an actual contact are returned.
• AREA_CODE — the area code component of the telephone number, sourced from the RA_PHONES record where phone type is 'GEN' and the primary flag is 'Y'.
• PHONE_NUMBER — the telephone number itself, subject to the same filtering conditions.

The three filters — CONTACT_ID IS NOT NULL, PHONE_TYPE = 'GEN', and PRIMARY_FLAG = 'Y' — collectively define the semantic contract of the view: one primary general phone per contact.

Common Use Cases and Queries

This view is typically consumed by e-Commerce Gateway extraction and mapping logic that needs a clean contact phone value for outbound documents, interface staging, or reporting. A representative query retrieves the primary phone for a specific contact:

• SELECT CONTACT_ID, AREA_CODE, PHONE_NUMBER FROM ECE_PRIMARY_CONTACT_PHONE_V WHERE CONTACT_ID = :contact_id;
• SELECT CONTACT_ID, AREA_CODE, PHONE_NUMBER FROM ECE_PRIMARY_CONTACT_PHONE_V ORDER BY CONTACT_ID;

Because the view depends on RA_PHONES, the values returned reflect the Receivables phone data at query time. If the implementation metadata indicates the view is not installed in a given database, developers should verify object existence before relying on it, or reproduce the same logic directly against RA_PHONES using the documented predicates.