Search Results pay_kr_emp_v




Overview
Explore in AI Chat

Overview

PAY_KR_EMP_V is a payroll (PAY) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to return employee and applicant information resolved against the current session date. Rather than exposing a raw assignment or person record, the view applies a date-aware filter driven by FND_SESSIONS, so that each row reflects the state of the person and assignment effective on the session's effective date. It is therefore a point-in-time reporting view for Oracle Payroll (Korean localization, as indicated by the PAY_KR prefix), typically consumed by concurrent programs, BI Publisher reports, and statutory extracts that must reflect the exact date the user signed in.

The view is validated and retains a VALID status in the ETRM data dictionary. It joins person, assignment, and organization information into a single denormalized projection, and it derives two calculated attributes — date of birth and age — from the national identifier using the PAY_KR_FF_FUNCTIONS_PKG package. Because the caller never needs to supply a date predicate, PAY_KR_EMP_V is convenient for self-service and batch reporting where the session date is the intended as-of date.

Underlying Base Objects

The view is defined over the following documented objects: FND_SESSIONS (synonym), HR_ALL_ORGANIZATION_UNITS_TL (synonym), HR_ORGANIZATION_UNITS (view), PER_ASSIGNMENTS_F (view), PER_PEOPLE_F (view), PER_PERSON_TYPES (synonym), and the packages PAY_KR_FF_FUNCTIONS_PKG, HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY.

The primary join links PER_PEOPLE_F (PP) to PER_ASSIGNMENTS_F (PA) on PERSON_ID, with both date-tracked (F) entities constrained so that the session effective date falls between their effective start and end dates. HR_ORGANIZATION_UNITS (HOU) is outer-joined via ESTABLISHMENT_ID to supply the business place, with HR_ALL_ORGANIZATION_UNITS_TL (HOUTL) providing the translated organization name. PER_PERSON_TYPES (PPT) supplies the system person type. The session date and ID are drawn from FND_SESSIONS using USERENV('SESSIONID').

Key Columns

Common Use Cases and Queries

The view is typically used to list active employees and applicants for a session, to validate Korean national identifier data, and to feed age- or identifier-based eligibility logic. A filtered lookup on applicant number would take the form:

SELECT assignment_number, applicant_number, full_name, national_identifier, date_of_birth, age FROM apps.pay_kr_emp_v WHERE applicant_number = :p_applicant_number;

A broader roster query, restricted to current employees, might read:

SELECT employee_number, full_name, business_place_name, system_person_type FROM apps.pay_kr_emp_v WHERE current_employee_flag = 'Y' ORDER BY full_name;

Because every result set depends on the effective date recorded for the current session in FND_SESSIONS, results are not static across sessions and should not be treated as a stable historical snapshot without an explicit date context.