Search Results pay_link_input_values_f_pk

Overview

PAY_LINK_INPUT_VALUES_F is a datetracked (effective-dated) table owned by the HR schema within the Payroll (PAY) product module of Oracle E-Business Suite. It stores input value overrides that apply to a specific element link. In Oracle Payroll, an element is a compensation or deduction component, and an element link determines which employees are eligible to receive that element and how it is processed. When a link requires that certain input values be constrained, defaulted, or overridden at the link level, those rules are persisted in this table. The "_F" suffix denotes the base datetrack table, which is consistently paired with a "_VL" or "_V" view that provides the developer-facing interface.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign-key structure is standalone. This suggests the table behaves as a self-contained reference structure rather than participating in the classic hub-and-link topology; its identity is defined by its own surrogate key and business keys rather than by relationships to other hubs. Modelers should treat it as an independent datetracked entity that can be referenced by, or joined loosely to, the surrounding payroll configuration model.

Key Information Stored

The table contains 16 documented columns. The most significant are described below.

• LINK_INPUT_VALUE_ID — the surrogate primary key, defined by PAY_LINK_INPUT_VALUES_F_PK together with the effective dates.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the datetrack date range that governs when the override is valid. These are part of both the primary key and the business key.
• ELEMENT_LINK_ID — identifies the element link to which this input value override applies; this is a key join column to the element link definition.
• INPUT_VALUE_ID — identifies the specific input value definition being overridden for that link.
• COSTED_FLAG — indicates whether the input value is costed for this link.
• DEFAULT_VALUE — the value applied when no explicit value is supplied at runtime.
• MAX_VALUE / MIN_VALUE — the permitted numeric boundaries for the input value.
• WARNING_OR_ERROR — controls whether a boundary violation raises a warning or a hard error.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the OAF/ADF framework to detect concurrent updates.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, and CREATION_DATE provide standard "who/when" tracking.

The second unique index, PAY_LINK_INPUT_VALUES_F_U50, on (ELEMENT_LINK_ID, INPUT_VALUE_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE), establishes the business-key candidate: for any given element link and input value, only one override may exist per effective date range.

Common Use Cases and Queries

Typical usage centers on validating and reporting the constraints applied to element links. A common query retrieves the active overrides for a given link as of a specific date:

• SELECT input_value_id, default_value, min_value, max_value, warning_or_error FROM pay_link_input_values_f WHERE element_link_id = :link_id AND TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date;
• Discovery of all constrained inputs for an element via joining to PAY_ELEMENT_LINKS_F on element_link_id.
• Audit reporting that lists default values and boundary rules that changed between two effective dates.
• Validation of timecard and element entry screens where DEFAULT_VALUE and MIN/MAX_VALUE drive user entry restrictions.

Consumers should generally query the corresponding _VL view to obtain the correct datetrack context and translated display values rather than the base table.

Related Objects

Because the table is classified as standalone, it has no explicit foreign keys in the supplied metadata, but it logically references and is referenced by the following:

• PAY_ELEMENT_LINKS_F — joined on ELEMENT_LINK_ID; the link whose overrides are stored here.
• PAY_INPUT_VALUES_F — joined on INPUT_VALUE_ID; defines the input value being overridden.
• PAY_LINK_INPUT_VALUES_F_VL — the developer-facing datetrack view over this base table.
• PAY_ELEMENT_LINKS_VL — provides the effective-dated view of the related link for reporting joins.
• PAY_INPUT_VALUES_VL — supplies descriptive context for the input value.
• PAY_ELEMENTS_F — reached transitively via the element link; useful for element-level reporting.
• PAY_ELEMENT_ENTRY_VALUES_F — stores actual entry values validated against the constraints defined here.