Results for “get_user_table_name”

36 results




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

Overview

APPS.PQP_CONFIG_INFO_PKG is a configuration utility package body within the Oracle EBS Payroll process (PQP application family). It serves as a centralized access layer for resolving configuration data that the payroll engine requires at runtime, particularly for payroll-run related features such as mileage claims processing and user-defined configuration values. The package bridges statutory element configuration, user tables, and the PQP_CONFIGURATION_VALUES store, exposing reusable lookup routines so that other components — notably PQP_GB_MILEAGE_CLAIM_PKG and the PQP_PCV maintenance routines — do not need to query configuration tables directly. In EBS 12.1.1 and 12.2.2, the package is delivered as a VALID body in the APPS schema and is classified as an OTHER API rather than a public web-service API.

Key Procedures and Functions

The ETRM metadata documents three callable units within the package body:

  • GET_USER_TABLE_NAME — Resolves the physical name of a payroll user table defined in PAY_USER_TABLES, returning the table identifier used to locate related configuration rows. This allows callers to work with logical user-table definitions rather than hard-coded names.
  • GET_ELEMENT_NAME — Retrieves the element name associated with a payroll element type, reading from PAY_ELEMENT_TYPES_F. This supports statutory and configuration logic that must map an element ID to its user-facing name.
  • PQP_VEH_CALC_INFO — Returns configuration information relating to vehicle calculation, supporting mileage and vehicle-related claim processing. It draws on configuration values maintained through the PQP_PCV insert, update, and delete routines.

No parameter lists are documented; callers should reference the package specification in the target instance for exact signatures.

Tables Accessed

The package body references three documented tables, all through APPS synonyms:

  • PAY_ELEMENT_TYPES_F — the date-tracked element type definition table; read to obtain element names and related metadata for configuration lookups.
  • PAY_USER_TABLES — holds payroll user table definitions; read to resolve user table names used in configuration value storage.
  • PQP_CONFIGURATION_VALUES — the core configuration value store; read (and indirectly maintained through PQP_PCV_DEL, PQP_PCV_INS, and PQP_PCV_UPD, which are listed as dependencies) to supply runtime configuration to consumers such as the mileage claim package.

Additional dependencies include FND_FILE for log/output handling, HR_API for HRMS API utilities, and the PQP_GB_MILEAGE_CLAIM_PKG and PQP_PCV packages. Note that PQP_PCV_DEL, PQP_PCV_INS, and PQP_PCV_UPD appear to be package units co-located within the same body.

Usage Notes

PQP_CONFIG_INFO_PKG is an internal payroll configuration package rather than a user-facing API. It is invoked indirectly when payroll processes or related packages need to resolve element names, user table names, or vehicle/mileage configuration values. Typical call paths include the PQP_GB_MILEAGE_CLAIM_PKG during mileage claim processing, and custom extensions that require consistent access to PQP_CONFIGURATION_VALUES. The metadata records that the package is not referenced by any database object, indicating that its callers are PL/SQL packages and forms rather than database-level dependencies such as views or triggers. Custom code should call these routines instead of querying the underlying configuration tables directly, to preserve consistency when configuration maintenance routines update PQP_CONFIGURATION_VALUES. Because the API classification is OTHER, there is no documented commitment to external interface stability; customizations should be validated against each patch level in 12.1.1 and 12.2.2.