Results for “jp_def_dep_oe”

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

Overview

APPS.PAY_JP_DEF_DEP_OE_V is an Oracle E-Business Suite view that exposes Japanese localization data for dependents and other eligible persons (DEP) associated with the Other Eligible (OE) contact type, which is a characteristic contact classification in Oracle Payroll. The view is defined over the payroll action-information data model and is intended solely for reading records that have already been captured through the standard Oracle Payroll dependent and other-eligible processing flows. It presents a denormalized, report-friendly projection of dependent/beneficiary records, combining contact identification data, Japanese phonetic name fields, personal details such as date of birth and death, and occupational information. Because it filters on a fixed action context and category, the view is a targeted read-only surface for Japanese payroll dependents and eligible persons rather than a general-purpose contact view.

Underlying Base Objects

The view is documented as being defined over three objects: the package FND_DATE, the package FND_NUMBER, and the view PAY_JP_DEF_DEP_OE_DML_V. FND_NUMBER supplies the CANONICAL_TO_NUMBER conversion routine used to normalize the character-based numeric identifiers carried in the payroll contact extra-information and relationship columns. FND_DATE supplies the CANONICAL_TO_DATE routine applied to DATE_OF_BIRTH, DATE_OF_DEATH, and CHANGE_DATE, converting the stored character representations into proper date values. PAY_JP_DEF_DEP_OE_DML_V is the DML-capable parent view that holds the actual dependent/other-eligible records, including the DATETRACK_UPDATE_MODE and DATETRACK_DELETE_MODE columns used by the Oracle Payroll datetracked (date-effective) model. PAY_JP_DEF_DEP_OE_V filters that DML view with the predicates ACTION_CONTEXT_TYPE = 'AAP' and ACTION_INFORMATION_CATEGORY = 'JP_DEF_DEP_OE', isolating the Japanese dependent/other-eligible rows from the wider action-information population.

Key Columns

• ROW_ID, ACTION_INFORMATION_ID, OBJECT_VERSION_NUMBER — Primary identifiers for the underlying action-information row and its optimistic-locking version.
• ASSIGNMENT_ACTION_ID, ASSIGNMENT_ID, ACTION_CONTEXT_TYPE, ACTION_INFORMATION_CATEGORY, STATUS — Payroll context linking the record to a specific assignment and processing action; the context type and category are constrained to 'AAP' and 'JP_DEF_DEP_OE'.
• EFFECTIVE_DATE, DATETRACK_UPDATE_MODE, DATETRACK_DELETE_MODE — Date-effective and datetrack control columns governing the validity and lifecycle of the record.
• CONTACT_EXTRA_INFO_ID, CEI_OBJECT_VERSION_NUMBER, CONTACT_RELATIONSHIP_ID — Converted numeric contact-extra-information and relationship identifiers.
• LAST_NAME_KANA, FIRST_NAME_KANA, LAST_NAME, FIRST_NAME — Personal name data, including Japanese phonetic (kana) forms.
• CONTACT_TYPE, DATE_OF_BIRTH, DATE_OF_DEATH, ADDRESS, CHANGE_DATE, CHANGE_REASON — Contact classification, key dates, address, and the reason and date of the most recent change.
• OCCUPATION, OCCUPATION_O — Current and previous occupation values, reflecting the date-effective model.
• OE_CONTACT_RELATIONSHIP_ID, OE_FULL_NAME, OE_CONTACT_TYPE, OE_ADDRESS, OE_CONTACT_RELATIONSHIP_ID_O — Fields describing the related other-eligible person and its prior-image relationship identifier.
• Audit columns — LAST_UPDATE_LOGIN, LAST_UPDATED_BY, LAST_UPDATE_DATE, CREATED_BY, CREATION_DATE.

Common Use Cases and Queries

Typical uses include dependent-eligibility reporting, Japanese payroll data extraction, and integration feeds that must publish dependent and other-eligible information to external systems. Because dates and numbers are surfaced in canonical form, consumers avoid re-implementing conversion logic. A representative query is:

• SELECT assignment_id, last_name, first_name, last_name_kana, first_name_kana, date_of_birth, contact_type, effective_date FROM apps.pay_jp_def_dep_oe_v ORDER BY assignment_id, effective_date DESC;
• SELECT oe_full_name, oe_contact_type, oe_address, occupation FROM apps.pay_jp_def_dep_oe_v WHERE contact_relationship_id = :rel_id;
• SELECT r.action_information_id, r.status, r.change_reason FROM apps.pay_jp_def_dep_oe_v r WHERE r.effective_date BETWEEN :start_dt AND :end_dt;

The ACTION_CONTEXT_TYPE and ACTION_INFORMATION_CATEGORY predicates are already applied internally, so callers need not filter on them.