Search Results kr_c

Overview

APPS.PAY_KR_SEP_TAX_V is an Oracle E-Business Suite internal database view owned by the APPS schema and registered under FND Design Data as PAY.PAY_KR_SEP_TAX_V. It is a Korea-localized separation tax reporting view that consolidates payroll action, assignment, element entry, and person/employer information required for severance and separation tax reporting. The view is marked VALID and is classified as an Internal view type with the Oracle advisory that it is for Oracle Internal Use Only; Oracle does not support direct access to applications data through this object except from standard Oracle Applications programs.

Functionally, PAY_KR_SEP_TAX_V presents a flattened, report-ready rowset assembled from payroll actions, assignment actions, run type attributes, tax unit data, and employee/employer address detail. It also carries an explicit reference to the prior element entry via the PREV_ELEMENT_ENTRY_ID column, which supports the reconciliation of prior-period separation entries against the current reporting row. This makes the view a staging layer for Korean severance tax extracts and statutory reports rather than a general-purpose payroll inquiry object.

Underlying Base Objects

The view is defined over the following documented referenced objects:

• PAY_KR_SEP_TAX_WO_ADDR_V (VIEW) — the Korea separation tax view without address detail, providing the payroll/assignment/tax core columns.
• PER_ADDRESSES (SYNONYM) — supplies person address data surfaced through PERSON_ADDRESS and related address columns.
• HR_GENERAL (PACKAGE), HR_PERSON_NAME (PACKAGE), HR_SECURITY (PACKAGE) — used to resolve business group context, formatted person names, and security-filtered access to person and assignment records.
• PAY_KR_REPORT_PKG (PACKAGE) and PAY_KR_SEP_FORM_PKG (PACKAGE) — Korean payroll reporting and separation form packages supplying derived amounts and report formatting logic.

The dependency chain confirms that the view inherits its business logic from the Korea separation form and report packages, with the address-free separation view acting as the immediate structural parent.

Key Columns

• BUSINESS_GROUP_ID, PAYROLL_ID, ASSIGNMENT_ID, ASSIGNMENT_ACTION_ID, PAYROLL_ACTION_ID — core payroll/assignment identifiers linking the row to its source action.
• EFFECTIVE_DATE, DATE_EARNED, XEFFECTIVE_DATE — effective dating for the payroll action and the separation event.
• RUN_TYPE_ID, RUN_TYPE_NAME — identifies the payroll run type that produced the separation entry.
• TAX_UNIT_ID — the Korean tax reporting unit associated with the row.
• PREV_ELEMENT_ENTRY_ID — the identifier of the prior element entry, used when reconciling prior separation or severance entries against the current row; this is the column most frequently searched by users.
• PREV_BP_NUMBER, PREV_BP_NAME, PREV_SEP_PAY, PREV_SEP_INS, PREV_SP_SEP_ALW, PREV_SP_NON_TAX_AMT — prior-period business place and separation pay/insurance/allowance/non-taxable amounts.
• BP_NUMBER, CORP_NAME, CORP_REPRESENTATIVE_NAME, CORP_NUMBER, BP_ADDRESS, TAX_OFFICE_NAME — employer/business place and tax office detail.
• LAST_NAME, FIRST_NAME, NATIONAL_IDENTIFIER, PERSON_ADDRESS, NATIONALITY — person identity and address information.
• HIRING_DATE, LEAVING_DATE, PREV_FIRST_HIRING_DATE, PREV_LAST_LEAVING_DATE, ACTUAL_TERMINATION_DATE — employment and termination dates.
• COUNTRY_CODE, COUNTRY, PERSON_ID, SEP_PAY_OVERSEAS_TAX_BREAK, NON_STAT_SEP_OVERSEAS_TAX_BRK — country context and overseas tax break amounts.

Common Use Cases and Queries

Typical usage is reconciliation and statutory reporting for Korean severance tax, including review of prior element entries and overseas tax break amounts. A representative query locating rows by prior element entry is:

• SELECT business_group_id, assignment_id, payroll_action_id, prev_element_entry_id, prev_sep_pay, bp_number FROM apps.pay_kr_sep_tax_v WHERE prev_element_entry_id = :p_element_entry_id;
• SELECT assignment_id, date_earned, run_type_name, sep_pay_overseas_tax_break FROM apps.pay_kr_sep_tax_v WHERE business_group_id = :p_business_group_id AND effective_date BETWEEN :p_start AND :p_end;
• SELECT person_id, national_identifier, prev_bp_number, prev_sep_ins, actual_termination_date FROM apps.pay_kr_sep_tax_v WHERE tax_unit_id = :p_tax_unit_id;

Because the object is flagged for Oracle Internal Use Only, direct SQL access should be limited to diagnostic or reconciliation activity, with production reporting driven through the standard Oracle Applications programs that consume this view.