Results for “effective_end_date”

50+ results




Overview
Explore in AI Chat

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

Overview

PA_XLA_EMPLOYEE_REF_V is a public APPS-schema view owned by the Oracle Projects (PA) product family and delivered as a standard component of Oracle E-Business Suite 12.1.1 and 12.2.2. Its purpose is to expose a simplified, denormalized reference set of employee attributes that support Oracle Subledger Accounting (XLA) processing within Projects. The "XLA" prefix in the name identifies it as a supporting reference object for the Projects subledger accounting engine, where employee identity, name, and person-type information are required to derive accounting events, build journal entries, and satisfy audit and reconciliation requirements. The view presents a filtered projection of the PA_EMPLOYEES view, returning only the columns commonly needed for employee-based references rather than the full set of employee attributes. Because subledger accounting flows must resolve the "who" behind labor, burden, and expense transactions, this view provides a stable and lightweight access point that avoids repeated joins to the broader HR employee structures. In ETRM, the object is documented with status VALID in the APPS schema.

Underlying Base Objects

The view text is defined directly over PA_EMPLOYEES, itself a Projects view built on Human Resources (HR) person and assignment data. The documented ETRM dependency list for PA_XLA_EMPLOYEE_REF_V identifies the following referenced objects:

  • PA_EMPLOYEES (VIEW) — the direct source from which all returned columns are selected.
  • HR_GENERAL (PACKAGE) — provides HR utility functions used in resolving person and business-group level attributes.
  • HR_PERSON_NAME (PACKAGE) — supplies the logic that formats a person's full name consistently with HR name conventions.
  • HR_SECURITY (PACKAGE) — enforces HR security (person/assignment-level access) so that only employees visible to the querying responsibility are returned.

Because the view ultimately depends on HR_SECURITY, results are subject to HR security profiles; a user may not see every row present in the underlying table depending on their assigned security profile. This behavior is consistent with other Projects employee-facing views.

Key Columns

The view exposes six columns. The primary keys and descriptive attributes are:

  • PERSON_ID — the unique identifier of the person in the HR person model. This is the primary join key to HR and Projects tables.
  • EMPLOYEE_NUMBER — the user-visible employee number assigned in HR, used in reporting and reconciliation.
  • EMPLOYEE_NAME — the formatted full name of the employee, derived from HR name logic. The ETRM column list labels this column EMPLOYEE_NAME, while the view text selects FULL_NAME from PA_EMPLOYEES; the underlying value is the person's full name.
  • PERSON_TYPE — the classification of the person (for example, Employee, Contingent Worker, or other person types defined in HR). Since the user searched for "person_type," this is the column of primary interest. It reflects the person type as carried in PA_EMPLOYEES and is critical for distinguishing employees from non-employees in accounting logic.
  • EFFECTIVE_START_DATE — the start of the effective date range for which the employee record applies.
  • EFFECTIVE_END_DATE — the end of the effective date range; the record is current when the effective end date is open or in the future.

Common Use Cases and Queries

The view is typically used in subledger accounting and Projects reporting to look up an employee's name and person type by PERSON_ID, or to filter the employee population by person type. A typical query retrieving employees of a specific person type is:

  • SELECT person_id, employee_number, employee_name, person_type, effective_start_date, effective_end_date FROM apps.pa_xla_employee_ref_v WHERE person_type = :p_person_type;
  • SELECT x.person_id, x.employee_name, x.person_type FROM apps.pa_xla_employee_ref_v x WHERE x.person_id = :p_person_id;
  • Joining to Projects labor or expenditure lines on PERSON_ID to supply the person type required for XLA accounting event and journal line definitions.

Because records are effective-dated, queries intended to return only current employees should restrict on the effective date range, as shown above, and developers should account for HR security when validating that expected rows are returned.