Results for “paybv_input_value”

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

Overview

PAYBV_INPUT_VALUE is a read-only APPS view in the Oracle E-Business Suite Payroll (PAY) module. It presents descriptive and configuration data for payroll element input values, exposing the definitional attributes that govern how an input value behaves when an element is processed. The view is a business-facing (BV) layer that translates internal lookup codes into user-readable decoded values, allowing reports, concurrent programs, and integrations to consume input value metadata without implementing their own decode logic. In both release 12.1.1 and 12.2.2 the view is owned by APPS and carries VALID status, and it is defined with the WITH READ ONLY clause, meaning it is intended exclusively for query access and cannot be used as a DML target.

Underlying Base Objects

The view is defined over two core Payroll tables and one package. The primary base object is PAY_INPUT_VALUES_F (referenced through a synonym), which stores the effective-dated, language-independent definition of each input value. It is joined to PAY_INPUT_VALUES_F_TL, the translation table, which supplies the language-specific NAME based on the session language obtained from USERENV('LANG'). The join is performed on INPUT_VALUE_ID, with the translation restricted to the current session language. The package HR_BIS is referenced through its functions BIS_DECODE_LOOKUP, GET_LEGISLATION_CODE, and GET_SEC_PROFILE_BG_ID. BIS_DECODE_LOOKUP converts stored lookup codes into display values, while GET_LEGISLATION_CODE and GET_SEC_PROFILE_BG_ID supply security context used to compute the business group access indicator. The documented referenced objects are therefore HR_BIS (PACKAGE), PAY_INPUT_VALUES_F (SYNONYM), and PAY_INPUT_VALUES_F_TL (SYNONYM).

Key Columns

The view exposes both decoded display columns and raw code columns, which supports presentation and programmatic filtering alike.

• NAME – the language-specific name of the input value derived from the translation table.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE – the date range during which the input value definition is valid.
• GENERATE_DB_ITEMS_FLAG – decoded YES_NO indicator controlling whether database items are generated for the input value; the underlying code is exposed as GENERATE_DB_ITEMS_FLAG_CODE.
• HOT_DEFAULT_FLAG / MANDATORY_FLAG – decoded YES_NO flags, each paired with a _CODE column, indicating whether the input receives the hot default and whether entry is mandatory.
• UOM – decoded unit of measure, with UOM_CODE retaining the underlying lookup value.
• WARNING_OR_ERROR – decoded WARNING_ERROR indicator, with WARNING_OR_ERROR_CODE preserved.
• DEFAULT_VALUE, MIN_VALUE, MAX_VALUE – the default entry and permitted range for the input value.
• LOOKUP_TYPE, LEGISLATION_CODE, LEGISLATION_SUBGROUP, DISPLAY_SEQUENCE – classification and ordering attributes.
• INPUT_VALUE_ID, ELEMENT_TYPE_ID, BUSINESS_GROUP_ID, FORMULA_ID, VALUE_SET_ID – primary and foreign key identifiers.
• BG_SECURITY_FLAG_CODE – computed as 'Y' or 'N' based on business group and legislation security logic.
• Audit columns – LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE, OBJECT_VERSION_NUMBER.

Common Use Cases and Queries

PAYBV_INPUT_VALUE is commonly queried to document element configurations, validate range and default settings, and drive data migrations between environments. A frequent use is identifying whether database items are generated for inputs, which is the purpose behind the generate_db_items_flag search term.

• Review inputs that generate database items:
  SELECT name, input_value_id, generate_db_items_flag FROM apps.paybv_input_value WHERE generate_db_items_flag = 'Yes';
• Filter by element type and effective date:
  SELECT name, effective_start_date, effective_end_date, mandatory_flag FROM apps.paybv_input_value WHERE element_type_id = :p_element_type_id AND SYSDATE BETWEEN effective_start_date AND effective_end_date;
• Compare decoded values against their codes for a specific legislation.

Because the view is read-only and security-filtered through BG_SECURITY_FLAG_CODE, consumers should apply the appropriate business group and legislation predicates to align results with the querying responsibility.