Results for “telephone_type”

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

Overview

The IGS_OR_PHONES_V view is a component of the Oracle IGS (Student System) product family, a module now classified as obsolete within Oracle E-Business Suite. The view is documented with the description "Describes Institution Phone Details," indicating its original purpose was to expose telephone and contact-point information associated with external organizations and parties in the student system context. It is a reporting-oriented construct that flattens the phone-related attributes stored on the underlying contact-point records, providing consumers with a denormalized read surface for institution and organization telephone data.

The ETRM metadata explicitly states that this view is "Not implemented in this database," meaning the object is documented as part of the reference data model but is not physically present in the installed schema. Administrators and developers searching for telephone_type will nonetheless encounter this view because its column list includes TELEPHONE_TYPE. The view therefore has value primarily as a documentation artifact and as a template for understanding how IGS phone data was modeled against the Oracle Contacts (HZ) foundation tables. In EBS 12.1.1 and 12.2.2 environments, actual phone data resides in the HZ contact-point tables rather than in this legacy IGS view.

Underlying Base Objects

The documented view text reveals that IGS_OR_PHONES_V is defined over a single base object: HZ_CONTACT_POINTS, aliased as CONT_POINT. No other base tables are referenced in the metadata, and the ETRM "Referenced base objects" section explicitly lists none. The view applies two principal filters to that base table:

• CONT_POINT.OWNER_TABLE_NAME = 'HZ_PARTIES' — restricting rows to contact points owned by party records, i.e., institutions or organizations rather than other entity types.
• CONT_POINT.CONTACT_POINT_TYPE NOT IN ('EDI', 'EMAIL', 'WEB') — excluding non-telephone contact-point categories so that only telephone, telex, and similar records are returned.

Because the view is built directly on HZ_CONTACT_POINTS, its freshness, partitioning, and security characteristics are inherited from that shared TCA (Trading Community Architecture) table.

Key Columns

The view exposes a broad set of contact-point attributes, several of which are central to telephone reporting:

• PHONE_ID — the aliased CONTACT_POINT_ID, uniquely identifying each phone record.
• PHONE_NUMBER — derived via DECODE; returns TELEX_NUMBER when the contact-point type is 'TLX', otherwise PHONE_NUMBER.
• PHONE_TYPE — the resolved type, computed as NVL(PHONE_LINE_TYPE, CONTACT_POINT_TYPE), giving the most specific classification available.
• TELEPHONE_TYPE — the raw underlying attribute from HZ_CONTACT_POINTS, the exact column matched by a "telephone_type" search.
• COUNTRY_CODE, AREA_CODE, EXTENSION — the component parts of a dialable number.
• STATUS, PRIMARY_FLAG — lifecycle and precedence indicators.
• OWNER_TABLE_NAME and OWNER_TABLE_ID — identify the owning party record.
• ORIG_SYSTEM_REFERENCE, OBJECT_VERSION_NUMBER, and the ATTRIBUTE1–ATTRIBUTE20 flex columns — supporting integration, concurrency control, and descriptive flexibility.

Common Use Cases and Queries

The principal use case is extracting institution phone details for student-system reporting and integration feeds. A typical query retrieves primary phone numbers for parties, filtered by type:

• Listing all telephone numbers with their resolved type: SELECT PHONE_ID, PHONE_NUMBER, PHONE_TYPE, TELEPHONE_TYPE FROM IGS_OR_PHONES_V WHERE STATUS = 'A';
• Restricting to primary numbers for a party: SELECT PHONE_NUMBER, AREA_CODE, EXTENSION FROM IGS_OR_PHONES_V WHERE OWNER_TABLE_ID = :party_id AND PRIMARY_FLAG = 'Y';
• Filtering specifically on the searched attribute: SELECT * FROM IGS_OR_PHONES_V WHERE TELEPHONE_TYPE = 'GEN';

Because the object is not implemented, these queries should be redirected to HZ_CONTACT_POINTS or the supported HZ_PHONES_V-style view in a live 12.1.1 or 12.2.2 instance; the IGS view remains useful chiefly as a documented model of the intended column semantics.