Results for “d_min_value”

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

Overview

PAY_INPUT_VALUES_V is an APPS-owned database view within the Oracle E-Business Suite Payroll (PAY) product module. It is classified as a UI-support view, meaning its primary purpose is to present element input value definitions in a translated, display-ready form for Oracle Forms-based user interfaces and for reporting or integration consumers that require the same presentation logic. Rather than exposing raw base table columns, the view joins name-translated rows, resolves flex value set names, decodes lookup codes into descriptive text, and applies formatting functions to numeric values such as default, minimum, and maximum amounts.

Because it surfaces decoded and formatted attributes, the view is commonly used as a convenient read-only source for data extracts, operational reports, and interfaces that need element input value metadata without re-implementing Oracle's decoding and formatting rules. It is valid and shipped in both EBS 12.1.1 and 12.2.2.

Underlying Base Objects

The view is defined over several documented base objects. The core transactional table is PAY_INPUT_VALUES_F, aliased as PIV, joined to its translation table PAY_INPUT_VALUES_F_TL (PIVTL) on INPUT_VALUE_ID with the language restricted to the session language via USERENV('LANG'). The element definition is sourced from PAY_ELEMENT_TYPES_F (ELEMENT), joined on ELEMENT_TYPE_ID. Optional formula information is drawn from FF_FORMULAS_F_VL (FF) through an outer join on FORMULA_ID, and flex value set names come from FND_FLEX_VALUE_SETS (FFVS) via an outer join on VALUE_SET_ID. FND_SESSIONS is referenced in the driving predicate.

Several PL/SQL packages are invoked within the SELECT list to transform stored values: HR_GENERAL supplies DECODE_LOOKUP for converting lookup codes such as UNITS and WARNING_ERROR into display text; HR_CHKFMT provides CHANGEFORMAT to render numeric values against the unit of measure and input currency code; and PAY_INPUT_VALUES_PKG supplies DECODE_VSET_VALUE for value-set-driven defaults.

Key Columns

• INPUT_VALUE_ID, ELEMENT_TYPE_ID — Primary identifiers linking the input value to its parent element type.
• NAME — Translated input value name; BASE_NAME is the untranslated base table name.
• LOOKUP_TYPE, VALUE_SET_ID, VALUE_SET_NAME — Validation source driving allowable entries.
• DEFAULT_VALUE, D_DEFAULT_VALUE — Stored default and its decoded/formatted display equivalent.
• MIN_VALUE, MAX_VALUE with D_MIN_VALUE, D_MAX_VALUE — Numeric boundaries and their formatted counterparts.
• UOM, UNIT_OF_MEASURE — Unit of measure code and decoded description.
• MANDATORY_FLAG, MANDATORY_FLAG_NAME, USER_ENTERABLE_FLAG — Entry control flags and derived indicators.
• WARNING_OR_ERROR, WARNING_OR_ERROR_NAME — Validation severity code and its decoded text.
• FORMULA_ID, FORMULA_NAME — Attached formula, if any.
• LEGISLATION_CODE, LEGISLATION_SUBGROUP, BUSINESS_GROUP_ID — Legislative and business group scoping.
• DISPLAY_SEQUENCE, HOT_DEFAULT_FLAG, GENERATE_DB_ITEMS_FLAG — Presentation and generation attributes.

Common Use Cases and Queries

Typical uses include validating element setup, documenting input value definitions for a given element, and feeding downstream interfaces with decoded defaults, ranges, and validation sources.

• List all input values for a specific element: SELECT name, d_default_value, uom, mandatory_flag_name FROM pay_input_values_v WHERE element_type_id = :element_type_id ORDER BY display_sequence;
• Identify validation sources: SELECT base_name, lookup_type, value_set_name FROM pay_input_values_v WHERE value_set_id IS NOT NULL;
• Report numeric ranges: SELECT base_name, d_min_value, d_max_value, unit_of_measure FROM pay_input_values_v WHERE legislation_code = :leg_code;

Consumers should treat the view as read-only and account for its dependence on session language, since NAME is returned only for rows matching USERENV('LANG').