Results for “per_person_type_usages”

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

Overview

The PER_PERSON_TYPE_USAGES view is an Oracle E-Business Suite date-effective (session-dated) view owned by the APPS schema within the PER — Human Resources product. It exposes the person type assignments that apply to a person for a given period, allowing concurrent users to query the data that is valid as of their specific session date rather than as of the current system date. This behavior is critical in Oracle HRMS because person type usages — the classification of a person as, for example, an Employee, an Applicant, a Contingent Worker, or a Beneficiary — are date-tracked and change over time as a worker's relationship with the enterprise evolves.

The view is a standard EBS date-effective ("_F" table / "_V" or descriptive view) construct: it wraps the base table PER_PERSON_TYPE_USAGES_F and filters rows so that only records whose effective date range brackets the current session effective date are returned. As a reporting and integration object it provides a stable, application-level interface for retrieving valid person type usages without requiring the caller to implement the date-effectivity logic manually.

Underlying Base Objects

The view is defined over the following documented objects:

• PER_PERSON_TYPE_USAGES_F (accessed through a synonym) — the underlying date-effective base table that physically stores the person type usage records and their effective date ranges.
• FND_SESSIONS (accessed through a synonym) — the Applications session table, queried twice in the view definition to obtain the current session's effective date.

The view text selects all columns from PER_PERSON_TYPE_USAGES_F and applies the predicate EFFECTIVE_START_DATE <= (session effective date) AND EFFECTIVE_END_DATE >= (session effective date), where the session effective date is derived via a subquery on FND_SESSIONS keyed on USERENV('SESSIONID'). This guarantees that a multi-organization or multi-time-zone user sees the row set appropriate to the date the session was established, consistent with Oracle date-effectivity (DateTrack) conventions.

Key Columns

The view exposes the primary key and date-effectivity columns, the descriptive attributes, and the standard EBS WHO columns augmented by the 20 ATTRIBUTE descriptive flexfield (DFF) columns and the concurrent program context columns.

• PERSON_TYPE_USAGE_ID — Primary key of the person type usage record.
• PERSON_ID — Foreign key to the person (worker, applicant, etc.) to whom the type usage applies.
• PERSON_TYPE_ID — Foreign key to the person type being assigned (e.g., Employee, Applicant).
• EFFECTIVE_START_DATE, EFFECTIVE_END_DATE — The date-effective range; the view returns rows where the session effective date falls within this range.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle Applications Framework.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — Standard WHO audit columns.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1…ATTRIBUTE20 — Descriptive flexfield segments for customer-defined attributes.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program audit context identifying the process that last modified the row.

Common Use Cases and Queries

Typical uses include worker-type reporting, integration extracts, and validation in HRMS customization. Because the view is session-dated, queries naturally return the "as of" record for the current session's effective date without extra filtering.

Listing active person type usages for a person:

SELECT person_type_usage_id, person_id, person_type_id, effective_start_date, effective_end_date FROM apps.per_person_type_usages WHERE person_id = :p_person_id;

Joining to person types to classify the current population:

SELECT pptu.person_id, ppt.system_person_type, ppt.user_person_type FROM apps.per_person_type_usages pptu, apps.per_person_types_vl ppt WHERE pptu.person_type_id = ppt.person_type_id AND pptu.person_id = :p_person_id;

Identifying new hires in a period:

SELECT person_id, person_type_id, effective_start_date FROM apps.per_person_type_usages WHERE person_type_id = :p_employee_type_id AND effective_start_date BETWEEN :p_start AND :p_end ORDER BY effective_start_date;

To retrieve historical rows outside the session date, query the base table PER_PERSON_TYPE_USAGES_F directly or use the DateTrack-aware APIs.