Search Results aged_type




Overview
Explore in AI Chat

Overview

PAY_JP_DEF_EMP_V is an Oracle E-Business Suite view owned by the APPS schema and defined within the PAY (Payroll) product family. As documented in the ETRM metadata for release 12.2.2, the object carries a VALID status and is described explicitly as a view used for Japanese localization only. Its functional scope is therefore restricted to the Japanese statutory reporting and employee information requirements that Oracle delivers as part of the Japan-specific payroll localization.

The view exposes a filtered projection of declarative employee information associated with assignment action processing. It is not a general-purpose HR view; instead, it surfaces records whose action context type is 'AAP' and whose action information category is 'JP_DEF_EMP'. This filter constrains the result set to Japan declarative employee action information captured through the assignment action framework. In reporting and integration terms, the view serves as a stable, read-only interface for extracting localized employee attributes — including kana name renderings, household head details, and various statutory status flags — without requiring the consumer to navigate the underlying declarative DML structures directly.

Underlying Base Objects

The view is defined over PAY_JP_DEF_EMP_DML_V, itself a view in the APPS schema that provides the DML-capable presentation of Japan declarative employee data. PAY_JP_DEF_EMP_V selects from PAY_JP_DEF_EMP_DML_V and applies the two constant predicates noted above, effectively converting the DML view into a read-only reporting view.

Two Oracle Application Object Library packages are referenced in the select list and are essential to the view's type handling. FND_DATE is invoked through its CANONICAL_TO_DATE function to convert stored canonical date strings into proper DATE values for DATE_OF_BIRTH, DATE_OF_DEATH, and CHANGE_DATE. FND_NUMBER is invoked through CANONICAL_TO_NUMBER to convert the canonical representation of HOUSEHOLD_HEAD_CTR_ID into a numeric value. Consumers should be aware that these conversions occur at query time and depend on the FND_DATE and FND_NUMBER package specifications being valid in the database.

Key Columns

The view returns a broad set of employee and declarative action attributes. The primary keys and context columns include ROW_ID, ACTION_INFORMATION_ID, OBJECT_VERSION_NUMBER, ASSIGNMENT_ACTION_ID, ASSIGNMENT_ID, EFFECTIVE_DATE, ACTION_CONTEXT_TYPE, and ACTION_INFORMATION_CATEGORY; the latter two are always 'AAP' and 'JP_DEF_EMP' respectively for rows returned by this view.

Common Use Cases and Queries

Typical usage centers on Japanese payroll and statutory reporting, where the CHANGE_REASON column is frequently used to audit why an employee's declarative status was amended. A representative query listing declarative changes with their reasons is:

SELECT assignment_id, effective_date, change_date, change_reason, married_flag FROM apps.pay_jp_def_emp_v WHERE change_reason IS NOT NULL ORDER BY change_date DESC;

Other common patterns include extracting kana names for statutory filings, enumerating employees by disability, aged, widow, or working-student status, and retrieving household head information for dependent-related reporting. Because the view is read-only and pre-filtered to the Japan declarative employee category, it is well suited to concurrent program data sources, BI Publisher reports, and inbound integration extracts that must not see unrelated action information rows.