Search Results max_value




Overview
Explore in AI Chat

Overview

PAY_LINK_INPUT_VALUES_X is a date-effective (X) view owned by the APPS schema in Oracle E-Business Suite, delivered within the Payroll (PAY) product family. It exposes the currently effective rows of the underlying link input value definition entity, which governs default, minimum, and maximum constraint behavior applied to input values when an element is linked to an assignment, element link, or payroll configuration. The view is documented as VALID in ETRM for both 12.1.1 and 12.2.2. Because it filters on the effective date range rather than returning all historical definition rows, it is the appropriate access point for reporting and integration logic that must reflect only the definition currently active as of the query execution date.

Underlying Base Objects

The view is defined over a single documented base object, PAY_LINK_INPUT_VALUES_F (referenced through a synonym), which stores the datetracked (F = date-effective/from) rows for link input values. The view text applies the filter TRUNC(SYSDATE) BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE against that base table. Consequently, PAY_LINK_INPUT_VALUES_X behaves as a point-in-time projection: it returns only those rows whose effective interval covers the current system date. Historical or future-dated definition rows present in PAY_LINK_INPUT_VALUES_F are excluded. This pattern is the standard Oracle HRMS/Payroll "X" view convention and means the view is non-updatable for datetracking purposes and should not be used to persist changes; DML must target the base table.

Key Columns

  • LINK_INPUT_VALUE_ID — Primary identifier for the link input value definition row.
  • EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — The datetrack interval that determines whether the row is returned by the view.
  • ELEMENT_LINK_ID — Foreign reference to the element link to which the input value constraint applies.
  • INPUT_VALUE_ID — Foreign reference to the input value definition being constrained.
  • DEFAULT_VALUE — Default value assigned to the input value for this link.
  • MAX_VALUE — The upper bound permitted for the input value; this is the column most frequently targeted by searches on this object, since it defines validation limits applied during element entry.
  • MIN_VALUE — The lower bound permitted for the input value.
  • COSTED_FLAG — Indicates whether the input value is costed.
  • WARNING_OR_ERROR — Determines whether a breach of the minimum or maximum constraint raises a warning or a hard error during entry.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — Standard audit columns retained from the base table.

Common Use Cases and Queries

The view is typically used to audit or report constraint configuration for element links, to reconcile default and boundary values across environments, and to drive integrations that must read only presently active definitions. A representative query retrieving the active maximum and minimum values for a given link is:

SELECT liv.LINK_INPUT_VALUE_ID, liv.ELEMENT_LINK_ID, liv.INPUT_VALUE_ID,
       liv.DEFAULT_VALUE, liv.MIN_VALUE, liv.MAX_VALUE, liv.WARNING_OR_ERROR
  FROM apps.PAY_LINK_INPUT_VALUES_X liv
 WHERE liv.ELEMENT_LINK_ID = :p_element_link_id
 ORDER BY liv.INPUT_VALUE_ID;

To identify all currently effective rows where an upper bound is enforced:

SELECT LINK_INPUT_VALUE_ID, ELEMENT_LINK_ID, INPUT_VALUE_ID, MAX_VALUE
  FROM apps.PAY_LINK_INPUT_VALUES_X
 WHERE MAX_VALUE IS NOT NULL;

Because the view already restricts to the current effective interval, queries should generally not add their own SYSDATE predicate on the effective dates unless a different as-of date is required — in which case the base table PAY_LINK_INPUT_VALUES_F must be queried directly with an explicit date substitution. Join paths to PAY_ELEMENT_LINKS_F and PAY_INPUT_VALUES_F via ELEMENT_LINK_ID and INPUT_VALUE_ID respectively provide descriptive context for reporting.