Search Results get_contract_id

Overview

APPS.HR_PUMP_GET is a public PL/SQL package belonging to the Oracle E-Business Suite Human Resources (HR) module. It is registered in the ETRM repository with an API classification of "OTHER" under the APPS schema. The package is functionally a lookup and resolution layer for the Oracle HR Data Pump engine. As stated in the package header notes, its functions are designed to be used by the Data Pump engine to resolve ID values that must be passed to the API modules during bulk data loads and migrations. The header further acknowledges that most of these routines may be used by any program that needs to perform the same kind of key resolution, with the notable exception of functions where a user key value is itself one of the parameters.

The package therefore serves a critical infrastructure role: it converts human-readable or context-dependent business keys into the internal surrogate primary keys required by Oracle HRMS APIs. In Oracle EBS 12.1.1 and 12.2.2, this resolution is essential whenever data is loaded from external systems, spreadsheets, or staged interface tables, since downstream APIs expect validated internal IDs rather than descriptive values.

Key Procedures and Functions

The package exposes 258 documented procedures and functions. The header explicitly lists the resolution functions declared for Data Pump use, including p_person_id, p_assignment_id, p_contract_id, and related entities. ETMR documents a representative subset of the full interface:

• GET_CONTRACT_ID — resolves the internal identifier for a contract, the routine most directly associated with the user search term "get_contract_id".
• GET_COLLECTIVE_AGREEMENT_ID — resolves the collective agreement identifier, using the associated flexfield structure where required.
• GET_CAGR_ID_FLEX_NUM — returns the flexfield structure number used for collective agreement key flexfield resolution.
• GET_ESTABLISHMENT_ID — resolves the establishment identifier used in EEO and statutory reporting.
• GET_EMP_FED_TAX_RULE_ID, GET_EMP_STATE_TAX_RULE_ID, GET_EMP_COUNTY_TAX_RULE_ID, GET_EMP_CITY_TAX_RULE_ID — resolve the jurisdictional tax rule identifiers applied to an employee payroll record.
• GET_START_LIFE_REASON_ID and GET_END_LIFE_REASON_ID — resolve the life event reason identifiers used in benefits processing.
• GET_BENEFIT_GROUP_ID — resolves the benefit group identifier for eligibility and enrollment.
• GET_PTNL_LER_FOR_PER_ID, GET_CSD_BY_PTNL_LER_FOR_PER_ID, GET_PTNL_LER_FOR_PER_OVN, GET_PER_IN_LER_ID, GET_BCKT_PER_IN_LER_ID — resolve potential and actual life event records associated with a person, supporting benefits life event processing.
• GET_TRGR_TABLE_PK_ID — resolves the primary key of a triggering table row, supporting the benefits event trigger framework.
• GET_WS_MGR_ID, GET_GROUP_PL_ID, GET_MGR_OVRID_PERSON_ID — resolve work schedule manager, group plan, and manager override person identifiers.

Each function encapsulates the join and validation logic required to translate a business key into a validated internal ID, sparing callers from replicating that logic.

Tables Accessed

The documented table references are concentrated in the Oracle Advanced Benefits (BEN) schema, accessed through APPS synonyms. These include BEN_BENFTS_GRP for benefit group resolution; BEN_LER_F and BEN_CBR_PER_IN_LER for life event and person-in-life-event records; BEN_ELIG_PER_F, BEN_ELIG_DPNT, BEN_ELIG_CVRD_DPNT_F, BEN_ELIG_PER_ELCTBL_CHC, and BEN_ELIG_PER_OPT_F for eligibility determination; BEN_ENRT_PERD and BEN_ENRT_RT for enrollment period and rate data; BEN_ACTL_PREM_F, BEN_ACTY_BASE_RT_F, BEN_COMP_LVL_FCTR, and BEN_CVG_AMT_CALC_MTHD_F for premium, activity rate, compensation level, and coverage amount calculation metadata; and BEN_CBR_QUALD_BNF for qualified beneficiary records. Reads against these tables supply the lookup values needed to return a validated internal ID to the caller.

Usage Notes

HR_PUMP_GET is invoked primarily by the Oracle HR Data Pump engine during bulk data loads, migrations, and conversions, where descriptive keys must be resolved before the target API can be called. It is also available to any custom program performing the same resolution, with the caveat that functions accepting user key values as parameters are intended strictly for Data Pump use. The package is referenced by 229 other packages in the EBS data model, confirming its role as shared infrastructure rather than a form-specific utility. In practice, integration developers call the appropriate GET_* function to convert a business key into an internal ID prior to invoking HRMS APIs, and the results are honored across both 12.1.1 and 12.2.2. Because these routines perform lookups and do not commit business transactions, they are safe to call repeatedly within a single load; however, their reliance on current reference data means the caller must ensure setup data is valid before resolution.