Results for “jp_empdet_emp”

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

Overview

APPS.PER_JP_EMPDET_EMP_V is an Oracle E-Business Suite view that exposes Japanese-specific employee detail (EMP DET) records stored within the Payroll action information framework. It is a filtered, column-formatted presentation of the PAY_ACTION_INFORMATION table, restricted to rows where ACTION_CONTEXT_TYPE equals 'AAP' and ACTION_INFORMATION_CATEGORY equals 'JP_EMPDET_EMP'. This category identifies Japanese localization employee detail (empdet) data captured against an assignment context.

The view exists to present the generic ACTION_INFORMATION1 through ACTION_INFORMATION30 columns as named, meaningful fields, and to convert raw stored values into canonical data types. Date fields are converted using FND_DATE.CANONICAL_TO_DATE and at least one numeric field is converted using FND_NUMBER.CANONICAL_TO_NUMBER. Because the base table stores everything as character data, this view provides the type-aware representation required by Oracle localization forms, concurrent programs, and downstream reporting.

Underlying Base Objects

The view is owned by APPS and is defined over the synonym PAY_ACTION_INFORMATION, which resolves to the underlying Payroll action information entity. The synonym is the direct base object referenced in the view definition.

Two PL/SQL packages are referenced as conversion utilities within the SELECT list: FND_DATE and FND_NUMBER. These are not base entities but provide the canonical conversion functions applied to the date and number columns. In Oracle EBS 12.1.1 and 12.2.2 the view definition and these dependencies are consistent; the object is a standard product view rather than a custom extension.

Filtering is applied at row level: only records whose action context type is 'AAP' and whose action information category is 'JP_EMPDET_EMP' are returned. This categories the row set to the Japanese employee detail flexfield usage only.

Key Columns

• ACTION_INFORMATION_ID — Primary identifier of the action information row.
• OBJECT_VERSION_NUMBER — Optimistic locking version for the row.
• ACTION_CONTEXT_ID / ACTION_CONTEXT_TYPE — Context of the record; the type is constrained to 'AAP'.
• ASSIGNMENT_ID — Assignment against which the employee detail is recorded.
• EFFECTIVE_DATE — Effective date of the information record.
• ACTION_INFORMATION_CATEGORY — Constrained to 'JP_EMPDET_EMP'.
• ACTION_INFORMATION1 .. ACTION_INFORMATION30 — The descriptive flexfield segments, exposed with selected date segments converted via FND_DATE.CANONICAL_TO_DATE and one numeric segment (ACTION_INFORMATION23) converted via FND_NUMBER.CANONICAL_TO_NUMBER.
• Audit columns — LAST_UPDATE_LOGIN, LAST_UPDATED_BY, LAST_UPDATE_DATE, CREATED_BY, CREATION_DATE for traceability.
• ROWID — Exposed for direct row addressing.

Common Use Cases and Queries

The view is typically used to retrieve Japanese employee detail values for a given assignment, for a specific effective period, or to feed reports and interfaces that require typed date and number output rather than raw character strings.

Sample query for a single assignment:

• SELECT assignment_id, effective_date, action_information1, action_information3, action_information23 FROM apps.per_jp_empdet_emp_v WHERE assignment_id = :p_assignment_id ORDER BY effective_date;

Sample query by effective date range:

• SELECT assignment_id, effective_date FROM apps.per_jp_empdet_emp_v WHERE effective_date BETWEEN :p_from_date AND :p_to_date;

Because the view already applies the 'AAP' and 'JP_EMPDET_EMP' filters, consumers do not need to add those predicates. Join the view to PER_ALL_ASSIGNMENTS_F on assignment_id to enrich output with person and assignment attributes for reporting or data conversion activities.