Search Results bassignment_action_id




Overview
Explore in AI Chat

Overview

PAY_KR_SEP_RESULT_SLIP_YB_V is a payroll reporting view owned by the APPS schema within the Oracle E-Business Suite Payroll (PAY) product. The view is registered as VALID in ETRM 12.2.2 and is also present in 12.1.1, where it is used to support the Korean localization of Separation Pay Slips. Its specific purpose is to return the result value associated with Subjected Yearly Bonus amounts that form part of a separation pay calculation.

The view is centered on the concept of an assignment_action_id. This identifier corresponds to a single processing instance of a payroll action for a given assignment. The view correlates a current separation processing action with each prior bonus processing action for the same assignment that falls within a trailing twelve-month window. In this way, it surfaces the historical yearly bonus earnings that are subject to averaging for separation pay purposes. The view is read-only and is consumed by reporting logic and by the PAY_KR_REPORT_PKG package rather than being used for transactional writes.

Underlying Base Objects

The view is defined over several standard Payroll synonyms and one package. The documented referenced base objects are:

PAY_ASSIGNMENT_ACTIONS is joined to PAY_PAYROLL_ACTIONS to obtain effective dates and date-earned values. A self-join pattern links the primary assignment action (PAA) to a bonus assignment action (BPAA) on assignment_id, restricted so that the bonus action sequence is earlier than the separation action sequence and the bonus action status is 'C' (completed). PAY_RUN_TYPES_F and its translation table PAY_RUN_TYPES_F_TL supply run type names, filtered so that the run type name begins with 'BON' and excludes 'BON_ALR'. An EXISTS subquery over PAY_RUN_RESULT_VALUES, PAY_RUN_RESULTS, and PAY_BALANCE_FEEDS_F confirms that a valid balance feed exists for the EARNINGS_SUBJ_AVG balance type within the relevant effective-date interval. The package PAY_KR_REPORT_PKG is invoked through the function GET_BALANCE_VALUE_ASG_RUN to derive the averaged subjected earnings value.

Key Columns

Common Use Cases and Queries

The principal use case is generating the yearly bonus component of a Korean separation pay slip. A reporting query typically filters on a specific assignment action to retrieve the contributing bonus periods and the computed average:

  • Retrieving all bonus rows supporting a given separation action: SELECT assignment_action_id, bassignment_action_id, beffective_date, brun_type_name, bearnings_subj_avg FROM apps.pay_kr_sep_result_slip_yb_v WHERE assignment_action_id = :p_assignment_action_id;
  • Reviewing all bonus contributions for an assignment before a separation action, joining on ASSIGNMENT_ID.
  • Auditing translated run type names by inspecting UBRUN_TYPE_NAME alongside BRUN_TYPE_NAME.

Because the view applies a twelve-month effective-date window and restricts bonus run types to those prefixed with 'BON', queries return only the qualifying prior bonus actions, which simplifies application logic and keeps separation pay calculations aligned with Korean statutory averaging rules.