Results for “delete_tax_record”

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

Overview

The APPS.PER_US_EXTRA_REHIRE_RULES package is a United States-specific Oracle Human Resources (HR) extension delivered as part of the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 codebase. Its name and structure indicate that it encapsulates supplemental business rules required when an employee is rehired, specifically the additional processing steps that fall outside the standard Oracle Payroll and HR rehire logic. In the United States localization, a rehire event carries statutory and payroll implications — particularly around the recalculation of tax records associated with prior periods of service — that are not handled by the core rehire functionality. This package exists to centralize those rules so that rehire transactions in US legislation trigger the correct downstream tax cleanup.

The package is classified under the API classification OTHER, meaning it is not a public, supported integration API in the same sense as an OPEN or CUSTOM hook API. It is an internal extension point invoked by Oracle's own HR and Payroll processing rather than a routine intended for direct customer invocation. This classification is important context for anyone considering using it: it is documented for reference and supportability, but not positioned as a public interface.

Key Procedures and Functions

The package exposes a single documented procedure:

• DELETE_TAX_RECORD — Removes the tax record associated with a specified period of service as part of the extra rehire processing. The procedure accepts a final process date and a period of service identifier, reflecting that the tax record must be tied to a defined period of service and honored against a cutoff date. No additional signatures are documented; the parameter list above is the complete documented interface.

No functions are declared in the documented specification, and no additional procedures are listed. The comment block at the top of the package specification indicates an internal Oracle source header (peexehcc.pkh), confirming that the package is a seeded component of the US HR localization rather than a customer-extensible object.

Tables Accessed

The package operates against two Oracle HR base tables, resolved through APPS synonyms:

• PER_PERIODS_OF_SERVICE — The central HR table that stores an employee's periods of service, including assignment relationships and the start and end dates of each service period. The p_period_of_service_id parameter identifies the specific record acted upon, and this table is read to locate and validate the period of service tied to the rehire event.
• PER_ADDRESSES — The HR table holding address records, typically used to support tax jurisdiction determination. Because US tax processing depends on the employee's address to establish the applicable tax rules, this table is referenced in conjunction with the tax record removal.

Because the procedure is named DELETE_TAX_RECORD, the intent is deletion of tax data associated with the identified period of service, with the final process date providing the cutoff for which records are eligible.

Usage Notes

The package is referenced by one other package within the EBS codebase, confirming that it is invoked programmatically by Oracle's own HR rehire processing rather than exposed directly to end users. It is not surfaced through a standard form or concurrent program and does not carry an OPEN or CUSTOM API classification. Consequently, it should be treated as a supporting internal component that fires during US rehire processing to reconcile tax records that would otherwise remain attached to a superseded period of service.

Customers and developers should not call DELETE_TAX_RECORD directly as a substitute for standard rehire transactions. In the event of custom rehire automation in US legislation, the package can be referenced as the Oracle mechanism for the same tax cleanup, but any invocation outside Oracle's delivered flows risks leaving tax records and periods of service inconsistent. The safest posture is to allow the standard rehire process to invoke it and to treat the package as read-only documentation of the delivered rehire rule set in EBS 12.1.1 and 12.2.2.