Search Results sp_irreg_bonus




Overview
Explore in AI Chat

Overview

APPS.PAY_KR_YER_PREV_ER_V is a reporting view in Oracle E-Business Suite (12.1.1 / 12.2.2) that exposes prior-employer year-end earnings information for Korean payroll processing. Its name encodes its purpose: PAY (Payroll), KR (Korea localization), YER (Year-End Reporting), and PREV_ER (Previous Employer). The view is a thin, denormalized projection over the descriptive flexfield-style extra information captured on employee assignments, converting stored character values into typed dates and numbers for downstream reporting.

The view plays a specific role in the Korean Year-End Tax Settlement (YEA) process. Where an employee joins mid-year, earnings and bonuses paid by a prior employer must be declared and aggregated with current-year figures for correct year-end tax adjustment. This view supplies those prior-employer figures — termination date, business partner details, and taxable earnings components — in a form suitable for concurrent programs, BI Publisher reports, and interfaces.

Underlying Base Objects

The view is defined over three documented base objects:

The view is unfiltered except for one predicate: aei.information_type = 'KR_YEA_PREV_ER_INFO'. This isolates the Korean year-end prior-employer extra information type from all other assignment extra information records, so consumers receive only relevant rows. No joins to PER_ASSIGNMENTS or PER_ALL_PEOPLE_F are performed inside the view; those joins are left to the calling query.

Key Columns

Common Use Cases and Queries

Typical usage includes feeding Korean year-end tax reports, validating prior-employer declarations, and reconciling total taxable income. A query retrieving prior-employer data for an assignment:

  • SELECT assignment_id, bp_name, bp_number, termination_date, taxable_total FROM apps.pay_kr_yer_prev_er_v WHERE assignment_id = :p_assignment_id;
  • Joining to assignments and people for a listing by employee number or name.
  • Summarizing taxable totals per business partner for a reporting period.

Note that all numeric and date columns are delivered already converted and typed, so no additional FND_NUMBER / FND_DATE wrapping is required by the consumer.