Search Results internal_location




Overview
Explore in AI Chat

Overview

The OKX_EMPLOYEES_V view is a public synonym owned by the APPS schema and is shipped as part of the OKX – Contracts Integration module in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented status is VALID. The view exposes a flattened, integration-oriented projection of employee data drawn from Oracle Human Resources (PER), and is intended to present person records in the shape expected by the Contracts Integration layer rather than to serve as a general-purpose HR reporting view.

The defining characteristic of the view is its column naming: rather than exposing pure HR column names, it aliases or reshapes them into generic identifiers such as NAME, DESCRIPTION, START_DATE_ACTIVE, END_DATE_ACTIVE, and STATUS, which are typical of interface views used to populate or validate contract-related data. Users who search for the string "internal_location" encounter this view because INTERNAL_LOCATION is one of the columns projected from the underlying person record.

Underlying Base Objects

The documented base object is a single table, referenced by synonym:

  • PER_ALL_PEOPLE_F — the datetracked, effective-dated person/employee entity in Oracle Human Resources.

The view is defined over this table with no joins to other PER entities. Because PER_ALL_PEOPLE_F is a date-tracked (_F) table, the view inherits effective-dated behavior: each physical row represents a person record valid between EFFECTIVE_START_DATE and EFFECTIVE_END_DATE. The view does not itself filter by current date; therefore callers must constrain the effective dates if they require only presently active records. This is a critical consideration, since unfiltered queries against the view may return multiple historical rows per person.

Key Columns

The principal columns exposed by the view are:

  • NAME — mapped from EMP.FULL_NAME; the concatenated employee display name.
  • EMPLOYEE_NUMBER — mapped from EMP.EMPLOYEE_NUMBER; the unique employee identifier.
  • LAST_NAME / FIRST_NAME — component name attributes carried through from the base table.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — mapped from the effective start and end dates of the person row.
  • START_DATE — the person's original hire/start date, distinct from both effective dates.
  • EMAIL_ADDRESS — the person's email attribute.
  • INTERNAL_LOCATION — the person's internal office or location designation, the column most directly relevant to searches for "internal_location."
  • STATUS — a derived column computed by decoding the effective dates against SYSDATE, returning 'I' (inactive) when the record is outside its effective window and 'A' (active) otherwise.
  • BUSINESS_GROUP_ID / PERSON_TYPE_ID — HR key identifiers retained for filtering and joins.
  • DESCRIPTION, SMALL_BUSINESS_FLAG, WOMEN_OWNED_FLAG, MINORITY_GROUP_LOOKUP — NULL placeholders included to satisfy the expected interface shape; they carry no data.

Common Use Cases and Queries

The view is typically consumed by Contracts Integration routines that need a lightweight employee list keyed by name, employee number, and location. Reported queries commonly constrain INTERNAL_LOCATION or select currently effective rows only.

Example: list currently active employees with their location.

  • SELECT employee_number, name, internal_location, email_address FROM apps.okx_employees_v WHERE status = 'A';

Example: filter by a specific internal location.

  • SELECT employee_number, name, internal_location FROM apps.okx_employees_v WHERE status = 'A' AND internal_location = :p_location;

Example: resolve a person by employee number.

  • SELECT person_id, name, start_date_active, internal_location FROM apps.okx_employees_v WHERE employee_number = :p_emp_num;

Because the view is built over an effective-dated entity, the STATUS derivation should generally be used as the primary filter, supplemented by explicit effective date bounds where point-in-time accuracy is required.