Search Results h_date




Overview
Explore in AI Chat

Overview

APPS.PAY_KR_SEP_HISTORY_V is a Korean localization view within Oracle E-Business Suite Payroll that consolidates separation history information for employees processed through the Korean severance (SEP) payroll run types. The view exposes the results of separation-related payroll actions, including the underlying severance date attributes that drive Korean statutory severance calculations. It is primarily consumed by Oracle Payroll reporting, statutory reporting forms, and downstream data extraction routines that require a denormalized, person-and-assignment-oriented projection of separation events. Because it joins multiple payroll action layers (payroll actions, assignment actions, and assignments) with person records, it permits reporting tools to present one row per separation-related assignment action with fully resolved descriptive attributes.

Underlying Base Objects

The view is defined over several base objects: the synonyms PAY_PAYROLL_ACTIONS, PAY_ASSIGNMENT_ACTIONS, PAY_RUN_TYPES_F, and PAY_ACTION_INTERLOCKS; the views PER_PEOPLE_F and PER_ASSIGNMENTS_F for person and assignment data; and the packages PAY_ASSIGNMENT_ACTIONS_PKG, PAY_KR_REPORT_PKG, PAY_KR_SEP_FORM_PKG, HR_GENERAL, HR_PAYROLLS, HR_PERSON_NAME, and HR_SECURITY, which supply derivation logic and security enforcement. The primary join links PAY_PAYROLL_ACTIONS to PAY_ASSIGNMENT_ACTIONS on PAYROLL_ACTION_ID, with person and assignment context provided by PER_PEOPLE_F and PER_ASSIGNMENTS_F. The view filters to separation-relevant action types only, requiring that the run type name match the 'SEP%' pattern, or that action type 'X' interlock conditions be satisfied. This restricts output to genuine severance run events rather than the full spectrum of payroll actions.

Key Columns

Common Use Cases and Queries

Typical usage includes extracting separation history for a business group, reporting severance dates for terminated employees, and validating that separation actions resolved to correct run types. The following query retrieves separation history including H_DATE:

  • SELECT person_id, full_name, employee_number, run_type_name, effective_date, h_date, l_date FROM apps.pay_kr_sep_history_v WHERE business_group_id = :p_bg AND effective_date BETWEEN :p_start AND :p_end;
  • Filtering by assignment_action_id to retrieve a single separation event’s attributes.
  • Joining to payroll result tables to reconcile H_DATE against stored severance period values.