Results for “datetrack_update_mode”

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

Overview

PAY_JP_DEF_DEP_V is an APPS-owned database view within the Oracle E-Business Suite Payroll (PAY) product module. The view is documented in ETRM as a Japanese localization object and carries a VALID status in the EBS 12.1.1 and 12.2.2 environments. Its purpose is to expose dependent and beneficiary information captured through the Japanese dependent declaration ("Def Dep") action information framework, allowing dependent records associated with an assignment action to be queried in a flattened, reportable form.

The view filters the underlying action information data set to a fixed context: only rows where ACTION_CONTEXT_TYPE equals 'AAP' and ACTION_INFORMATION_CATEGORY equals 'JP_DEF_DEP' are returned. This makes PAY_JP_DEF_DEP_V a purpose-built projection for Japanese payroll dependent declarations rather than a general-purpose action information view. It is typically consumed by localized payroll reporting, extract processes, and integration routines that must reproduce the dependent data supplied by an employee during a Japanese payroll declaration cycle.

Underlying Base Objects

PAY_JP_DEF_DEP_V is defined over three documented base objects:

• PAY_JP_DEF_DEP_DML_V (VIEW) — the primary source, supplying the dependent declaration rows and the filtering predicate on ACTION_CONTEXT_TYPE and ACTION_INFORMATION_CATEGORY.
• FND_NUMBER (PACKAGE) — used to convert stored character representations into numeric values through FND_NUMBER.CANONICAL_TO_NUMBER, applied to CONTACT_EXTRA_INFO_ID, CEI_OBJECT_VERSION_NUMBER, CONTACT_RELATIONSHIP_ID, ESTIMATED_ANNUAL_INCOME, and ESTIMATED_ANNUAL_INCOME_O.
• FND_DATE (PACKAGE) — used to convert stored character representations into proper dates through FND_DATE.CANONICAL_TO_DATE, applied to DATE_OF_BIRTH, DATE_OF_DEATH, and CHANGE_DATE.

This two-layer design is characteristic of Japanese localization objects, where the DML view handles the persisted action information structure and the reporting view applies canonical datatype conversion and context filtering for downstream consumption.

Key Columns

The user searching on "dep_type" will find this column directly exposed by the view, alongside its "_O" counterpart:

• DEP_TYPE / DEP_TYPE_O — the dependent type classification for the declared dependent, with the "_O" column preserving the original (non-canonical) stored value.
• ACTION_CONTEXT_TYPE, ACTION_INFORMATION_CATEGORY, ACTION_INFORMATION_ID, ASSIGNMENT_ACTION_ID — identify the action information record and its context; these are fixed to 'AAP' and 'JP_DEF_DEP' respectively in this view.
• ASSIGNMENT_ID, EFFECTIVE_DATE, STATUS — the assignment the declaration applies to, its effective date, and the record status.
• CONTACT_EXTRA_INFO_ID, CONTACT_RELATIONSHIP_ID, LAST_NAME_KANA, FIRST_NAME_KANA, LAST_NAME, FIRST_NAME, CONTACT_TYPE — dependent identity data, including Japanese kana name representations.
• DATE_OF_BIRTH, DATE_OF_DEATH, ADDRESS, CHANGE_DATE, CHANGE_REASON — biographical and change-tracking attributes for the dependent.
• OCCUPATION / OCCUPATION_O, ESTIMATED_ANNUAL_INCOME / ESTIMATED_ANNUAL_INCOME_O, DISABILITY_TYPE / DISABILITY_TYPE_O, DISABILITY_DETAILS / DISABILITY_DETAILS_O — dependent-specific attributes required for Japanese tax and social insurance declarations.
• ROW_ID, OBJECT_VERSION_NUMBER, DATETRACK_UPDATE_MODE, DATATRACK_DELETE_MODE, audit columns — row identity, concurrency control, and audit metadata.

Common Use Cases and Queries

Typical scenarios include dependent declaration reporting, verification of declared dependents per assignment, and extraction of disability or income attributes for downstream Japanese tax processing. Because the view already applies the AAP / JP_DEF_DEP filter, query predicates need only target assignment, date, or dependent type.

• Retrieve declared dependents by type for an assignment:

SELECT assignment_id, effective_date, last_name, first_name, dep_type, dep_type_o FROM apps.pay_jp_def_dep_v WHERE assignment_id = :p_assignment_id AND dep_type = :p_dep_type ORDER BY effective_date;

• Extract dependent attributes for a declaration period:

SELECT assignment_id, contact_extra_info_id, dep_type, occupation, estimated_annual_income, disability_type, date_of_birth FROM apps.pay_jp_def_dep_v WHERE effective_date BETWEEN :p_start AND :p_end;

Because DEP_TYPE and its related "_O" columns coexist, reports should generally present the canonical DEP_TYPE while preserving DEP_TYPE_O for audit comparison against the originally entered value.