Search Results xassignment_action_id




Overview
Explore in AI Chat

Overview

PAY_KR_SEP_TAX_WO_ADDR_V is an APPS-owned database view within the Oracle EBS Payroll (PAY) product module, delivered as a valid object in both release 12.1.1 and 12.2.2. Its name indicates its function: a Korean (KR) separation tax reporting view ("SEP_TAX") rendered "without address" ("WO_ADDR"), meaning it exposes the separation tax data set while omitting the business place address concatenation that sibling views include. The view is designed to support Korean statutory separation payment reporting, where terminated employees' severance and retirement income must be declared to tax authorities with reference to the business place (BP) and the responsible tax office.

The view consolidates payroll run context, assignment actions, employee personal data, element entry results, business place organization attributes, corporate representative details, and territory lookups into a single flattened row per assignment action. This makes it suitable for concurrent program reports, XML Publisher data templates, and custom extracts where the report layout supplies address information from an external source rather than from the view itself.

Underlying Base Objects

The view is defined over a mixture of payroll, human resources, and lookup objects. Documented base objects include PAY_ASSIGNMENT_ACTIONS, PAY_PAYROLL_ACTIONS, PAY_ACTION_INTERLOCKS, PAY_ELEMENT_ENTRIES_F, PAY_ELEMENT_ENTRY_VALUES_F, PAY_ELEMENT_LINKS_F, PAY_ELEMENT_TYPES_F, PAY_INPUT_VALUES_F, PAY_LINK_INPUT_VALUES_F, and PAY_RUN_TYPES_F. Employee and assignment attributes derive from PER_ASSIGNMENTS_F, PER_PEOPLE_F, PER_PERIODS_OF_SERVICE, HR_ORGANIZATION_UNITS, HR_ORGANIZATION_INFORMATION, HR_LOCATIONS, and FND_TERRITORIES_VL.

The view also invokes PL/SQL packages rather than relying solely on joins: PAY_KR_REPORT_PKG supplies result values for numeric and date inputs (for example non-taxable earnings and hiring/leaving dates), PAY_KR_SEP_FORM_PKG supplies Korean address formatting routines, and HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY provide person-name and security predicates. The tax-unit and corporate-header columns are sourced from HR_ORGANIZATION_INFORMATION aliased as BHOI, CHOI, and THOI — business place, corporation, and tax office organization records respectively.

Key Columns

Identity and run context columns include BUSINESS_GROUP_ID, PAYROLL_ID, ASSIGNMENT_ID, ASSIGNMENT_ACTION_ID, PAYROLL_ACTION_ID, RUN_TYPE_ID, and RUN_TYPE_NAME. The date columns EFFECTIVE_DATE, DATE_EARNED, and XEFFECTIVE_DATE establish the temporal basis of the separation record; the X-prefixed columns XEFFECTIVE_DATE, XASSIGNMENT_ACTION_ID, and XPAYROLL_ACTION_ID follow the ETRM convention for alternate or archive-linked run identifiers. This is directly relevant to the "xeffective_date" search that surfaced this view.

Tax and identification columns include TAX_UNIT_ID, PREV_ELEMENT_ENTRY_ID, and the business place attributes BP_NUMBER (ORG_INFORMATION2), CORP_NAME, CORP_REPRESENTATIVE_NAME, and CORP_NUMBER drawn from HR_ORGANIZATION_INFORMATION. Employee columns include LAST_NAME, FIRST_NAME, NATIONAL_IDENTIFIER, and NATIONALITY. Report package calls return PREV_BP_NUMBER, PREV_BP_NAME, PREV_SEP_PAY, PREV_SEP_INS, PREV_SP_SEP_ALW, and PREV_SP_NON_TAX_AMT, representing prior-period separation pay, insurance, allowances, and non-taxable earnings used to reconcile cumulative separation income. WKPD result dates provide HIRING_DATE, LEAVING_DATE, PREV_FIRST_HIRING_DATE, and PREV_LAST_LEAVING_DATE.

Common Use Cases and Queries

Typical uses include Korean severance tax declaration reports, year-end adjustment verification, and reconciliation of prior-period separation payments against current assignment actions. The following query retrieves separation records for a business group restricted by effective date:

  • SELECT assignment_id, assignment_action_id, effective_date, xeffective_date, date_earned, bp_number, last_name, first_name, prev_sep_pay FROM apps.pay_kr_sep_tax_wo_addr_v WHERE business_group_id = :p_bg_id AND effective_date BETWEEN :p_start AND :p_end;
  • SELECT payroll_action_id, payroll_id, run_type_name, tax_unit_id, corp_name, corp_number FROM apps.pay_kr_sep_tax_wo_addr_v WHERE assignment_action_id = :p_aa_id;
  • SELECT h.xeffective_date, h.prev_sep_pay, h.prev_sp_non_tax_amt, h.leaving_date FROM apps.pay_kr_sep_tax_wo_addr_v h WHERE h.national_identifier = :p_nid AND h.business_group_id = :p_bg_id ORDER BY h.xeffective_date DESC;

Because the view calls PL/SQL functions per row, performance-intensive extracts should filter by ASSIGNMENT_ACTION_ID or BUSINESS_GROUP_ID and date range before aggregation. The view is subject to HR_SECURITY predicates through the underlying HR package calls, so results are constrained by the querying user's security profile.