Results for “previous_last_name”

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

Overview

The IRC_REGISTERED_USERS view is an Oracle E-Business Suite dictionary object owned by the APPS schema and categorized under the PER (Human Resources) product family. It exposes a filtered, denormalized list of registered recruiting users — that is, persons who have an associated record in the iRecruitment notification preferences table and whose access flag has been set to allow participation. In practice, the view answers the question "which people are currently registered and permitted to access the iRecruitment module?" by joining person profile data to notification preference data.

Because the view already joins two base objects and applies a business filter (ALLOW_ACCESS = 'Y'), it is well suited for reporting, integration extracts, and dependent forms or concurrent programs that need a single, ready-to-consume source of registered user identity data. Its role in Oracle EBS is primarily as a read-only reporting and integration interface rather than as a transactional object; no DML should be issued against it directly.

Underlying Base Objects

The ETRM metadata documents two referenced base objects, both exposed through synonyms:

• HZ_PERSON_PROFILES (SYNONYM) — the Trading Community Architecture (TCA) table holding person-level attributes such as names, phonetic renderings, birth and death dates, marital status, and name adjuncts. The view selects all its display columns from this table, aliased as HPP.
• IRC_NOTIFICATION_PREFERENCES (SYNONYM) — the iRecruitment notification preferences table, aliased as INP. It supplies the ALLOW_ACCESS and PARTY_ID columns used for filtering and joining.

The join condition is HPP.PARTY_ID = INP.PARTY_ID, so the view is effectively an inner join between the two objects, further restricted by INP.ALLOW_ACCESS = 'Y'. This means any person without a matching notification preference record, or with access disallowed, is excluded from the result set.

Key Columns

The view exposes fifteen columns, most of them name and demographic attributes sourced from HZ_PERSON_PROFILES:

• FIRST_NAME, LAST_NAME, MIDDLE_NAME — the person's primary name components, drawn from PERSON_FIRST_NAME, PERSON_LAST_NAME, and PERSON_MIDDLE_NAME.
• NAME_SUFFIX — maps to PERSON_NAME_SUFFIX and carries generational or honorific suffixes such as Jr., Sr., II, or III. This is the column most directly relevant to the name_suffix search term.
• PRE_NAME_ADJUNCT — the name prefix or title (for example, Dr., Mr., Ms.), from PERSON_PRE_NAME_ADJUNCT.
• NAME_PHONETIC, FIRST_NAME_PHONETIC, LAST_NAME_PHONETIC — phonetic renderings of the full name and its components, useful for fuzzy or sound-based searching.
• PREVIOUS_LAST_NAME, KNOWN_AS — alternate or prior name information.
• PERSON_ID — the party identifier cast to a number via TO_NUMBER(HPP.PERSON_IDENTIFIER). Note that this is the party/person identifier and not necessarily the HR PERSON_ID in every deployment.
• DATE_OF_BIRTH, PLACE_OF_BIRTH, DATE_OF_DEATH, MARITAL_STATUS — demographic attributes carried through for completeness.

Common Use Cases and Queries

Typical scenarios include generating rosters of registered iRecruitment users, validating that a given person is registered before provisioning access, and extracting name data — including suffixes and phonetic forms — for downstream matching or directory purposes.

Listing all registered users with their full names, including suffix:

SELECT person_id,
       first_name,
       middle_name,
       last_name,
       name_suffix,
       pre_name_adjunct
FROM   apps.irc_registered_users
ORDER  BY last_name, first_name;

Searching specifically for persons bearing a particular suffix:

SELECT person_id, first_name, last_name, name_suffix
FROM   apps.irc_registered_users
WHERE  name_suffix = 'Jr.';

Retrieving a single registered user by identifier:

SELECT first_name, last_name, name_suffix, known_as
FROM   apps.irc_registered_users
WHERE  person_id = :p_person_id;

Because the view already enforces the ALLOW_ACCESS = 'Y' filter, callers should not attempt to re-derive that condition from the base tables; doing so risks inconsistency with the EBS-registered population. All queries should be executed under an APPS-aware responsibility with appropriate grants.