Results for “jp_empdet_extra_info”

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

Overview

APPS.PER_JP_WRKREG_EXTRA_INFO_V is a reportable database view in Oracle E-Business Suite (EBS) Release 12.1.1 and 12.2.2 that exposes rows of the PAY_ACTION_INFORMATION table associated with Japanese work register extra information. The view filters the physical table down to the rows where ACTION_CONTEXT_TYPE equals 'AAP' and ACTION_INFORMATION_CATEGORY equals 'JP_EMPDET_EXTRA_INFO', providing a stable, self-documenting interface for developers, reports, and integrations that need to read Japanese employee detail extra information without embedding the restrictive WHERE clause in every query.

The name reflects its purpose. PER denotes the HRMS/People product family, JP indicates the localization layer for Japan, WRKREG refers to the work register construct used in Japanese payroll and HR processing, and EXTRA_INFO signals that the view carries the extensible, descriptive attributes captured alongside the employee detail (jp_empdet_extra_info) record. Because the underlying storage is a generic date-tracked key-flex structure, the view acts as a logical projection rather than a physical table, meaning consumers benefit from real-time consistency with the base data and automatic inheritance of object versioning and audit columns.

In reporting and integration terms, the object is read-only. It is queryable from PL/SQL, Oracle Reports, Oracle XML Publisher, OBIEE/BI Publisher data models, and any JDBC or OIC-based extraction. Because it is owned by APPS, grants are typically managed through the standard HRMS security model, so access should be tested against the custom responsibility or read-only user used by the reporting layer.

Underlying Base Objects

The documented base object for this view is PAY_ACTION_INFORMATION, exposed in the ETRM metadata as SYNONYM. The view is defined as a straight SELECT over that table with two fixed predicates applied: ACTION_CONTEXT_TYPE = 'AAP' and ACTION_INFORMATION_CATEGORY = 'JP_EMPDET_EXTRA_INFO'. No joins, unions, or aggregation appear in the view text, so the view projects every column of PAY_ACTION_INFORMATION — ROWID plus the identifying, flex, and audit columns — for the qualifying subset only.

PAY_ACTION_INFORMATION is the generic, multi-purpose holding table used across Oracle Payroll and HRMS action processing. The AAP context type identifies the action-context population to which the row belongs. ACTION_INFORMATION1 through ACTION_INFORMATION30 form the key-flex segment that carries the actual Japanese employee detail extra attributes. Assignment_id and effective_date anchor each record to a specific assignment and time-effective date, so the view naturally participates in date-tracked (datetracked) processing consistent with the rest of HRMS.

Because the view is defined over a synonym, the underlying object resolves to the APPS-owned PAY_ACTION_INFORMATION in the current schema context. There is no materialized or denormalized copy, so any DML must be performed against the base table through the supported business APIs rather than against the view.

Key Columns

The view exposes the full column list of PAY_ACTION_INFORMATION. The most significant columns for consumers are:

• ACTION_INFORMATION_ID — Primary identifier for the action information record; unique per stored row.
• ACTION_CONTEXT_TYPE — Always 'AAP' in this view, identifying the action context.
• ACTION_INFORMATION_CATEGORY — Always 'JP_EMPDET_EXTRA_INFO', the category that defines the semantic meaning of the information flexfields.
• ACTION_CONTEXT_ID — Reference to the parent action context record.
• ASSIGNMENT_ID — The assignment to which the extra information belongs; the key link to PER_ASSIGNMENTS.
• EFFECTIVE_DATE — The date from which the information is effective, supporting datetrack queries.
• ACTION_INFORMATION1 … ACTION_INFORMATION30 — The thirty generic flex columns holding the actual Japanese employee detail extra attributes. Which of these are populated depends on the configuration of the JP_EMPDET_EXTRA_INFO descriptive flexfield.
• OBJECT_VERSION_NUMBER — Optimistic locking control column used by the underlying framework.
• LAST_UPDATE_LOGIN, LAST_UPDATED_BY, LAST_UPDATE_DATE, CREATED_BY, CREATION_DATE — Standard EBS audit columns for traceability.

Consumers should never assume which flex column maps to which business attribute; the mapping is defined by the flexfield setup and can vary by implementation.

Common Use Cases and Queries

Typical scenarios include Japanese payroll and HR reporting, data migration validation, audit of extra information captured against assignments, and integration extracts feeding downstream HR data warehouses. A common query pattern joins the view to the assignment to obtain employee context:

• Assignment-level extraction: SELECT v.assignment_id, v.effective_date, v.action_information1, v.action_information2 FROM apps.per_jp_wrkreg_extra_info_v v WHERE v.assignment_id = :p_assignment_id ORDER BY v.effective_date.
• Date-effective lookup: SELECT * FROM apps.per_jp_wrkreg_extra_info_v WHERE assignment_id = :p_assignment_id AND effective_date = (SELECT MAX(effective_date) FROM apps.per_jp_wrkreg_extra_info_v WHERE assignment_id = :p_assignment_id AND effective_date <= SYSDATE).
• Join to assignment for employee details: SELECT a.assignment_id, a.person_id, v.action_information1 FROM apps.per_jp_wrkreg_extra_info_v v, apps.per_all_assignments_f a WHERE v.assignment_id = a.assignment_id AND v.effective_date BETWEEN a.effective_start_date AND a.effective_end_date.
• Audit/change tracking: SELECT action_information_id, last_updated_by, last_update_date FROM apps.per_jp_wrkreg_extra_info_v WHERE last_update_date >= :p_since.

Because the view already applies the context and category filters, queries remain short and less error-prone. For best performance, filter on ASSIGNMENT_ID and EFFECTIVE_DATE, which align with the selective access paths expected on the base table. Always qualify the view with the APPS schema in cross-schema queries.