Search Results set_batchname_suffix_connector




Overview

HXT_INTERFACE_UTILITIES is a shared PL/SQL utility package residing in the APPS schema that supports the Oracle E-Business Suite time and labor interface infrastructure. Its primary responsibility is to provide common helper routines used by the Oracle Time and Labor (OTL / HXT) interface programs when transferring timecard data into the Oracle Payroll and supporting cost allocation structures. The package is classified as an OTHER API in the ETRM documentation, meaning it is not a public, externally facing interface but rather an internal support library invoked by other packages within the time and labor stack.

The utility package centralizes batching, caching, naming, and commit management logic that would otherwise be duplicated across retrieval and interface programs. It abstracts configuration concerns such as batch sizing, batch name generation, suffix handling, and the choice between legacy and current retro-processing batch behavior. By consolidating this logic, it ensures consistent behavior across the HXT_OTC_RETRIEVAL_INTERFACE and PAY_HR_OTC_RETRIEVAL_INTERFACE packages, both of which reference this utility package.

Key Procedures and Functions

The documented interface exposes 69 procedures and functions. The most prominent groupings are as follows:

Additional undocumented-in-excerpt helpers (the GRE prefix and other members) follow the same internal support pattern.

Tables Accessed

Usage Notes

This package is invoked indirectly by concurrent programs and interface routines rather than directly by end users. Its callers include HXT_OTC_RETRIEVAL_INTERFACE and PAY_HR_OTC_RETRIEVAL_INTERFACE, both of which rely on it for batching, commit management, and naming logic during timecard retrieval into BEE and payroll batch structures. Custom extensions that replicate OTL-to-Payroll workflows may reference the same utility routines where consistent batch behavior is required. Settings such as USE_OLD_RETRO_BATCHES, batch name suffix connectors, and maximum batch size are effectively controlled through the utility's setter procedures or profile options, allowing administrators to tune processing without code changes. Because the package is classified as OTHER and manages shared state, developers should treat it as internal infrastructure and avoid direct modification.