Search Results fa_employees




Overview
Explore in AI Chat

Overview

FA_EMPLOYEES is a read-only database view owned by the APPS schema in Oracle E-Business Suite, registered under the Oracle Assets (OFA) product. Its documented purpose is to present employee records together with termination information, allowing Oracle Assets functionality and dependent reporting to resolve the identity of an employee and the date on which that employee's period of service ended. The view is designated VALID and is available in both the 12.1.1 and 12.2.2 release lines as documented in the E-Business Suite Technical Reference Manual (ETRM).

Within the Assets module, the view acts as a simplified, denormalized projection over Oracle Human Resources (PER) data rather than as a transactional entity. It exposes only four columns and does not contain any Assets-specific attributes such as asset assignments, depreciation books, or employee-to-asset relationships. Its role is therefore that of a lookup and reporting convenience layer: consumers receive a compact set of person identifiers, the employee number, the formatted name, and the actual termination date, without needing to join directly to the PER schema objects or to account for the date-tracked structure of the underlying tables. This makes the view suitable for use in Assets reports, concurrent program logic, and third-party integrations that must determine whether a person was still an active employee at a given point in time.

Underlying Base Objects

The documented view text selects from two base objects: PER_PERIODS_OF_SERVICE (referenced through a synonym) and PER_PEOPLE_X (a view). The join is an equi-join on PERSON_ID, and the ETRM lists the following referenced base objects: HR_GENERAL (package), HR_PERSON_NAME (package), HR_SECURITY (package), PER_PEOPLE_X (view), and PER_PERIODS_OF_SERVICE (synonym).

The relationship between the view and these objects is important for interpretation. PER_PERIODS_OF_SERVICE is the HR table that stores periods of service for employees and applicants, including the ACTUAL_TERMINATION_DATE column surfaced by the view. PER_PEOPLE_X is a person-level view that provides PERSON_ID, EMPLOYEE_NUMBER, and FULL_NAME. The three HR packages are not selected from directly; they are referenced because PER_PEOPLE_X and the other PER objects depend on them. HR_GENERAL supplies core HR business logic, HR_PERSON_NAME governs name formatting (which is why the view can expose a pre-formatted NAME column), and HR_SECURITY enforces row-level security so that a query against FA_EMPLOYEES returns only those persons the querying user is authorized to see. Because PER_PEOPLE_X carries a trailing "_X" suffix, it is a date-tracked view; the join to PER_PERIODS_OF_SERVICE can therefore return multiple rows for a person with multiple periods of service.

Key Columns

  • EMPLOYEE_ID — the PERSON_ID from PER_PEOPLE_X, aliased as EMPLOYEE_ID. This is the primary person identifier and is the value typically stored on Assets records that reference employees.
  • EMPLOYEE_NUMBER — the employee number assigned in HR, carried through from PER_PEOPLE_X. It is the human-readable identifier commonly used in listings and reports.
  • NAME — the full name from PER_PEOPLE_X, aliased as NAME. Because the source is an HR person view, the value reflects HR name-formatting rules rather than a raw database column.
  • ACTUAL_TERMINATION_DATE — the actual termination date from PER_PERIODS_OF_SERVICE. A null value indicates that no period of service has recorded an actual termination, i.e., the person has not been terminated as of the query.

Common Use Cases and Queries

The principal use case is identifying terminated versus active employees when reporting or reconciling Assets data. A typical query filters on the termination date to isolate employees who have left:

  • SELECT employee_id, employee_number, name, actual_termination_date FROM apps.fa_employees WHERE actual_termination_date IS NOT NULL ORDER BY actual_termination_date DESC;
  • SELECT employee_id, employee_number, name FROM apps.fa_employees WHERE actual_termination_date IS NULL AND employee_number = :employee_number;
  • SELECT e.employee_number, e.name, a.* FROM apps.fa_employees e, apps.fa_employee_assignments a WHERE e.employee_id = a.employee_id; (illustrative join to Assets assignment data)

Note that because the view joins to PER_PERIODS_OF_SERVICE, employees with more than one period of service may appear more than once, so consumers requiring one row per person should aggregate or filter to the relevant period. Direct DML against FA_EMPLOYEES is not supported; the view is intended for query and reporting only, and access is filtered automatically by the HR security model applied through the referenced HR packages.