Results for “per_jp_empdet_emp_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The PER_JP_EMPDET_EMP_V view is a Japanese localization view owned by the APPS schema in Oracle E-Business Suite, classified under the PER (Human Resources) product family. As documented, the view exists solely to support Japanese localization requirements. It presents a structured, filtered projection of payroll action information, exposing Japanese employee-level detail records that are stored within the generic PAY_ACTION_INFORMATION table in a canonical (character) form.

The view plays a reporting and integration role: it converts the canonical text stored in PAY_ACTION_INFORMATION into usable typed values by applying the FND_DATE.CANONICAL_TO_DATE and FND_NUMBER.CANONICAL_TO_NUMBER conversion functions. In this way, downstream reports, extracts, and interfaces receive properly typed dates and numbers rather than raw character strings. The view is marked VALID in the ETRM metadata and is available in both 12.1.1 and 12.2.2 environments.

Underlying Base Objects

The documented referenced base objects for this view are FND_DATE (PACKAGE), FND_NUMBER (PACKAGE), and PAY_ACTION_INFORMATION (SYNONYM). The view is defined entirely over PAY_ACTION_INFORMATION, aliased as PAI in the view text. Every column is sourced from this single table, with the exception of the conversions performed by the FND_DATE and FND_NUMBER packages.

The base table is filtered on two conditions: PAI.ACTION_CONTEXT_TYPE = 'AAP' and PAI.ACTION_INFORMATION_CATEGORY = 'JP_EMPDET_EMP'. The 'JP_EMPDET_EMP' category identifies the rows as Japanese employee detail information, while the 'AAP' context type distinguishes action-based assignment records. Only rows satisfying both predicates are returned, meaning the view is a narrowly scoped subset of the much larger PAY_ACTION_INFORMATION repository.

Key Columns

• ROW_ID — the ROWID of the underlying PAY_ACTION_INFORMATION row, useful for direct row access.
• ACTION_INFORMATION_ID — the primary identifier of the action information record.
• ASSIGNMENT_ID — the assignment that the Japanese employee detail belongs to.
• ASSIGNMENT_ACTION_ID — the related assignment action identifier.
• ACTION_CONTEXT_TYPE / ACTION_CONTEXT_ID / ACTION_INFORMATION_CATEGORY — context and category discriminators; the category is fixed to 'JP_EMPDET_EMP'.
• EFFECTIVE_DATE — the effective date of the record.
• FULL_NAME_KANA / FULL_NAME_KANJI — the employee name in phonetic kana and kanji representations.
• DATE_OF_BIRTH, GENDER, HIRE_DATE, TERMINATION_DATE — core employee attributes; date fields are converted through FND_DATE.CANONICAL_TO_DATE.
• ADDRESS_LINE1–3, REGION1–3, TOWN_OR_CITY, COUNTRY, POSTAL_CODE — Japanese address components.
• KIND_OF_BUSINESS — business classification data.
• ACTION_INFORMATION1 through ACTION_INFORMATION30 — the flexibly mapped segments that carry the Japanese-specific values; selected segments 3, 14, 16, 24–28 are converted to dates and segment 23 to a number.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY, and OBJECT_VERSION_NUMBER.

Common Use Cases and Queries

Typical use cases include extracting Japanese employee detail records for statutory reporting, payroll/labor interfaces, and localized HR reports. A straightforward query retrieves the name, birth date, and hire date for a given assignment:

SELECT assignment_id,
       full_name_kana,
       full_name_kanji,
       date_of_birth,
       hire_date
FROM   apps.per_jp_empdet_emp_v
WHERE  assignment_id = :p_assignment_id;

Because the view already converts canonical text into dates and numbers, report developers avoid repeating FND_DATE and FND_NUMBER conversion logic. A second common pattern joins the view to assignment or person tables using ASSIGNMENT_ID or ACTION_INFORMATION_ID to enrich output with employee identifiers. Since only rows with ACTION_CONTEXT_TYPE = 'AAP' and ACTION_INFORMATION_CATEGORY = 'JP_EMPDET_EMP' are exposed, queries need not repeat these filters. Integrators consuming the view should account for the canonical-to-date/number conversions, which ensure typed values are returned for downstream processing.