Results for “pay_jp_nonresident_entries_v”

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

Overview

APPS.PAY_JP_NONRESIDENT_ENTRIES_V is a PL/SQL view owned by the APPS schema and validated in Oracle E-Business Suite 12.1.1 and 12.2.2. It exists exclusively to support the Japanese localization of Oracle Payroll and is not part of the core, global payroll data model. The view consolidates element entry data for the seeded element COM_NRES_INFO, which holds nonresident information captured against an assignment — most notably the nonresident start date and the projected residence date.

The view's principal role is to flatten the parent/child structure of element entries and their input values into a single row per element entry. For each qualifying entry, it derives the input value IDs and the canonical date values for the inputs named NRES_START_DATE and PROJECTED_RES_DATE. This makes the Japanese nonresident attributes directly consumable by concurrent programs, reports, and downstream integrations without requiring callers to join PAY_ELEMENT_ENTRIES_F, PAY_ELEMENT_ENTRY_VALUES_F, PAY_INPUT_VALUES_F, and PAY_ELEMENT_LINKS_F themselves. The user search term "nres_start_date" maps directly to one of the two decoded input values, confirming that this view is the standard access path for that attribute.

Underlying Base Objects

The view is defined over the following documented base objects, all referenced through APPS synonyms except the FND_DATE package:

• PAY_ELEMENT_ENTRIES_F — supplies the element entry header (entry type, assignment, effective dates).
• PAY_ELEMENT_ENTRY_VALUES_F — supplies the individual input values attached to each entry.
• PAY_INPUT_VALUES_F — defines the input value names, used to pivot NRES_START_DATE and PROJECTED_RES_DATE.
• PAY_ELEMENT_LINKS_F — links the element type to the assignment or applicant criteria.
• PAY_ELEMENT_TYPES_F — filters to the element named COM_NRES_INFO.
• FND_SESSIONS — joined on USERENV('SESSIONID') to obtain the effective date driving date-tracked (datetracked) lookups.
• FND_DATE — the package providing CANONICAL_TO_DATE, which converts the stored canonical screen entry values into true DATE values.

The joins enforce effective-date containment across every date-tracked table using the session effective date, and restrict PAY_ELEMENT_ENTRIES_F to ENTRY_TYPE = 'E'. The element link join uses the expression PEL.ELEMENT_TYPE_ID + 0 = PET.ELEMENT_TYPE_ID, a common pattern to force numeric comparison.

Key Columns

• ELEMENT_ENTRY_ID — primary identifier for the element entry; groups the aggregated input values.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the date-tracked validity window for the entry.
• ASSIGNMENT_ID — the assignment to which the nonresident entry belongs.
• ELEMENT_LINK_ID — the link record governing eligibility for the assignment.
• OBJECT_VERSION_NUMBER — optimistic locking version for the entry row.
• MIN(DISTINCT DECODE(... 'NRES_START_DATE' ...)) — two aggregated columns holding the input value ID and the canonical DATE for the nonresident start date.
• MIN(DISTINCT DECODE(... 'PROJECTED_RES_DATE' ...)) — the equivalent value ID and DATE pair for the projected residence date.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns aggregated with MIN(DISTINCT).

Because results are aggregated, the view returns at most one row per element entry, with the two date inputs pivoted into columns rather than rows.

Common Use Cases and Queries

Typical applications include Japanese nonresident reporting, audit of nonresident start dates, and interfaces feeding tax or residence-status processing. Because the view depends on FND_SESSIONS and USERENV('SESSIONID'), it must be queried from within an EBS session (for example, through a concurrent program or OAF page) rather than from a bare SQL*Plus connection, where the effective date would not resolve as expected.

• Reporting nonresident start dates per assignment for a payroll period.
• Identifying assignments with a missing NRES_START_DATE or PROJECTED_RES_DATE.
• Extracting data for external tax filings or localization-specific integrations.

A representative query, restricted by EBS effective date context:

• SELECT element_entry_id, assignment_id, effective_start_date, effective_end_date FROM apps.pay_jp_nonresident_entries_v;
• SELECT assignment_id, element_entry_id FROM apps.pay_jp_nonresident_entries_v WHERE assignment_id = :p_assignment_id;

Consumers should treat the two decoded date columns as the authoritative nonresident attributes and join back to PAY_ASSIGNMENT_ACTIONS_F or PER_ALL_ASSIGNMENTS_F for person-level context.