Search Results per_information1

Overview

ICX_PER_PEOPLE_X_V is an APPS-owned database view in Oracle E-Business Suite, delivered under the ICX (Oracle iProcurement) product. The ETRM record for this object lists its description as "Obsolete," indicating that Oracle no longer actively maintains or recommends the view in the 12.1.1 or 12.2.2 code lines, even though the object remains present with a VALID status in the APPS schema. The view functions as a thin pass-through layer defined over PER_PEOPLE_X, exposing the underlying people record structure to iProcurement and other ICX-related components. Its practical role in reporting and integration is therefore limited to legacy or backward-compatibility scenarios: it presents person and applicant attributes — including APPLICANT_NUMBER — in a querable form for modules that historically referenced the ICX-namespaced object rather than the PER schema objects directly.

Underlying Base Objects

According to the documented view metadata, ICX_PER_PEOPLE_X_V is defined over PER_PEOPLE_X (VIEW), with dependencies on the HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY packages. The view text confirms this relationship explicitly: the SELECT statement projects every column of PER_PEOPLE_X without transformation, filtering, or join logic. This means the view inherits all business rules, security behavior, and row filtering implemented in the PER_PEOPLE_X view, which in turn is the effective-dated, secured representation of the PER_PEOPLE_F / PER_ALL_PEOPLE_F person model. Because ICX_PER_PEOPLE_X_V adds no logic of its own, its behavior is entirely determined by the underlying PER objects; any change to PER_PEOPLE_X propagates directly.

Key Columns

The view projects the complete column list of PER_PEOPLE_X. Columns most relevant to reporting include:

• PERSON_ID — primary identifier of the person record.
• APPLICANT_NUMBER — the applicant identifier, the attribute referenced by the user's search term; used for external applicant tracking.
• EMPLOYEE_NUMBER — the employee identifier for persons who are also employees.
• FULL_NAME, FIRST_NAME, LAST_NAME, MIDDLE_NAMES, KNOWN_AS, PREVIOUS_LAST_NAME, TITLE — name and personal data attributes.
• EFFECTIVE_START_DATE, EFFECTIVE_END_DATE, START_DATE — date-tracked validity columns inherited from the effective-dated person model.
• CURRENT_APPLICANT_FLAG, CURRENT_EMP_OR_APL_FLAG, CURRENT_EMPLOYEE_FLAG — current-record indicators.
• EMAIL_ADDRESS, WORK_TELEPHONE, NATIONALITY, SEX, DATE_OF_BIRTH, NATIONAL_IDENTIFIER, MARITAL_STATUS — contact and personal attributes.
• BUSINESS_GROUP_ID, PERSON_TYPE_ID, VENDOR_ID, COMMENT_ID — organizational and type references.
• ATTRIBUTE1–ATTRIBUTE30, PER_INFORMATION_CATEGORY, PER_INFORMATION1–20 — DFF and extra information flexfield segments.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE, OBJECT_VERSION_NUMBER — audit and versioning columns.

Common Use Cases and Queries

Because the view is marked obsolete, it should only be used where an existing custom component already references it. A typical query retrieving an applicant by number is:

SELECT person_id, applicant_number, full_name, email_address, current_applicant_flag FROM apps.icx_per_people_x_v WHERE applicant_number = :applicant_number AND current_applicant_flag = 'Y';

Broader person lookups follow the same pattern, for example selecting by employee number or full name and restricting to current effective records. HR_SECURITY dependencies mean results are subject to the security profile of the connecting user, so the same query may return different rows for different responsibilities. For new development, Oracle's supported direction is to query the PER schema person views directly rather than this obsolete ICX view.