Results for “phone_area_code”

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

Overview

ASO_PVT_PHONES_V is a private (PVT) view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the ASO - Order Capture product family. It exposes a filtered, single-purpose projection of telephone contact point data drawn from the Trading Community Architecture (TCA) contact point model. The view's defining predicate restricts the result set to active phone records associated with parties, which makes it a stable, low-noise source for phone detail lookups performed during order capture, order import, and related ASO processing. Although the naming convention identifies it as a private view, its column list and filter logic are documented in ETRM and it is frequently referenced in customizations, extracts, and reporting queries that need a consolidated phone record without traversing the fuller HZ_CONTACT_POINTS structure.

Underlying Base Objects

The view is defined over HZ_CONTACT_POINTS, accessed through a synonym resolved in the APPS schema. It is best understood as a vertical slice of that table, applying three constant filters: STATUS = 'A' (active records only), OWNER_TABLE_NAME = 'HZ_PARTIES' (contact points belonging to parties rather than other owner entities), and CONTACT_POINT_TYPE = 'PHONE' (phone contact points only). Because the view selects only eight of the many columns present in HZ_CONTACT_POINTS, joins to other TCA or ASO objects must be made through CONTACT_POINT_ID or OWNER_TABLE_ID rather than through columns not projected here. No additional tables, code, or database objects are documented as contributing to the view definition.

Key Columns

• CONTACT_POINT_ID — Surrogate identifier of the underlying phone contact point; the primary join key back to HZ_CONTACT_POINTS and to other TCA contact point usages.
• PHONE_COUNTRY_CODE — Country or international dialing code for the phone number.
• PHONE_AREA_CODE — Area code component of the number. This is the column most directly associated with the search term "phone_area_code" and is the field typically referenced when phone numbers must be segmented or validated by region.
• PHONE_NUMBER — The local subscriber number, stored as entered minus the country and area codes.
• PHONE_EXTENSION — Extension digits, when applicable.
• OWNER_TABLE_ID — Identifier of the owning entity within the HZ_PARTIES population, typically the party identifier.
• PHONE_LINE_TYPE — Classification of the line, such as general, fax, or mobile.
• PRIMARY_FLAG — Indicates whether the phone record is the primary number for its owner.

The ETRM documentation lists a PHONE_ID column in the header column block while the view text projects CONTACT_POINT_ID; implementers should confirm the actual column name against the deployed 12.1.1 or 12.2.2 instance before referencing it in code.

Common Use Cases and Queries

Typical uses include retrieving a party's primary phone during order entry, building outbound contact extracts, and validating that a party has an active phone before submitting a sales order. The following sample returns phone details for a supplied party:

• SELECT contact_point_id, phone_country_code, phone_area_code, phone_number, phone_extension, phone_line_type, primary_flag FROM apps.aso_pvt_phones_v WHERE owner_table_id = :p_party_id AND primary_flag = 'Y';
• SELECT phone_area_code, COUNT(*) FROM apps.aso_pvt_phones_v GROUP BY phone_area_code ORDER BY 2 DESC; — area code distribution across active party phones.
• SELECT v.owner_table_id, v.phone_number FROM apps.aso_pvt_phones_v v, apps.hz_parties p WHERE v.owner_table_id = p.party_id AND p.party_name LIKE :p_name; — joins the view to HZ_PARTIES for party-level reporting.

Because the view carries no ASO-specific transactional data and applies fixed filters, it should be treated as a read-only convenience layer. Custom code that requires inactive numbers, non-party owners, or non-phone contact points must query HZ_CONTACT_POINTS directly.