Search Results mtl_employees_current_view




Overview
Explore in AI Chat

Overview

MTL_EMPLOYEES_CURRENT_VIEW is an APPS-owned Inventory (INV) view that presents the set of employees who are currently assigned to a given organization. Its definition resolves current, primary employee assignments by joining person, assignment, person type, and organization data, and restricting rows to those whose person and assignment effective date ranges encompass the system date. Because it reflects only assignments that are active "today," the view is well suited to point-in-time reporting rather than historical analysis.

The view is commonly consumed by Oracle Inventory and related modules as a lookup source for personnel associated with a warehouse, subinventory, or business group. Report developers and integrators use it wherever a validated list of active employees is required, for example when populating LOVs, attributing transaction activity to a person, or resolving an employee's default accounting flexfield. The view exposes the employee's default code combination, which is the attribute most often sought by users searching for default_code_combination_id.

Underlying Base Objects

The documented base objects referenced by MTL_EMPLOYEES_CURRENT_VIEW include PER_PEOPLE_X, PER_ASSIGNMENTS_X, PER_PERSON_TYPES, and HR_ORGANIZATION_UNITS. Supporting packages and views also participate through column derivation and security, namely HR_GENERAL, HR_PERSON_NAME, HR_SECURITY, and the PER_PERSON_TYPES synonym.

  • PER_PEOPLE_X — supplies person-level attributes such as person_id, employee_number, full_name, and the descriptive attributes (ATTRIBUTE1–20).
  • PER_ASSIGNMENTS_X — supplies assignment-level attributes including assignment_id, location_id, supervisor_id, set_of_books_id, and the default code combination.
  • PER_PERSON_TYPES — used to derive the system person type for employee classification.
  • HR_ORGANIZATION_UNITS — provides the business group / organization context used in the join.
  • HR_SECURITY — enforces organizational security so that only authorized employees are visible.
  • HR_GENERAL and HR_PERSON_NAME — resolve derived values such as formatted names.

Joins are conditioned on person-to-assignment matching, business group equivalence, a primary assignment flag of 'Y', assignment type 'E' (employee), and the SYSDATE effective-date tests on both person and assignment.

Key Columns

The view projects a broad set of columns, several of which are frequently referenced in reporting and integration logic.

Common Use Cases and Queries

Typical scenarios include listing active employees in an organization, retrieving an employee's default accounting combination, and joining employee data to inventory transactions or requisitions. Because the view already enforces effective-date logic and primary assignment filtering, queries remain concise.

To retrieve employees for a specific organization:

  • SELECT employee_num, full_name, supervisor_id FROM mtl_employees_current_view WHERE organization_id = :org_id;

To obtain the default code combination for a given employee:

  • SELECT employee_id, default_code_combination_id FROM mtl_employees_current_view WHERE employee_num = :emp_number;

To join to accounting definitions for description reporting:

  • SELECT e.full_name, gcc.concatenated_segments FROM mtl_employees_current_view e, gl_code_combinations_kfv gcc WHERE e.default_code_combination_id = gcc.code_combination_id AND e.organization_id = :org_id;