Results for “jp_def_emp”

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

Overview

APPS.PAY_JP_DEF_EMP_V is a Japanese localizations view within the Oracle E-Business Suite Payroll (PAY) product family. It exposes the "Define Employee" (JP_DEF_EMP) action information record type, which is used to capture employee personal and demographic data specific to Japanese statutory reporting requirements — including name in Kana, sex, address, household head information and disability, aged, widow and working student attributes. The view presents these values as a flattened, application-friendly row set for a single assignment action.

Because it filters on ACTION_CONTEXT_TYPE = 'AAP' and ACTION_INFORMATION_CATEGORY = 'JP_DEF_EMP', the view returns only rows of the assignment action information category that carries Japanese employee definition data. It is therefore a targeted reporting and integration surface rather than a general-purpose view over all action information.

Underlying Base Objects

Per the documented metadata (ETRM 12.2.2), the view is defined over three referenced objects: the view PAY_JP_DEF_EMP_DML_V, and the packages FND_DATE and FND_NUMBER.

• PAY_JP_DEF_EMP_DML_V — the immediate source view from which all columns are projected. It is the DML-capable view that maps the generic action information structures to the JP_DEF_EMP category.
• FND_DATE — supplies the CANONICAL_TO_DATE function used to convert Oracle Forms canonical date strings into proper DATE values for DATE_OF_BIRTH, DATE_OF_DEATH and CHANGE_DATE.
• FND_NUMBER — supplies CANONICAL_TO_NUMBER, applied to HOUSEHOLD_HEAD_CTR_ID to convert the stored canonical string into a numeric value.

The view does not itself store data; it is a read-only projection. Row identity is carried through ROW_ID and ACTION_INFORMATION_ID, and concurrency is tracked via OBJECT_VERSION_NUMBER.

Key Columns

• ASSIGNMENT_ACTION_ID / ASSIGNMENT_ID — link the record to the assignment action and the underlying assignment; these are the primary join keys to the action framework.
• EFFECTIVE_DATE — the date from which the employee definition data takes effect.
• ACTION_CONTEXT_TYPE / ACTION_INFORMATION_CATEGORY — always 'AAP' and 'JP_DEF_EMP' respectively in this view.
• LAST_NAME_KANA / FIRST_NAME_KANA — the employee's name in Japanese Kana, as required for statutory reporting.
• LAST_NAME / FIRST_NAME — the employee's name in standard characters.
• DATE_OF_BIRTH / DATE_OF_DEATH — converted to DATE via FND_DATE.
• SEX, POSTAL_CODE, ADDRESS — core demographic attributes.
• HOUSEHOLD_HEAD_CTR_ID — converted to a number via FND_NUMBER; identifies the household head contact.
• HOUSEHOLD_HEAD_FULL_NAME / HOUSEHOLD_HEAD_CONTACT_TYPE — descriptive household head details.
• MARRIED_FLAG — marital status indicator.
• CHANGE_DATE / CHANGE_REASON — audit context for the change.
• DISABILITY_TYPE / AGED_TYPE / WIDOW_TYPE / WORKING_STUDENT_TYPE — statutory classification flags, each paired with a corresponding *_DETAILS column.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO columns for auditing.

Common Use Cases and Queries

This view is typically used for extract reporting, payroll interfaces and downstream statutory submissions that require the defined employee attributes for a given assignment action. A representative query is:

SELECT assignment_action_id,
       assignment_id,
       effective_date,
       last_name_kana,
       first_name_kana,
       date_of_birth,
       sex,
       household_head_full_name,
       married_flag
FROM   apps.pay_jp_def_emp_v
WHERE  assignment_id = :p_assignment_id
ORDER BY effective_date;

Because the view is pre-filtered to the JP_DEF_EMP category, callers need not repeat the ACTION_CONTEXT_TYPE and ACTION_INFORMATION_CATEGORY predicates. For full history, join on ASSIGNMENT_ACTION_ID to the action framework tables, or correlate to PAY_ASSIGNMENT_ACTIONS for process context. Given the canonical conversions, values returned are already in native DATE and NUMBER form, so no further decoding is required in reporting logic.