Results for “per_jp_wrkreg_extra_info_v”

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

Overview

The APPS.PER_JP_WRKREG_EXTRA_INFO_V view is a Japanese localization object within the Oracle E-Business Suite PER — Human Resources product family. It is documented in ETRM as a VALID view owned by the APPS schema and is explicitly scoped to Japanese localization only. The view presents a filtered, denormalized projection of work register (WRKREG) extra information — the supplementary assignment-level detail captured during payroll action processing — and exposes it under the friendly column prefix ADDITIONAL_INFORMATION1 through ADDITIONAL_INFORMATION24. In EBS reporting and integration, this view serves as the supported read surface for Japanese payroll and HR customers who must display, extract, or transfer the 24 descriptive flexfield-style attribute slots associated with an assignment action. Rather than requiring callers to know the physical ACTION_INFORMATION1..30 layout of the base table, the view shields consumers from the underlying generic action-information model and presents only the subset relevant to the Japanese work register.

Underlying Base Objects

The view is defined over a single base object, PAY_ACTION_INFORMATION (referenced in the metadata through its APPS synonym). The view text confirms this directly:

• Base table: PAY_ACTION_INFORMATION — the generic action-information repository used across Oracle Payroll for assignment action, assignment, and run-level context data.
• Filter predicate: the view restricts rows to ACTION_CONTEXT_TYPE = 'AAP' (assignment action processing) and ACTION_INFORMATION_CATEGORY = 'JP_EMPDET_EXTRA_INFO'. Only Japanese employee-detail extra-information records therefore surface.
• Column mapping: the physical ACTION_INFORMATION1..30 columns are re-exposed with the alias set ADDITIONAL_INFORMATION1..24, so the view reduces the visible attribute surface from thirty to twenty-four.
• No joins: the definition is a straight SELECT ... FROM PAY_ACTION_INFORMATION with no joins to PER_ASSIGNMENTS or other HR tables; assignment identity is carried by the retained ASSIGNMENT_ID and ASSIGNMENT_ACTION_ID columns.

Key Columns

• ROW_ID / ROWID — the physical row identifier from the base table, retained in the projection.
• ACTION_INFORMATION_ID — primary key of the action-information record.
• OBJECT_VERSION_NUMBER — optimistic locking column supporting concurrent updates.
• ASSIGNMENT_ACTION_ID — the payroll assignment action to which this extra information belongs.
• ASSIGNMENT_ID — the assignment (employee/position) context.
• EFFECTIVE_DATE — effective date of the action-information row.
• ACTION_CONTEXT_TYPE — always 'AAP' in this view.
• ACTION_INFORMATION_CATEGORY — always 'JP_EMPDET_EXTRA_INFO'.
• ADDITIONAL_INFORMATION1 … ADDITIONAL_INFORMATION24 — the localized attribute slots that customers populate for Japanese work register reporting; the searched term additional_information1 maps to the first of these.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — standard WHO audit columns.

Common Use Cases and Queries

Typical scenarios include extracting Japanese work-register attributes for statutory reporting, validating populated extra-information slots, and reconciling assignment actions with their supplemental detail.

• Retrieve all extra information for a given assignment action:

SELECT assignment_action_id, assignment_id, effective_date,
       additional_information1, additional_information2
FROM   apps.per_jp_wrkreg_extra_info_v
WHERE  assignment_action_id = :p_action_id;

• Find records where the first additional-information slot is populated:

SELECT action_information_id, assignment_id, additional_information1
FROM   apps.per_jp_wrkreg_extra_info_v
WHERE  additional_information1 IS NOT NULL;

• Join to assignments for employee-level reporting, using the retained ASSIGNMENT_ID as the link key.

Because the view enforces the Japanese category predicate, queries against it never require additional ACTION_CONTEXT_TYPE or ACTION_INFORMATION_CATEGORY filters.