Search Results get_insert_values

Overview

PAY_US_LOC_CHANGE is a PL/SQL package owned by the APPS schema that supports the United States localization of Oracle Payroll. Its documented purpose centers on the reporting and validation of employee location changes as they relate to tax unit assignments. When an employee's work location changes, the tax jurisdiction to which that employee reports may also change, and the payroll application must reconcile the affected assignment records and produce an audit or exception report. The package encapsulates the logic required to gather the relevant insertion values, stage intermediate results into a temporary table, update tax information tied to a location, and finally print the resulting report. The header comment identifies the source file as pyuslocu.pkh, with a version marker dated 2008, indicating that the interface has been stable across the 12.1.1 and 12.2.2 releases. The package is classified as OTHER in the ETRM metadata, meaning it is not an open or public API intended for external integration; it is an internal implementation unit used by Oracle Payroll US localization functionality.

Key Procedures and Functions

The package exposes four documented procedures, none of which are functions.

• CNT_PRINT_REPORT — Controls the counting and printing of the location change report. It is the reporting entry point that drives output once the underlying data has been gathered and staged.
• GET_INSERT_VALUES — Retrieves the values required for insertion into the temporary table. It accepts a processing name, an assignment identifier, and a location identifier, and returns the GRE name, full employee name, assignment number, and location code. This procedure performs the master data lookup that feeds the staging step.
• PUT_INTO_TEMP_TABLE — This is the procedure referenced by the search term "put_into_temp_table." It stages a single row of report data into a temporary table, carrying the tax unit name, location code, employee full name, assignment number, effective start and end dates, and an error indicator. The presence of the error parameter shows that the procedure doubles as a validation gateway: rows that fail tax or location validation are written with a populated error column so they can be surfaced in the report.
• UPDATE_TAX — Updates tax-related data for a given location. It follows the standard concurrent program signature convention with errbuf and retcode output parameters, plus an input location identifier, confirming that it is designed to be invoked directly as a concurrent program from a report or request set.

Tables Accessed

The package references four objects through APPS synonyms.

• PER_ALL_ASSIGNMENTS_F — The primary assignment table, read to obtain employee assignment records, effective dates, and assignment numbers associated with a location change.
• HR_SOFT_CODING_KEYFLEX — The key flexfield structure holding soft coding for assignments, consulted to resolve tax unit and location coding values.
• PAY_US_RPT_TOTALS — A US payroll reporting totals table used to accumulate or store summarized report figures.
• DUAL — Utilized for single-row evaluations and simple computations within the PL/SQL logic.

Usage Notes

PAY_US_LOC_CHANGE is an internal package and is not referenced by any other documented packages, which indicates it is invoked directly rather than composed into a larger API chain. UPDATE_TAX, with its errbuf and retcode parameters, is the natural concurrent program entry point and would typically be attached to a concurrent program definition and submitted from the Submit Requests form or a request set. The remaining procedures support the report pipeline and are called from within the package or from tightly coupled localization code. Because the object is classified as OTHER, customizations should not call these procedures directly; instead, developers should rely on supported payroll and HR APIs where equivalent functionality exists. The 120.0.12010000.1 version stamp suggests the package behaves consistently between EBS 12.1.1 and 12.2.2, with the primary 12.2 differences arising from the Online Patching editioning model rather than from changes to this package's interface.