Search Results projected_res_date

Overview

APPS.PAY_JP_NONRESIDENT_ENTRIES_V is a Japanese localization (JP) payroll view within Oracle E-Business Suite, delivered as part of the Oracle Payroll module. It exposes element entry records associated with the COM_NRES_INFO element — the "Non-Resident Information" element used to capture non-resident tax and residency data for Japanese payroll processing. The view presents a consolidated, session-effective-date-filtered projection of element entries and their key descriptive flexfield-style input values (specifically NRES_START_DATE and PROJECTED_RES_DATE).

Because the view resolves effective dates through FND_SESSIONS, it returns only records that are valid as of the current session's effective date, making it suitable for concurrent programs, payroll processes, and localization-specific reporting. It is owned by the APPS schema and is intended for read-only consumption by Oracle Payroll, Japanese statutory reporting, and downstream integrations.

Underlying Base Objects

The view is defined over several synonyms referencing core Oracle Payroll tables, joined with the FND_DATE package and FND_SESSIONS:

• PAY_ELEMENT_ENTRIES_F — the driving table holding element entry headers (pee).
• PAY_ELEMENT_ENTRY_VALUES_F — the entry-level input values (peev) linked to each entry.
• PAY_ELEMENT_LINKS_F — the element-to-link mapping (pel) providing element_link_id.
• PAY_ELEMENT_TYPES_F — element definitions (pet), filtered to element_name = 'COM_NRES_INFO'.
• PAY_INPUT_VALUES_F — input value definitions (piv), used to pivot NRES_START_DATE and PROJECTED_RES_DATE.
• FND_SESSIONS — supplies the session effective date used throughout the date-bounded joins.
• FND_DATE (PACKAGE) — invoked as fnd_date.canonical_to_date to convert stored screen entry values into canonical dates.

Joins are constrained by effective date ranges on the element type, entry, link, and input value, and entries are restricted to entry_type = 'E'.

Key Columns

• ELEMENT_ENTRY_ID — primary identifier of the element entry.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — date-effective range of the entry.
• ASSIGNMENT_ID — the assignment to which the entry belongs.
• ELEMENT_LINK_ID — the link through which the element is assigned.
• OBJECT_VERSION_NUMBER — optimistic locking version for the row.
• NRES_START_DATE (value id and date) — the non-resident start date, returned both as an input_value_id and as a canonical date.
• PROJECTED_RES_DATE (value id and date) — the projected residency date, similarly returned in both forms.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns, aggregated via MIN(DISTINCT ...).

Common Use Cases and Queries

Typical uses include Japanese non-resident tax reporting, auditing residency effective dates, and feeding downstream compliance extracts. Because the view relies on FND_SESSIONS for its effective date, it is best queried inside a session where the effective date is set appropriately (for example, within a payroll concurrent program).

Sample query:

• SELECT element_entry_id, assignment_id, element_link_id, nres_start_date, projected_res_date FROM apps.pay_jp_nonresident_entries_v WHERE assignment_id = :p_assignment_id;
• SELECT nres_start_date, projected_res_date FROM apps.pay_jp_nonresident_entries_v WHERE effective_start_date BETWEEN :p_start AND :p_end;

Note that the grouping and MIN(DISTINCT ...) aggregation collapse potentially multiple input value rows into a single row per element entry, so consumers should treat each returned row as the effective, de-duplicated residency record for the given assignment and entry.