Search Results add_to_batch




Overview

APPS.PAY_HR_OTC_RETRIEVAL_INTERFACE is an Oracle E-Business Suite payroll-side interface package that bridges Oracle Time and Labor (OTL) retrieval data with Oracle Payroll batch processing. Its principal business function is to consolidate timecard and retrieval information originating from the HXC (Oracle Time and Labor) schema into the PAY_BATCH_HEADERS and PAY_BATCH_LINES structures so that payroll runs can process the resulting elements, including adjustments, retroactive entries, and BEE (Batch Element Entry) transactions. In effect, the package acts as a batch loader and converter, transforming OTL transactions and building blocks into payroll batch lines that payroll costing and processing can consume.

The header comment identifies the source file as pytshpri.pkb (version 120.8), confirming that the package is part of the standard payroll time-and-labor integration delivered in EBS 12.1.1 and 12.2.2. The package operates on a global package name (pay_hr_otc_retrieval_interface.), declares standard global exceptions (e_continue, e_halt), and maintains state such as g_batches_created and a g_retro_batch_suffix constant defaulting to '_RETRO'. A display_value function converts internal LOV codes to their displayed meanings by joining PAY_INPUT_VALUES_F and PAY_ELEMENT_TYPES_F.

Key Procedures and Functions

The documented API surface contains twenty procedures and functions, which fall into several logical groups:

Tables Accessed

The package references the following tables through APPS synonyms:

Usage Notes

PAY_HR_OTC_RETRIEVAL_INTERFACE is invoked indirectly through Oracle Payroll and Oracle Time and Labor retrieval concurrent programs rather than directly by end users. The package is referenced by zero other PL/SQL packages in the ETRM catalog, indicating it is a terminal consumer called from concurrent program definitions and form-driven retrieval flows. Customizations should not call the internal procedures directly where a supported concurrent program exists, but diagnostic or extension code may legitimately reference ADD_TO_BATCH, BATCH_NAME, and BATCHES_CREATED when auditing or extending batch generation. Because the package writes to PAY_BATCH_HEADERS and PAY_BATCH_LINES, any direct invocation must respect batch rollback semantics via MARK_BATCHES_FOR_ROLLBACK to avoid orphaned or duplicate batch lines. Integration must be enabled (validated by CHK_INTG_ENABLED) before OTL data is transferred to HR/Payroll.