Search Results hrdpv_create_enrollment

Overview

APPS.BEN_PRE_DATAPUMP_PROCESS is a PL/SQL package body in the Oracle E-Business Suite Benefits (BEN) schema, classified under the ETRM metadata as an "OTHER" API type. Its name indicates a pre-processing role that runs ahead of the standard datapump-based benefits data load. In the Oracle EBS 12.1.1 and 12.2.2 releases, the Benefits module relies on the HR datapump staging framework (the HR_PUMP_BATCH_HEADERS and HR_PUMP_BATCH_LINES_S structures) to stage inbound benefit enrollment, dependent, and beneficiary records before they are validated and committed to the core Benefits tables. This package serves as the controlled pre-processing entry point that reads those staged lines and converts them into pre-created enrollment, dependent, and beneficiary entities using the corresponding HRDPV_* program units. It bridges the raw staging rows held by the HR datapump tables and the formal Benefits enrollment/eligibility processing logic.

Key Procedures and Functions

The ETRM metadata documents three procedures or functions within this package body:

• PRE_CREATE_ENROLLMENT — Handles the pre-creation of benefit enrollment records derived from datapump staging data. It orchestrates the pre-enrollment step so that enrollment rows exist prior to full Benefits processing.
• PRE_PROCESS_DEPENDENT — Pre-processes dependent information staged through the datapump framework, preparing dependent records for subsequent Benefits validation and commitment.
• PRE_PROCESS_BENEFICIARY — Pre-processes beneficiary information staged through the datapump framework, preparing beneficiary records for downstream Benefits processing.

The package body calls into HRDPV_CREATE_ENROLLMENT, HRDPV_PROCESS_DEPENDENT, and HRDPV_PROCESS_BENEFICIARY to perform the substantive pre-processing work, and depends on HR_UTILITY and the FND_FILE utility package (used for concurrent program output/log handling). Parameter lists are not exposed in the documented metadata and should be confirmed against the live package specification.

Tables Accessed

The documented tables accessed via APPS synonyms are:

• HR_PUMP_BATCH_HEADERS — the datapump batch header table that identifies each inbound staging batch and its processing context. It provides the batch-level scope under which pre-processing occurs.
• HR_PUMP_BATCH_LINES_S — the datapump batch line staging table holding the individual records (enrollment, dependent, beneficiary data) to be processed. This is the primary source of the records that the three pre-processing procedures act upon.

These tables are central to the HR datapump architecture: the header establishes the batch, and the lines hold the transactional payload that BEN_PRE_DATAPUMP_PROCESS reads to drive its pre-create and pre-process logic.

Usage Notes

BEN_PRE_DATAPUMP_PROCESS is typically invoked as part of the Benefits datapump load sequence, immediately before the main datapump processing that commits records to the Benefits tables. Because FND_FILE is a declared dependency, the package is designed to run within a concurrent program context, writing log and output to the standard concurrent manager files. The ETRM metadata records that this package is referenced by one other database object and is not itself referenced elsewhere as a public entry point, indicating it is a helper invoked internally by the Benefits datapump orchestration rather than directly by forms or end users. Customizations should not modify this package body; instead, extensions should wrap or call it in the documented sequence. Confirm the exact concurrent program and parameter binding in the target 12.1.1 or 12.2.2 instance, since behavior can vary by patch level.