Search Results get_to_id

Overview

APPS.HR_H2PI_MAP is a packaged PL/SQL utility belonging to the Oracle E-Business Suite HR family of APIs, classified in ETRM as OTHER rather than as a business API. Its purpose is to maintain identifier cross-reference mappings between the Human Resources (HR) system and the Payroll (H2PI) system. When an HR-side entity must be referenced by a payroll-side process, the two systems frequently use different surrogate keys for the same logical record. HR_H2PI_MAP provides the controlled gateway through which those key pairs are recorded and subsequently resolved, ensuring that downstream payroll logic can translate an internal HR identifier into its payroll counterpart, and vice versa, without hard-coding assumptions about key values.

The package body header ($Header: hrh2pimp.pkb 115.1 2002/03/07) indicates an early-generation component that has remained stable across the 12.1.1 and 12.2.2 releases. It is a foundational, low-level utility rather than an end-user facing module: five other packages reference it, which confirms its role as a shared dependency in the HR-to-Payroll conversion and integration stack.

Key Procedures and Functions

ETRM documents three procedures in this package body:

• CREATE_ID_MAPPING — Inserts a new mapping row into the mapping table, associating a source HR identifier with a destination Payroll identifier for a named table. This is the write entry point of the package. The source text shows defensive validation at the head of the procedure: a table name, a from-identifier, and a to-identifier are each checked for null, and any null raises the locally declared INVALID_PARAM exception (error number -20001) with a FATAL-prefixed message identifying the offending parameter. A separate MAPPING_ID_MISSING exception is declared at package level with error number -20010. The insert is performed with a SELECT-based insert that restricts insertion to mappings not already present, so the procedure is effectively idempotent for a given key triplet.
• GET_TO_ID — Returns the Payroll-side identifier corresponding to a supplied HR-side identifier, reading from the mapping table. It is the forward translation routine used when HR context must be expressed in Payroll terms.
• GET_FROM_ID — The inverse of GET_TO_ID, returning the HR-side identifier for a supplied Payroll-side identifier. Together with GET_TO_ID it forms the bidirectional lookup pair that consumers of the package rely on.

The presence of the -20001 INVALID_PARAM exception is directly relevant to the search term "invalid_param": it is raised when CREATE_ID_MAPPING is called with a null TABLE_NAME, FROM_ID, or TO_ID, and the accompanying message text names the specific parameter at fault.

Tables Accessed

The package operates on a single documented table, HR_H2PI_ID_MAPPING, accessed through its APPS synonym. This table is the persistent store for the cross-reference data and holds, at minimum, the business group, the from-identifier, the to-identifier, and the table name identifying the mapped entity type. CREATE_ID_MAPPING writes to it; GET_TO_ID and GET_FROM_ID read from it. Because all three documented routines converge on this table, it is the sole stateful dependency of the package and the object most likely to be involved in any diagnostic investigation of mapping failures.

Usage Notes

HR_H2PI_MAP is not intended for direct end-user invocation. It is typically called by the other EBS packages that reference it, by HR-to-Payroll data conversion or migration routines, and by custom code that must reconcile identifiers across the two systems. The standard pattern is to call CREATE_ID_MAPPING once during setup or conversion to establish the mapping, then to call GET_TO_ID or GET_FROM_ID thereafter as a lookup. Callers should trap the -20001 INVALID_PARAM condition and the -20010 MAPPING_ID_MISSING condition explicitly, since an unhandled exception propagates with the package's diagnostic message. When diagnosing an "invalid_param" error it is advisable to check that all three CREATE_ID_MAPPING arguments were populated, because null validation precedes any insert and no mapping row is written when validation fails. The hr_utility.set_location calls embedded in the source provide step-level trace output useful in such investigations.