Search Results pay_link_input_values_f_u50

Overview

PAY_LINK_INPUT_VALUES_F is a DateTracked table owned by the HR schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It stores input value settings defined at the element link level, allowing each link rule to override the input value definitions inherited from the parent element. Through this mechanism, individual links can carry their own default values, validation limits, and warning or error behaviour, independent of the element-level definition. The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and its indexes are held in APPS_TS_TX_IDX. From a Data Vault modelling perspective, the mined relationship structure classifies this object as standalone; a satellite-style treatment keyed on the business unique index would be a reasonable heuristic suggestion, since the table records descriptive attribute values in an effective-dated context rather than acting as a hub or link.

Key Information Stored

The surrogate primary key, enforced through PAY_LINK_INPUT_VALUES_F_PK, is composed of LINK_INPUT_VALUE_ID, EFFECTIVE_START_DATE, and EFFECTIVE_END_DATE. The business-key candidate is captured by the unique index PAY_LINK_INPUT_VALUES_F_U50, which spans ELEMENT_LINK_ID, INPUT_VALUE_ID, EFFECTIVE_START_DATE, and EFFECTIVE_END_DATE; this index is the object most commonly referenced in searches. ELEMENT_LINK_ID identifies the element link rule that owns the override, while INPUT_VALUE_ID identifies the specific input value being customised.

The attribute columns define the override behaviour. DEFAULT_VALUE holds the value proposed at entry time, which may still be overridden for a particular element entry. MIN_VALUE and MAX_VALUE set the permissible boundaries for entry. WARNING_OR_ERROR determines whether a warning or an error is raised when the input value fails formula validation. COSTED_FLAG indicates whether the input value participates in costing. The remaining columns are standard Oracle EBS Who columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE, and OBJECT_VERSION_NUMBER, which supports optimistic locking in the OAF framework. The table contains sixteen documented columns in total.

Common Use Cases and Queries

Typical reporting scenarios include auditing link-level overrides against element-level defaults, verifying that minimum and maximum boundaries are consistently applied, and identifying links where costed inputs have been configured. A representative query joining the link and input value identifiers is:

• SELECT link_input_value_id, element_link_id, input_value_id, default_value, min_value, max_value FROM pay_link_input_values_f WHERE element_link_id = :p_link_id AND TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date;
• Querying by the U50 index columns (element_link_id, input_value_id, effective_start_date, effective_end_date) delivers the most efficient access path for point lookups.
• DateTrack-aware queries must always include the effective date predicate, since multiple dated rows exist for the same logical configuration.

Related Objects

The table participates in the Oracle Payroll element link configuration model. The most significant related objects include PAY_ELEMENT_LINKS_F, joined via ELEMENT_LINK_ID, which holds the link rule itself; PAY_INPUT_VALUES_F, joined via INPUT_VALUE_ID, which supplies the element-level input value definition being overridden; PAY_ELEMENT_TYPES_F, reached indirectly through the link to the element type; PAY_ELEMENT_ENTRIES_F and PAY_ELEMENT_ENTRY_VALUES_F, which store the values actually entered for a person assignment; PAY_COST_ALLOCATIONS_F, relevant where COSTED_FLAG is set; and FND_USER, joined via LAST_UPDATED_BY or CREATED_BY. The corresponding DateTracked business logic is generally driven through the Payroll element link and input value APIs rather than direct DML against this table.