Results for “reason_code”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PAY_KR_SEP_HI_ADJ_V is an APPS-owned database view in the Oracle E-Business Suite Payroll (PAY) product, registered with VALID status in the ETRM repository for releases 12.1.1 and 12.2.2. The view supports the Korean statutory Health Insurance (HI) separation adjustment process, commonly referred to as the "Sep HI Adj" (Separation Health Insurance Adjustment) report. It consolidates employee separation data with establishment-level health insurance registration information so that payroll and benefits users can reconcile health insurance qualification and loss events against actual terminations.

The view is read-only and does not store data; it is a reporting and integration object typically consumed by concurrent programs, Oracle Reports, and custom extracts delivered for Korean localization compliance. Its role is to join person, assignment, period-of-service, and extra information records into a single denormalized result set suitable for statutory filing.

Underlying Base Objects

The documented ETRM base objects include HR_GENERAL (PACKAGE), HR_ORGANIZATION_INFORMATION (SYNONYM), HR_PERSON_NAME (PACKAGE), HR_SECURITY (PACKAGE), PER_ASSIGNMENTS_F (VIEW), PER_PEOPLE_EXTRA_INFO (SYNONYM), PER_PEOPLE_F (VIEW), and PER_PERIODS_OF_SERVICE (SYNONYM).

• PER_PEOPLE_F (PAP) — supplies person identifiers, names, national identifiers, and business group context.
• PER_PEOPLE_EXTRA_INFO (PPEI) — holds the Korean health insurance DFF values, filtered on INFORMATION_TYPE = 'PER_KR_HEALTH_INSURANCE_INFO'.
• PER_ASSIGNMENTS_F (PAA) — provides the ESTABLISHMENT_ID and ASSIGNMENT_ID linkage.
• PER_PERIODS_OF_SERVICE (PPS) — supplies ACTUAL_TERMINATION_DATE, which is the SEPARATION_DATE driving the record eligibility.
• HR_ORGANIZATION_INFORMATION (HOI1) — filtered on ORG_INFORMATION_CONTEXT = 'KR_HI_INFORMATION', returning the BP (business place) HI number from ORG_INFORMATION1.
• HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY are invoked indirectly for name formatting and row-level security enforcement.

The view text is a UNION ALL of two branches distinguished by the literal PERIOD column ('P' and 'C'), both projecting identical columns. Effective-dating predicates ensure the termination date falls within the effective ranges of PER_PEOPLE_F and PER_ASSIGNMENTS_F, and the termination is constrained to the calendar year of the separation.

Key Columns

• ESTABLISHMENT_ID — from PER_ASSIGNMENTS_F; the establishment (business place) used to join HR_ORGANIZATION_INFORMATION. This is the primary search term associated with the view.
• ASSIGNMENT_ID — the assignment for the terminated employee.
• HI_NUMBER — the health insurance number from PEI_INFORMATION1.
• EMPLOYEE_NAME — concatenation of LAST_NAME and FIRST_NAME.
• REGISTRATION_NUMBER — the national identifier of the person.
• QUALIFIED_DATE — NVL of PEI_INFORMATION4 and PEI_INFORMATION2 (qualification/loss date).
• SEPARATION_DATE — ACTUAL_TERMINATION_DATE from PERIODS_OF_SERVICE.
• REASON_CODE — PEI_INFORMATION3.
• PERIOD — literal 'P' or 'C' identifying the union branch.
• BP_HI_NUMBER — establishment-level HI number from HR_ORGANIZATION_INFORMATION.
• BUSINESS_GROUP_ID — partitioning/security attribute.

Common Use Cases and Queries

Typical usage is statutory reporting of employees who separated during a given year and require health insurance adjustment, constrained by establishment. A representative query:

• SELECT establishment_id, assignment_id, hi_number, employee_name, registration_number, qualified_date, separation_date, reason_code, period, bp_hi_number FROM pay_kr_sep_hi_adj_v WHERE establishment_id = :p_establishment_id AND separation_date BETWEEN :p_start AND :p_end;
• Establishment-based reconciliation: group by establishment_id and period to compare 'P' and 'C' branches.
• Extract for filing: filter on business_group_id and separation_date within the target calendar year.

Because the view relies on HR_SECURITY, query results are restricted by the caller's security profile; concurrent programs should therefore be run under a responsibility with adequate organization access.