Results for “pay_input_values_f”

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

Overview

PAY_INPUT_VALUES_F is the HR-owner, payroll-module table that stores the input value definitions associated with specific payroll elements. In effect, it is the metadata catalog through which Oracle Payroll declares which entry values an element can accept, how those values are validated, defaulted, and displayed, and how they are sequenced. Because input values feed the element's runtime processing directly, this table sits at the boundary between payroll configuration and payroll execution.

The object follows the standard Oracle E-Business Suite date-tracked (or "date-effective") design pattern: each row is bounded by EFFECTIVE_START_DATE and EFFECTIVE_END_DATE, and multiple versions of the same logical definition can coexist as long as their date ranges do not overlap. The _F suffix on the table name denotes this date-effective structure.

With respect to Data Vault modeling, the metadata classifies the object heuristically as standalone. This suggests modeling PAY_INPUT_VALUES_F primarily as a satellite-like entity rather than as a pure hub or link, with the versioned rows acting as descriptive payload around the element context. The classification is a heuristic derived from the FK structure and should be validated against local modeling standards.

Key Information Stored

The surrogate primary key PAY_INPUT_VALUES_F_PK is composed of INPUT_VALUE_ID, EFFECTIVE_START_DATE, and EFFECTIVE_END_DATE (with ZD_EDITION_NAME appended in the documented 12.2.2 physical schema). The business-key candidate PAY_INPUT_VALUES_F_UK2 is defined over ELEMENT_TYPE_ID, NAME, BUSINESS_GROUP_ID, LEGISLATION_CODE, and the two date-effective columns. Important columns include:

• INPUT_VALUE_ID — unique identifier for the input value definition.
• ELEMENT_TYPE_ID — the payroll element to which the input value belongs.
• NAME — the identifier of the input value as referenced in element formulas and links.
• BUSINESS_GROUP_ID — the business group owning the definition.
• LEGISLATION_CODE and LEGISLATION_SUBGROUP — territory scoping.
• LOOKUP_TYPE — the validation lookup governing allowable values.
• VALUE_SET_ID — reference to an approved value set (FK to FRM_PART_VALUE_SETS).
• FORMULA_ID — calculation formula used for the value.
• DEFAULT_VALUE, MIN_VALUE, MAX_VALUE, WARNING_OR_ERROR — defaulting and validation behavior.
• MANDATORY_FLAG, HOT_DEFAULT_FLAG, GENERATE_DB_ITEMS_FLAG — entry and processing controls.
• DISPLAY_SEQUENCE — ordering when the element is presented for input.
• Standard audit columns LAST_UPDATE_DATE, CREATED_BY, CREATION_DATE, and OBJECT_VERSION_NUMBER.

Common Use Cases and Queries

Typical uses include validating payroll setup during implementations, auditing input value changes across date ranges, and building payroll element configuration reports.

• List active input values for an element as of a date:

  SELECT name, default_value, lookup_type, mandatory_flag FROM pay_input_values_f WHERE element_type_id = :element_id AND :eff_date BETWEEN effective_start_date AND effective_end_date;

• Identify all versions of an input value for historical audit, ordering by EFFECTIVE_START_DATE.
• Detect value-set-driven inputs by joining to FRM_PART_VALUE_SETS on VALUE_SET_ID.
• Reconcile inputs across business groups or legislations using the BUSINESS_GROUP_ID and LEGISLATION_CODE predicates from PAY_INPUT_VALUES_F_UK2.

Related Objects

The most significant relationships documented are:

• PAY_ELEMENT_TYPES_F — the element definition joined via ELEMENT_TYPE_ID.
• FRM_PART_VALUE_SETS — referenced through VALUE_SET_ID.
• FF_FORMULAS_F — joined via FORMULA_ID for input value calculations.
• PAY_INPUT_VALUES_TL — translated names and descriptions.
• FF_FORMULA_FUNCTIONS and element links, which consume the input value NAME at runtime.