Results for “terminate_flag”

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

Overview

PER_JP_WRKREG_EMP_V is an APPS-owned database view within the Oracle E-Business Suite Human Resources (PER) product family. It is documented in ETRM as existing solely to support the Japanese localization of Oracle HRMS, and its status is VALID in both 12.1.1 and 12.2.2. The view presents employee work-registration detail rows as they are stored in the generic Oracle Payroll action-information model, exposing Japanese-specific person and assignment attributes such as kana and kanji names, address components, birth and hire dates, and termination data. Because the physical repository (PAY_ACTION_INFORMATION) is a key-flexfield-style table, PER_JP_WRKREG_EMP_V serves as the semantic decoding layer that converts positional segment columns into business-meaningful names for reporting, interfaces, and localization extracts.

Underlying Base Objects

The documented referenced base objects are the FND_DATE package and the PAY_ACTION_INFORMATION synonym. The view text applies an explicit filter of ACTION_CONTEXT_TYPE = 'AAP' and ACTION_INFORMATION_CATEGORY = 'JP_EMPDET_EMP', restricting output to Japanese employee detail action information attached to assignment actions. It also calls FND_DATE.CANONICAL_TO_DATE on segments ACTION_INFORMATION3, ACTION_INFORMATION14, ACTION_INFORMATION16, and ACTION_INFORMATION18 so that date values stored in canonical (character) form are returned as true DATE values to the caller. Columns such as ROWID and OBJECT_VERSION_NUMBER are passed through for row identification and optimistic locking. In 12.2.2 and later, PAY_ACTION_INFORMATION is typically realized as a synonym over the corresponding PAY_ACTION_INFORMATION_F / _F? table pair, so the view remains the stable abstraction over that storage.

Key Columns

• ACTION_INFORMATION_ID, ASSIGNMENT_ACTION_ID, ACTION_CONTEXT_ID: Primary identifiers and the assignment-action context to which each row belongs.
• ASSIGNMENT_ID, EFFECTIVE_DATE: The employee assignment and the date from which the record applies.
• FULL_NAME_KANA, FULL_NAME_KANJI: Phonetic (kana) and ideographic (kanji) renderings of the employee name, mapped from ACTION_INFORMATION1 and ACTION_INFORMATION2.
• DATE_OF_BIRTH, HIRE_DATE, TERMINATION_DATE, DATE_OF_DEATH: Date attributes, several derived via FND_DATE.CANONICAL_TO_DATE from their underlying character segments.
• GENDER, ADDRESS_LINE1–3, REGION1–3, TOWN_OR_CITY, COUNTRY, POSTAL_CODE: Personal and address detail segments.
• KIND_OF_BUSINESS, TERMINATION_REASON, TERMINATE_FLAG: Work-registration classification and leaver attributes.
• EMPLOYEE_NUMBER: The person's employee number for reconciliation to PER_ALL_PEOPLE_F.
• ACTION_INFORMATION30: The thirtieth positional segment of the underlying action-information flexfield, surfaced without transformation; its business meaning is defined by the JP_EMPDET_EMP structure rather than by the view.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE, LAST_UPDATE_LOGIN: Standard WHO audit columns.

Common Use Cases and Queries

The view is most often consumed by Japanese localization reports, statutory extracts, and inbound/outbound interfaces that require work-registration detail without decoding the underlying flexfield directly. The absence of a documented join to PER_ALL_PEOPLE_F means callers typically join on ASSIGNMENT_ID to enrich the result.

SELECT assignment_id,
       employee_number,
       full_name_kanji,
       full_name_kana,
       date_of_birth,
       hire_date,
       termination_date,
       action_information30
FROM   apps.per_jp_wrkreg_emp_v
WHERE  effective_date BETWEEN :p_start AND :p_end
ORDER  BY assignment_id, effective_date;

Because ACTION_INFORMATION30 retains its positional identity, a frequent integration pattern is to filter on it for a localization-specific flag or code, or to project it into a staging table alongside the decoded columns. All access should be granted through the APPS synonym, and queries should apply an EFFECTIVE_DATE predicate to limit the potentially large set of historic action-information rows returned from PAY_ACTION_INFORMATION.