Search Results upload_state_tax_record

Overview

APPS.HR_H2PI_PERSON_UPLOAD is a PL/SQL package that forms part of the Oracle Human Resources "H2PI" (HR-to-Payroll Interface / person upload) infrastructure. Its purpose is to move person-related data staged in a set of HR_H2PI_ interface tables into the corresponding Oracle HRMS and Oracle Payroll base tables. The package declares AUTHID CURRENT_USER, meaning its SQL statements execute with the privileges of the invoking schema rather than the package owner, which is important when it is called from concurrent program contexts or custom code running under a different schema.

The package is organized around a series of granular upload procedures, each responsible for a single logical entity — person, address, assignment, salary, payment method, cost allocation, element entry, and statutory tax records. A driver procedure, upload_person_level, coordinates the broader upload flow, while the remaining procedures handle individual record types. This module-level design allows the interface to process records incrementally and to isolate failures to a specific entity type.

Key Procedures and Functions

The documented interface exposes seventeen procedures:

• UPLOAD_PERSON_LEVEL — the top-level driver that initiates person-level processing for a given client identifier.
• UPLOAD_PERSON — loads a person record identified by person ID and effective start date.
• DELETE_ADDRESS and UPLOAD_ADDRESS — remove or load address records respectively.
• TERMINATE_PERSON — applies a termination to an existing person record.
• UPLOAD_ASSIGNMENT — the procedure matched by the user's search term; loads assignment data for a person from the staged interface tables.
• UPLOAD_PERIOD_OF_SERVICE — loads period-of-service records associated with an assignment.
• UPLOAD_SALARY — loads salary proposals into payroll.
• UPLOAD_PAYMENT_METHOD — loads personal payment method information.
• UPLOAD_COST_ALLOCATION — loads cost allocation distributions.
• UPLOAD_ELEMENT_ENTRY — loads element entries, including associated entry values, links, names, and types.
• UPLOAD_FEDERAL_TAX_RECORD, UPLOAD_STATE_TAX_RECORD, UPLOAD_COUNTY_TAX_RECORD, UPLOAD_CITY_TAX_RECORD — load the respective employee tax rules.
• UPLOAD_TAX_PERCENTAGE — loads tax percentage details.
• CREATE_END_DATE_RECORDS — generates end-dated records for entities being closed out during the upload.

The metadata does not document the full parameter signatures beyond the source excerpt, so parameter details for each procedure should be confirmed against the package specification in the target environment.

Tables Accessed

The package reads from and writes to a family of HR_H2PI_ interface tables via APPS synonyms. These include HR_H2PI_EMPLOYEES and HR_H2PI_ASSIGNMENTS for core person and assignment staging; HR_H2PI_ADDRESSES for address data; HR_H2PI_COST_ALLOCATIONS for costing; the element-related tables HR_H2PI_ELEMENT_ENTRIES, HR_H2PI_ELEMENT_ENTRY_VALUES, HR_H2PI_ELEMENT_LINKS, HR_H2PI_ELEMENT_NAMES, and HR_H2PI_ELEMENT_TYPES; the statutory tax staging tables HR_H2PI_FEDERAL_TAX_RULES, HR_H2PI_CITY_TAX_RULES, and HR_H2PI_COUNTY_TAX_RULES; and the supporting tables HR_H2PI_BG_AND_GRE, HR_H2PI_HR_ORGANIZATIONS, and HR_H2PI_ID_MAPPING, the last of which maps source identifiers to generated Oracle HRMS identifiers during upload.

Usage Notes

HR_H2PI_PERSON_UPLOAD is not intended for direct ad-hoc invocation. It is normally called by the H2PI person upload concurrent program or by other H2PI packages that orchestrate the interface; the metadata records that it is referenced by one other package. Customers typically populate the HR_H2PI_ staging tables from an external source system (for example, a third-party HR system or legacy conversion), then run the upload process to transform and load the data into Oracle HRMS.

Because the procedures use AUTHID CURRENT_USER, callers must ensure the executing schema has appropriate privileges on the HR_H2PI and HRMS tables. Any custom code or wrapper should invoke the procedures in the documented sequence — person level first, then dependent entities such as assignment, salary, and tax records — and should validate staged data before execution. Always verify the exact signature and behavior against the package specification in your specific EBS 12.1.1 or 12.2.2 instance, as the metadata excerpt provided here is abbreviated.