Search Results pers_pension_saving

Overview

APPS.PAY_KR_TAX_EXEM_V is an Oracle E-Business Suite (EBS) view in the Oracle Payroll (PAY) application, purpose-built for the Korean localization of year-end tax adjustment (YEA) processing. The view exposes the tax exemption and pension-related information stored against employee assignments during the Korean YEA flow, deriving its data from the PER_ASSIGNMENT_EXTRA_INFO descriptive flexfield container. This view exists in both the 12.1.1 and 12.2.2 releases and is referenced through the standard APPS schema, placing it in the same namespace as other PAY KR tax and pension localization objects.

Functionally, the view acts as a decoded, presentation-ready projection of flexfield string data: numeric and date columns returned by the view are the result of runtime conversion functions rather than physical columns. It therefore serves as a reporting and integration interface rather than a transactional table. Because it filters the underlying data to the current FND session effective date context, the view returns only the tax exemption record matching the active payroll or GRE session year.

Underlying Base Objects

The view is defined over two referenced objects, with conversion logic supplied by two packaged functions:

• PER_ASSIGNMENT_EXTRA_INFO (accessed via synonym) — the physical descriptive flexfield store holding the KR_YEA_TAX_EXEM_INFO information type records. The view selects from this object aliased as AEI.
• FND_SESSIONS (accessed via synonym) — joined as FND to obtain the current session effective date, matched against USERENV('SESSIONID').
• FND_DATE (package) — supplies CANONICAL_TO_DATE, converting the stored canonical string in AEI_INFORMATION1 into a proper date.
• FND_NUMBER (package) — supplies CANONICAL_TO_NUMBER, converting the canonical numeric strings in AEI_INFORMATION2 through AEI_INFORMATION7 into numeric values.

The join predicate restricts rows to INFORMATION_TYPE = 'KR_YEA_TAX_EXEM_INFO', and the year component of the session effective date is matched to the leading four characters of AEI_INFORMATION1, ensuring the record returned corresponds to the active tax year.

Key Columns

• ROW_ID — the ROWID of the underlying PER_ASSIGNMENT_EXTRA_INFO row; the unique row identifier for the view.
• ASSIGNMENT_EXTRA_INFO_ID — primary key of the source flexfield row.
• ASSIGNMENT_ID — the assignment to which the tax exemption data belongs.
• INFORMATION_TYPE — the flexfield context value (KR_YEA_TAX_EXEM_INFO).
• AEI_INFORMATION_CATEGORY — the descriptive flexfield structure category.
• OBJECT_VERSION_NUMBER — optimistic locking version for the source row.
• EFFECTIVE_DATE — date derived from AEI_INFORMATION1, representing the effective date of the tax exemption record and used for year matching.
• NP_PREM — national pension premium amount, from AEI_INFORMATION2.
• PERS_PENSION_PREM — personal (employee) pension premium amount, from AEI_INFORMATION3. This is the column most frequently targeted by the user search term "pers_pension_prem".
• PERS_PENSION_SAVING — personal pension savings amount, from AEI_INFORMATION4.
• INVEST_PARTNERSHIP_FIN1 and INVEST_PARTNERSHIP_FIN2 — investment partnership figures, from AEI_INFORMATION5 and AEI_INFORMATION6.
• CREDIT_CARD_EXP — credit card expenditure amount used in tax exemption computation, from AEI_INFORMATION7.

Common Use Cases and Queries

The view is typically queried during Korean year-end tax reporting, payroll auditing, and integration exports. A representative query retrieving the personal pension premium for a given assignment is:

• SELECT assignment_id, effective_date, pers_pension_prem, np_prem FROM apps.pay_kr_tax_exem_v WHERE assignment_id = :p_assignment_id;
• SELECT assignment_id, pers_pension_prem, pers_pension_saving, credit_card_exp FROM apps.pay_kr_tax_exem_v WHERE substr(to_char(effective_date,'YYYY'),1,4) = :p_tax_year;

Because the view is session- and effective-date dependent, it returns the record relevant to the currently initialized FND session. Consumers should therefore invoke it within a properly initialized EBS session context rather than through an unauthenticated database connection, ensuring the session effective date aligns with the intended tax year.