Results for “email_format_meaning”

15 results




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

Overview

The IGS_PE_CONTACTS_DETAILS_V view is a denormalized reporting and integration object within the Oracle E-Business Suite Student System (IGS) product family. It presents person and organization contact point information — email addresses, telephone numbers, and related attributes — in a form that is directly consumable by reports, concurrent programs, and external interfaces without requiring joins to the FND_LOOKUP_VALUES table. The view surfaces both the stored code values (for example, EMAIL_FORMAT and PHONE_LINE_TYPE) and their translated meanings (EMAIL_FORMAT_MEANING and PHONE_LINE_TYPE_MEANING), enabling user-facing output to display descriptive lookup text rather than internal codes.

Underlying Base Objects

Per the ETRM metadata, the view is defined over one base table and three references to the FND_LOOKUP_VALUES lookup table:

  • IGS_PE_CONTACT_DTLS — the primary base table, aliased CP, which stores contact point records including status, email, and telephone data.
  • FND_LOOKUP_VALUES L1 — joined on STATUS = LOOKUP_CODE with LOOKUP_TYPE = 'REGISTRY_STATUS'.
  • FND_LOOKUP_VALUES L2 — joined on PHONE_LINE_TYPE = LOOKUP_CODE with LOOKUP_TYPE = 'PHONE_LINE_TYPE'.
  • FND_LOOKUP_VALUES L3 — joined on EMAIL_FORMAT = LOOKUP_CODE with LOOKUP_TYPE = 'EMAIL_FORMAT'.

All three lookup joins are outer joins (denoted by the (+) operator) and are constrained by LANGUAGE = USERENV('LANG'), VIEW_APPLICATION_ID = 222, and SECURITY_GROUP_ID = 0, ensuring language-appropriate and application-scoped translations. The outer-join semantics allow contact records to be returned even when a matching lookup value is absent.

Key Columns

The view exposes the surrogate ROW_ID (CP.ROWID) along with the primary key CONTACT_POINT_ID and the LOCATION_VENUE_ADDR_ID foreign key linking to address information. CONTACT_POINT_TYPE identifies whether the record is an email, phone, or other contact mechanism. STATUS and STATUS_MEANING provide the registry status code and its decoded description.

For email functionality, EMAIL_FORMAT stores the lookup code and EMAIL_FORMAT_MEANING exposes the corresponding decoded meaning (the column most relevant to the email_format_meaning search). EMAIL_ADDRESS holds the actual address value. Telephone columns include TELEPHONE_TYPE, PHONE_AREA_CODE, PHONE_COUNTRY_CODE, PHONE_NUMBER, PHONE_EXTENSION, and PHONE_LINE_TYPE, with PHONE_LINE_TYPE_MEANING supplying the decoded line-type description. Standard audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) and the concurrent program context columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE) are also present, followed by twenty generic ATTRIBUTE columns for extensibility.

Common Use Cases and Queries

Typical uses include generating student or prospect contact listings, driving email notification interfaces, and validating that contact records carry properly coded email formats. A representative query retrieving email contacts with decoded format meaning is:

  • SELECT contact_point_id, email_address, email_format_meaning FROM igs_pe_contacts_details_v WHERE contact_point_type = 'EMAIL';
  • SELECT phone_number, phone_line_type_meaning FROM igs_pe_contacts_details_v WHERE contact_point_type = 'PHONE' AND status_meaning = 'Active';
  • SELECT email_format, email_format_meaning, COUNT(*) FROM igs_pe_contacts_details_v GROUP BY email_format, email_format_meaning;

Because the lookup decoding is embedded, these queries return presentation-ready results suitable for BI Publisher reports and inbound/outbound integration extracts without additional lookup joins.