Search Results date_employee_data_verified




Overview
Explore in AI Chat

Overview

APPS.POS_PER_PEOPLE_X_V is a public Oracle E-Business Suite view that exposes the columns of the PER_PEOPLE_X entity in a form suitable for reporting, integration, and concurrent processing. In the EBS 12.1.1 and 12.2.2 data models, PER_PEOPLE_X is the dated (effective-dated) extension table for person records stored in PER_ALL_PEOPLE_F. The _X suffix designates the "extra information" table that holds non-key, implementation-specific person attributes — notably the descriptive flexfield (DFF) segments ATTRIBUTE1 through ATTRIBUTE30 and the PER_INFORMATIONn columns — together with the surrogate and audit keys required to relate each row back to the parent person and to a specific effective date. POS_PER_PEOPLE_X_V presents this data through the APPS schema so that callers gain synonym-based access consistent with Oracle's public API naming conventions.

Because the view does not itself enforce multitenancy or security predicates, it functions as a thin projection rather than a secured reporting entity. Users searching for date_employee_data_verified will find that column surfaced directly by this view, which makes POS_PER_PEOPLE_X_V a common retrieval point for the date on which an employee's personal data was last verified.

Underlying Base Objects

The ETRM metadata documents the following referenced base objects:

  • PER_PEOPLE_X (VIEW) — the immediate source object. The view text is a straight projection of all columns from PER_PEOPLE_X with no joins, filters, or expressions, so row cardinality and column semantics are identical to the base view.
  • HR_GENERAL (PACKAGE) — the HR utility package that resolves effective dates, business group context, and date-tracked lookups used when the dated person model is queried. It supplies the date-tracking logic that governs which effective row is applicable.
  • HR_PERSON_NAME (PACKAGE) — the package responsible for formatting and deriving person name components (full name, known-as, previous last name). Name columns exposed here are maintained through this package's logic.
  • HR_SECURITY (PACKAGE) — the security package that applies business group and organization-level access control. Although the view text does not embed a security predicate, callers that require row-level security must route through HR_SECURITY rather than querying POS_PER_PEOPLE_X_V directly.

In practice the view inherits the effective-dating characteristics of PER_PEOPLE_X, so any query must filter on EFFECTIVE_START_DATE and EFFECTIVE_END_DATE to isolate the intended version.

Key Columns

Common Use Cases and Queries

Typical scenarios include verifying when employee data was last confirmed, extracting DFF segments for downstream interfaces, and reconciling person records across business groups. Because the view is unsecured, employ a date-track filter and consider joining to PER_ALL_PEOPLE_F for secured access.

  • Verified-date reporting: 
    SELECT person_id, employee_number, full_name,
       date_employee_data_verified
  FROM apps.pos_per_people_x_v
 WHERE TRUNC(SYSDATE) BETWEEN effective_start_date
                          AND effective_end_date
   AND current_employee_flag = 'Y';
  • Employees with no verification on record: 
    SELECT p.person_id, p.full_name, p.employee_number
  FROM apps.pos_per_people_x_v p
 WHERE p.date_employee_data_verified IS NULL
   AND p.current_employee_flag = 'Y';
  • Flexfield extraction for interfaces: 
    SELECT person_id, attribute_category,
       attribute1, attribute2, per_information1
  FROM apps.pos_per_people_x_v
 WHERE TRUNC(SYSDATE) BETWEEN effective_start_date
                          AND effective_end_date;

Each query should constrain the effective dates; omitting them returns every historical version and inflates results. Where sensitive data is involved, layer HR_SECURITY logic or query the secured person views instead.