Search Results last_name_phonetic




Overview
Explore in AI Chat

Overview

APPS.IRC_REGISTERED_USERS is a read-only database view in the Oracle E-Business Suite (EBS) Applications schema, valid in both 12.1.1 and 12.2.2. It conforms to the iRecruitment (IRC) module and exposes a consolidated set of personal identity attributes for individuals who have registered with the iRecruitment application. The view gathers name, phonetic name, birth, death, and marital data into a single denormalized projection, and it is defined with the FND design data reference PER.IRC_REGISTERED_USERS, indicating that its logical definition originates from the People (PER) product family metadata.

The view is flagged "Oracle Internal Use Only." Oracle Corporation does not support direct access to Applications data through this object except from standard Oracle Applications programs. Consequently, it should be treated as an internal implementation object rather than a supported integration point. Its practical relevance for the search term "first_name_phonetic" is direct: the view surfaces FIRST_NAME_PHONETIC as a first-class column, allowing phonetic matching of a registrant's given name.

Underlying Base Objects

Per the documented ETRM metadata, APPS.IRC_REGISTERED_USERS is defined over two referenced base objects, both accessed through APPS synonyms:

  • HZ_PERSON_PROFILES — the Trading Community Architecture (TCA) person profile entity that stores core person attributes such as name components and birth information.
  • IRC_NOTIFICATION_PREFERENCES — the iRecruitment notification preference entity associated with registered users.

The view is not referenced by any other database object, so it sits at the top of its dependency chain as a terminal consumer of these two sources. Because the view has no downstream dependents, changes to its definition do not cascade to other database objects, though application code may still depend on it at runtime.

Key Columns

The view exposes fifteen columns. The identity and name columns are the most heavily used:

Common Use Cases and Queries

Typical scenarios include phonetic candidate name searches, extraction of registered-user demographics for reporting, and reconciliation between iRecruitment registrations and TCA person records. A basic query retrieves all columns:

  • SELECT FIRST_NAME, LAST_NAME, NAME_PHONETIC, LAST_NAME_PHONETIC, FIRST_NAME_PHONETIC, MIDDLE_NAME, NAME_SUFFIX, PREVIOUS_LAST_NAME, KNOWN_AS, PERSON_ID, DATE_OF_BIRTH, PLACE_OF_BIRTH, DATE_OF_DEATH, MARITAL_STATUS, PRE_NAME_ADJUNCT FROM APPS.IRC_REGISTERED_USERS;

To target the searched term, a phonetic name lookup can filter directly on the phonetic column:

  • SELECT PERSON_ID, FIRST_NAME, FIRST_NAME_PHONETIC FROM APPS.IRC_REGISTERED_USERS WHERE FIRST_NAME_PHONETIC = :p_phonetic;

Because of the Oracle Internal Use Only restriction, such queries are appropriate for diagnostic or reporting purposes only and should not be embedded in supported interfaces without Oracle's endorsement.