Results for “pay_indicator_entries_v”

30 results




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

Overview

The APPS.PAY_INDICATOR_ENTRIES_V view is a Payroll (PAY) module construct delivered in Oracle E-Business Suite 12.1.1 and 12.2.2. It functions as the data source for the Advance block within the Advance Pay form (PAYWSAHP), retrieving indicator element entries associated with a specific assignment. The view isolates the element entries that carry advance pay indicators, presenting them alongside derived attributes such as the advance start date, advance end date, computed advanced amount, and a processed flag.

The view is not intended as a general-purpose reporting object. Its inline comments explicitly document the period-boundary logic it enforces: session dates one through four display pay/holiday period one and period two, session date five displays only period two, and session date six displays no periods. A further documented constraint states that the view handles empty queries only, because of the embedded TO_DATE statements; consequently the corresponding form does not support Query-By-Example (QBE). Integrators and report developers should account for this limitation when attempting to filter the view externally.

Underlying Base Objects

The view is defined over the following documented base objects:

The declared query carries the ORDERED and DISTINCT hints.

Key Columns

  • LEGISLATION_CODE — the legislation under which the entry is defined.
  • ASSIGNMENT_ID — the assignment owning the indicator element entry.
  • ELEMENT_ENTRY_ID — the unique identifier of the advance pay indicator entry.
  • EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the payment period boundaries for the entry.
  • Advance pay start date — derived from the first screen entry value via FND_DATE.CANONICAL_TO_DATE.
  • Advance pay end date — derived from the second screen entry value.
  • Advanced amount — returned by PAY_ADVANCE_PAY_PKG.ADVANCE_AMOUNT, evaluated against the start date, element entry, and assignment.
  • Processed flag — a DECODE expression yielding 'N' when the advanced amount is NULL and 'Y' otherwise.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns propagated from the element entry.

Common Use Cases and Queries

Typical usage centers on confirming whether an assignment already carries a processed advance for a given period, and on reconciling the start and end dates the form would present. Note the absence of a rule_mode column; the legislation and session-date logic effectively governs which periods appear, so queries keyed on a hypothetical rule_mode will not resolve against this view.

A representative query:

  • SELECT assignment_id, element_entry_id, effective_start_date, effective_end_date, legislation_code FROM apps.pay_indicator_entries_v WHERE assignment_id = :p_assignment_id;
  • SELECT assignment_id, element_entry_id, legislation_code FROM apps.pay_indicator_entries_v WHERE TRUNC(effective_start_date) BETWEEN :p_start AND :p_end;

Because the view relies on session context and embedded conversions, external filters should be kept narrow, and developers should validate results against the Advance Pay form itself rather than treating the view as a standalone reporting source.