Results for “get_request_id”

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

Overview

APPS.HR_H2PI_MAIN_UPLOAD is the controller package body for the HR "H2PI" (Human Resources to Payroll Interface) data load process in Oracle E-Business Suite. It orchestrates the movement of externally supplied staging data into the Oracle HRMS and Oracle Payroll tables. The package works against the HR_H2PI_* family of staging tables, which are populated by external sources, and coordinates validation, cleanup, and the insertion/update of records into the production HR and Payroll schema. In the context of the 12.1.1 and 12.2.2 releases, the package effectively serves as the master driver invoked by the H2PI upload concurrent program. Its embedded header (hrh2pimn.pkb 120.0) confirms it is a delivered Oracle application object owned by APPS.

Key Procedures and Functions

The package exposes five documented components:

• UPLOAD — The primary entry point. It drives the full load of staged data for a given run, invoking the individual table-level upload logic that transforms and transfers staging records into the HR and Payroll base tables.
• RETRY_UPLOAD — Provides a re-execution path for records that failed a prior upload attempt, allowing users to correct and reprocess failed rows without reloading the entire data set.
• CLEAR_STAGING_TABLES — Removes rows from the staging tables for a specified client. The source excerpt shows it accepts p_from_client_id NUMBER and performs a series of DELETE statements against each HR_H2PI_* staging table filtered by client_id.
• GET_FROM_BUSINESS_GROUP_ID — Retrieval utility used to obtain the Business Group identifier, which governs the organization context for the upload.
• GET_REQUEST_ID — Retrieval utility that returns the concurrent request identifier, enabling the package to track and report its execution.

Tables Accessed

The package reads from and writes to the HR_H2PI_* staging tables and supporting HR entities. Documented references include HR_H2PI_EMPLOYEES, HR_H2PI_ADDRESSES, HR_H2PI_ASSIGNMENTS, HR_H2PI_BG_AND_GRE, HR_H2PI_CITY_TAX_RULES, HR_H2PI_COST_ALLOCATIONS, HR_H2PI_COUNTY_TAX_RULES, HR_H2PI_ELEMENT_ENTRIES, HR_H2PI_ELEMENT_ENTRY_VALUES, HR_H2PI_ELEMENT_LINKS, HR_H2PI_ELEMENT_NAMES, HR_H2PI_ELEMENT_TYPES, HR_H2PI_FEDERAL_TAX_RULES, and HR_H2PI_HR_ORGANIZATIONS, plus HR_ALL_ORGANIZATION_UNITS. The source excerpt further shows the staging set spans periods of service, locations, pay bases, organization classifications and information, payrolls, input values, taxes (state and county), salaries, and payment methods.

Usage Notes

Because CLEAR_STAGING_TABLES is keyed on client_id, each staged row carries a client identifier that isolates one data set from another — a common design when multiple clients or Business Groups share a single staging schema. The package is invoked from the H2PI upload concurrent program or from PL/SQL callers that first populate the staging tables. It is referenced by one other package. Administrators should run CLEAR_STAGING_TABLES before a fresh upload to prevent duplicate or stale rows, and use RETRY_UPLOAD only after correcting rejected records.