Results for “pay_input_values_x”

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

Overview

PAY_INPUT_VALUES_X is a date-effective (date-tracked) view owned by the APPS schema in Oracle E-Business Suite, belonging to the PAY (Payroll) product family. It presents input values that are defined against element types within Oracle Payroll and related modules. An input value represents a data entry point associated with an element — such as hours worked, a rate, or an override amount — that feeds the payroll run and the formula processing engine.

Because input value definitions are date-tracked, PAY_INPUT_VALUES_X filters the underlying datable to expose only the rows whose effective date range encloses the current system date. This makes the view the standard reporting and integration interface for obtaining the currently active definition of each input value, without requiring callers to write their own effective-dating predicates. It is commonly consumed by BI Publisher reports, extracts, Fast Formulas, and interfaces that need a stable, "as-of-today" picture of payroll input configuration.

Underlying Base Objects

The view is defined over two synonymous base objects in the APPS schema:

• PAY_INPUT_VALUES_F — the date-effective (F) table holding the analytical definition of each input value, keyed on INPUT_VALUE_ID plus EFFECTIVE_START_DATE/EFFECTIVE_END_DATE.
• PAY_INPUT_VALUES_F_TL — the translation (TL) table holding the language-dependent NAME attribute.

The join is made on INPUT_VALUE_ID, with the translation restricted to IVTL.LANGUAGE = USERENV('LANG'), so only the session's language row is returned. The date-effective predicate is applied as TRUNC(SYSDATE) BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE. The view also substitutes the base table's internal NAME column with the translated NAME and re-labels the base NAME as SYSTEM_NAME, allowing both the user-facing and system identifiers to be exposed side by side.

Key Columns

• INPUT_VALUE_ID — primary identifier of the input value definition.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — date-effectiveness boundaries of the row.
• ELEMENT_TYPE_ID — the element type to which this input value belongs.
• NAME — the translated, user-facing name of the input value.
• SYSTEM_NAME — the untranslated internal name used for formulas and code references.
• LOOKUP_TYPE / UOM / DEFAULT_VALUE — validation list, unit of measure, and default entry value.
• MANDATORY_FLAG / HOT_DEFAULT_FLAG / GENERATE_DB_ITEMS_FLAG — behaviour flags governing entry and database item generation.
• FORMULA_ID — associated formula, where applicable.
• MIN_VALUE / MAX_VALUE / WARNING_OR_ERROR — validation bounds and enforcement mode.
• DISPLAY_SEQUENCE, LEGISLATION_CODE, LEGISLATION_SUBGROUP, BUSINESS_GROUP_ID — ordering and legislative/organisational scoping.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

Typical uses include validating input value configuration for an element type, extracting active input definitions for integration, and resolving the SYSTEM_NAME to match formula references. A representative query follows:

SELECT input_value_id, element_type_id, name, system_name,
       uom, default_value, mandatory_flag, min_value, max_value
FROM   apps.pay_input_values_x
WHERE  element_type_id = :p_element_type_id
ORDER BY display_sequence;

To locate an input by its internal identifier:

SELECT name, system_name, effective_start_date, effective_end_date
FROM   apps.pay_input_values_x
WHERE  system_name = 'HOURS_WORKED';

Because the view already enforces the current-date effectiveness and language filters, consumers should avoid adding redundant date predicates to the underlying F table and instead query this view directly for active definitions.