Results for “per_jp_empdet_assignments_v”

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

Overview

The view PER_JP_EMPDET_ASSIGNMENTS_V is an Oracle E-Business Suite database object owned by the APPS schema and categorized under the PER (Human Resources) product family. Its documented description states that it is used for Japanese localization only, meaning it exists to support country-specific statutory and reporting requirements for Japan rather than generic global HR functionality. In EBS 12.1.1 and 12.2.2, the object is reported as VALID, and it is not a standalone transactional entity but rather a filtered projection over a shared payroll action-information store.

The view presents employee assignment detail records that have been captured as action information under a dedicated Japanese localization context. Because it exposes a narrow, pre-filtered slice of data, it functions primarily as a reporting and integration surface: external extracts, localization reports, and interface programs can query the view without needing to reconstruct the underlying filter predicates on action context type and action information category.

Underlying Base Objects

The documented base objects referenced by this view are PAY_ACTION_INFORMATION (accessed through a synonym) and the FND_DATE package. The view selects from PAY_ACTION_INFORMATION and applies two constant predicates: ACTION_CONTEXT_TYPE = 'AAP' and ACTION_INFORMATION_CATEGORY = 'JP_EMPDET_ASSIGNMENTS'. The 'AAP' context identifies assignment-level action information, so the rows returned are assignment-scoped action records.

PAY_ACTION_INFORMATION is a generic key-flexfield style store: descriptive values are held in numbered columns such as ACTION_INFORMATION1 through ACTION_INFORMATION7 and beyond, with the meaning of each column determined by the category. This is why the view can present logical business attributes such as organization name, job, position, and grade even though the base table contains only generic numbered columns. The FND_DATE.CANONICAL_TO_DATE function is applied to columns 5 and 6, converting the canonical date representation stored in the base table into proper date values for the corresponding date-oriented columns.

Key Columns

The view exposes a mixture of technical identifiers and localization business attributes:

• ROW_ID / ACTION_INFORMATION_ID — the physical row identifier and the primary key of the underlying action-information record.
• OBJECT_VERSION_NUMBER — optimistic locking/versioning column for the base record.
• ASSIGNMENT_ID / ASSIGNMENT_ACTION_ID — the assignment and assignment action to which the detail record belongs.
• ACTION_CONTEXT_TYPE / ACTION_CONTEXT_TYPE ('AAP') and ACTION_INFORMATION_CATEGORY ('JP_EMPDET_ASSIGNMENTS') — the fixed filter values that define the view's scope.
• EFFECTIVE_DATE / START_DATE / END_DATE — effective dating for the assignment detail; the date columns derived from ACTION_INFORMATION5 and ACTION_INFORMATION6 are converted via FND_DATE.CANONICAL_TO_DATE.
• ORGANIZATION_NAME, JOB, POSITION, GRADE — the Japanese localization business attributes mapped from numbered action-information columns, describing the assignment's organizational and job classification.
• ASSIGNMENT_NUMBER — the human-readable assignment identifier.
• Audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) — standard who/when audit trail inherited from the base table.

The documentation also lists ACTION_INFORMATION_ID and ROW_ID separately, and shows that the select list retrieves additional numbered columns beyond those given friendly names in the column list. The mapping between numbered columns and the business-named columns is the essential interpretation layer for this view.

Common Use Cases and Queries

Typical uses include Japanese localization reporting of assignment details, data extracts for downstream statutory interfaces, and reconciliation of assignment action information captured through the Japanese localization process. A representative query is:

• SELECT assignment_id, assignment_number, organization_name, job, position, grade, start_date, end_date FROM apps.per_jp_empdet_assignments_v WHERE assignment_id = :p_assignment_id;
• SELECT assignment_id, effective_date, organization_name, job, grade FROM apps.per_jp_empdet_assignments_v WHERE effective_date BETWEEN :p_from AND :p_to ORDER BY assignment_id, effective_date;

Because the view already applies the 'AAP' and 'JP_EMPDET_ASSIGNMENTS' predicates internally, queries against it should not repeat those filters. Consumers requiring non-Japanese localization data must query PAY_ACTION_INFORMATION directly with the appropriate context and category. As with all APPS-owned views, grants and synonym availability should be confirmed for the connecting schema, and the view should be treated as a read-only reporting object rather than a DML target.