Search Results pay_element_links_f_pk




Overview
Explore in AI Chat

Overview

APPS.PAY_JP_HOUSING_ENTRIES_V is a Japanese localization reporting view within the Oracle E-Business Suite Payroll (PAY) module. It exposes housing loan tax credit element entries, filtering specifically on the element named YEA_HOUSING_LOAN_TAX_CREDIT. The view consolidates header-level element entry data with associated input values, element link definitions, and element type metadata, presenting them as a single denormalized result set suitable for payroll reporting, extracts, and regulatory reporting requirements specific to Japanese payroll processing.

Because the view is session-aware, it relies on FND_SESSIONS and the USERENV('sessionid') function to align effective-dating logic with the current user session. This design is consistent with many Oracle Payroll localization views that must respect the effective date context of the running session when resolving date-tracked rows.

Underlying Base Objects

The view is defined over the following documented base objects, all referenced through PUBLIC synonyms owned by APPS:

  • FND_SESSIONS — Provides session context; joined on session_id = userenv('sessionid') and used to constrain effective dates.
  • PAY_ELEMENT_TYPES_F — Supplies element type definitions; joined to identify the YEA_HOUSING_LOAN_TAX_CREDIT element and to enforce date-tracked validity.
  • PAY_ELEMENT_ENTRIES_F — The core element entry records, restricted to entry_type = 'E' (entry-level rows).
  • PAY_ELEMENT_LINKS_F — Links entries to element types via element_link_id and element_type_id. The view text explicitly hints the PAY_ELEMENT_LINKS_F_PK index, which is likely why a search for that index name surfaced this object.
  • PAY_ELEMENT_ENTRY_VALUES_F — Holds the input values attached to each entry.
  • PAY_INPUT_VALUES_F — Defines the input values and their display sequences, used to pivot the values into distinct columns.
  • FND_DATE — A package referenced for date conversion via FND_DATE.canonical_to_date.

Key Columns

The view exposes the following columns derived from the base tables:

  • element_entry_id — Primary identifier of the element entry.
  • effective_start_date / effective_end_date — Effective-dating boundaries for the entry.
  • assignment_id — The assignment to which the entry belongs.
  • element_link_id — Identifier of the element link connecting the entry to its element type.
  • object_version_number — Optimistic locking version attribute.
  • Input value columns — Two pivoted columns derived from display_sequence 1 and 2, exposing input_value_id identifiers and their screen_entry_value. Sequence 1 is cast to a number; sequence 2 is converted to a date using FND_DATE.canonical_to_date, reflecting the distinct data types of the two housing loan inputs.
  • Audit columns — creation_date, created_by, last_update_date, last_updated_by, last_update_login, each aggregated with MIN(DISTINCT ...).

Common Use Cases and Queries

This view is typically consumed by Japanese payroll reports that require housing loan tax credit data per assignment, often for tax filing or reconciliation. A representative query is:

  • SELECT assignment_id, effective_start_date, effective_end_date, element_entry_id FROM apps.pay_jp_housing_entries_v WHERE assignment_id = :p_assignment_id;
  • SELECT assignment_id, MIN(effective_start_date) FROM apps.pay_jp_housing_entries_v GROUP BY assignment_id; — for extracting the earliest housing entry per employee.
  • Joining the view to PER_ALL_ASSIGNMENTS_F or PER_PEOPLE_F to enrich output with employee name and number.

Because the view restricts to entries effective as of the current session date, consumers must set the correct effective date context (typically via the standard HRMS session initialization) before querying, or results may be empty or misaligned with historical reporting needs.