Results for “return_old_element_name”

8 results




Overview
Explore in AI Chat

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

Overview

The APPS.PQP_FEDHR_USPAY_INT_UTILS package is a utility package within the Oracle E-Business Suite Payroll (PQP) module, classified under the Federal HR / US Payroll integration area. Its name and source header indicate that it was originally delivered as part of a Federal HR payroll extension (pqpfhexr.pkh), and it operates against the standard Oracle Payroll data model using APPS synonyms. The package serves as a shared helper library for element name resolution and configuration-driven lookups, allowing Federal payroll processing to translate, validate, or substitute element names based on entries held in the PQP_CONFIGURATION_VALUES table rather than relying on fixed, hard-coded element names. Its access status is documented as Internal Development Use Only, which means it is intended primarily for Oracle internal development rather than as a supported public API. Nevertheless, the ETRM metadata records that it is referenced by 23 other packages, indicating that it is a frequently called foundation utility within the payroll code base.

Key Procedures and Functions

The ETRM metadata documents seven procedures and functions, of which five are named. The most prominent routines are concerned with element name resolution:

  • RETURN_NEW_ELEMENT_NAME — Returns a new element name when a corresponding entry exists in PQP_CONFIGURATION_VALUES; otherwise it returns the element name passed to it unchanged. This is the core configuration-aware lookup routine.
  • RETURN_OLD_ELEMENT_NAME — The counterpart of the above, resolving an element name back to its original, pre-configuration value. This is the routine associated with the user's search term.
  • IS_ELE_LINK_EXISTS — Determines whether an element link exists for a given element and business context, allowing callers to avoid duplicate or invalid link creation.
  • IS_SCRIPT_RUN — Checks whether a script (typically a payroll or configuration script) has already been executed, supporting idempotent processing.
  • PAY_BASIS_TO_SAL_BASIS — Translates a payroll basis value into a salary basis value, consistent with the package's use of PER_PAY_BASES.

The remaining documented routines are unnamed in the excerpt but are of the same utility character: short, single-purpose helpers used by other payroll packages. Parameter lists are not reproduced here because the available metadata documents only the signature of RETURN_NEW_ELEMENT_NAME and leaves the others to be confirmed against the deployed source.

Tables Accessed

The package reads from and writes to a set of standard Oracle Payroll and HR tables, all accessed via APPS synonyms:

  • PQP_CONFIGURATION_VALUES — The primary configuration store consulted by the element name resolution routines.
  • PAY_ELEMENT_TYPES_F — The element type definitions used to validate and resolve element names.
  • PAY_ELEMENT_LINKS_F — The element link definitions checked by IS_ELE_LINK_EXISTS.
  • PAY_INPUT_VALUES_F — The input value definitions associated with elements, used when resolving or validating element metadata.
  • PER_PAY_BASES — The pay basis definitions supporting the pay basis to salary basis conversion routine.
  • PER_ALL_ASSIGNMENTS_F — The assignment records used to establish the employee or assignment context for element and link checks.
  • PLITBLM — The standard PL/SQL index-by table used internally for bulk or list processing within the package.

Usage Notes

Because the package is marked for internal development use, it is not exposed through a user-facing form or concurrent program. Instead, it is invoked from PL/SQL — primarily from other payroll packages, as evidenced by its 23 documented dependents, and secondarily from custom extensions or fast formulas that require configuration-aware element name resolution. Typical invocation points include batch payroll processing, element link maintenance routines, and configuration-driven scripts where the effective element name may vary by business group and effective date. Callers should treat the package as version-sensitive: since it is not a public API, its behavior may change between releases and patches, and any custom code that references it should be regression-tested on upgrade from 12.1.1 to 12.2.2. For the specific search term return_old_element_name, the relevant entry point is the RETURN_OLD_ELEMENT_NAME function, which reverses the configuration-driven substitution performed by RETURN_NEW_ELEMENT_NAME.