Search Results ut_lov_conversion




Overview
Explore in AI Chat

Overview

PAY_USER_TABLES_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports the maintenance of user-defined tables within Oracle Payroll. In EBS, a "user table" is a configurable validation source that allows implementers and payroll administrators to define their own lists of values — for example, employee categories, union codes, or pay-basis groupings — that can then be referenced during element entry, payroll processing, or validation of user-defined input values. The package provides the underlying programmatic interface to the PAY_USER_TABLES, PAY_USER_ROWS_F, PAY_USER_COLUMNS, and related translation tables, exposing the standard insert, update, delete, and lock operations expected of an EBS entity API, together with validation and utility routines. It is classified as an OTHER API rather than a public HR/Payroll API, meaning it is primarily intended for internal use by Oracle Forms and other seeded components rather than for direct customer invocation, although it may be called from custom extensions with care.

Key Procedures and Functions

  • INSERT_ROW — Creates a new user table definition, capturing business group, legislation, range or match behaviour, key units, table name, and row title.
  • UPDATE_ROW — Modifies an existing user table, optionally updating base table name and base row title attributes.
  • DELETE_ROW — Removes a user table identified by ROWID and USER_TABLE_ID.
  • LOCK_ROW — Obtains a lock on a user table record to support concurrent-edit protection in the forms layer.
  • CHECK_UNIQUE — Validates that the user_table_name is unique within the business group and legislation code, raising an error if a duplicate exists.
  • CHECK_REFERENCES — Verifies that no dependent rows exist before a delete or key change is permitted.
  • GET_DB_DEFAULTS — Returns default column values for a new record, typically invoked when a form initialises a fresh block.
  • UT_LOV_CONVERSION — Performs conversion of user-table list-of-values data; this is the routine matching the user search term. It is used to translate or reformat stored user-table row values so they can be presented in an LOV, and is commonly referenced when investigating how user table LOV entries are derived.
  • ADD_LANGUAGE — Inserts a translated row into PAY_USER_TABLES_TL for an additional language.
  • TRANSLATE_ROW — Updates translatable attributes (such as row title) for a given language.
  • VALIDATE_TRANSLATION — Confirms that translation data is valid before commit.
  • CHECK_BASE_UPDATE — Validates changes to base user table attributes.
  • RETURN_DML_STATUS — Returns the value of the global g_dml_status flag, indicating whether a row-level DML operation succeeded.

Tables Accessed

  • PAY_USER_TABLES / PAY_USER_TABLES_S — The base and shift (date-tracked) definition tables for user tables.
  • PAY_USER_TABLES_TL — Translation table holding language-specific row titles.
  • PAY_USER_ROWS_F — The rows (values) belonging to each user table.
  • PAY_USER_COLUMNS — Defines the available columns usable within user tables.
  • FND_LANGUAGES — Supplies installed language information for the translation routines.

Usage Notes

PAY_USER_TABLES_PKG is referenced by eleven other packages, indicating a central role in the Payroll user-table maintenance layer. It is normally invoked indirectly through the seeded "User Tables" Form (typically PYUSRTAB), whose blocks call INSERT_ROW, UPDATE_ROW, DELETE_ROW, and LOCK_ROW on commit. The UT_LOV_CONVERSION routine is encountered most often where forms present a list of values populated from user tables; custom developers diagnosing LOV display issues should inspect this procedure. Direct calls from custom concurrent programs or APIs are possible but are not officially supported, and Rowid-based LOCK_ROW semantics make it unsuitable for set-based batch processing.