Search Results pre_create_enrollment

Overview

APPS.BEN_PRE_DATAPUMP_PROCESS is a Benefits module wrapper package that supports the Oracle EBS datapump staging process for enrollment data. Its stated purpose, drawn from the package header, is to serve as a wrapper procedure for Benefits enrollments pre datapump processing. The package was created on 10 Jan 2006 and revised on 23 Mar 2006 to add beneficiary handling. It is compiled with AUTHID CURRENT_USER, meaning its SQL executes under the privileges of the calling schema rather than the package owner.

The package occupies the staging layer that precedes the actual datapump load into Benefits transactional tables. It prepares dependent, beneficiary, and enrollment records so that subsequent datapump movement of data proceeds against a consistent, pre-validated set of staging rows. In Oracle EBS 12.1.1 and 12.2.2 this pre-processing model is the standard mechanism for separating validation and enrichment work from the bulk transfer performed by the datapump utility.

Key Procedures and Functions

The package exposes three documented procedures, all classified under the ETRM API classification OTHER. Each accepts a batch identifier and a validation flag, allowing callers to target a specific datapump batch and to run in validate-only mode before committing changes.

• PRE_CREATE_ENROLLMENT — Prepares enrollment records for the datapump process. This is the primary entry point for standard enrollment staging prior to transfer.
• PRE_PROCESS_DEPENDENT — Handles pre-processing of dependent records associated with the batch. This procedure is the object most commonly located by searches for dependency-related processing in the Benefits datapump flow.
• PRE_PROCESS_BENEFICIARY — Handles pre-processing of beneficiary records, added in the 115.1 revision of the package header. It parallels the dependent procedure for beneficiary designations.

All three procedures are declared only; no function members are documented. Parameter lists are intentionally omitted here, but the metadata confirms each carries a batch identifier defaulting to null and a validate flag defaulting to 'N'.

Tables Accessed

Through APPS synonyms the package references two staging tables:

• HR_PUMP_BATCH_HEADERS — Stores header-level information for each datapump batch, including batch identity and status. The package reads and updates header status as pre-processing progresses.
• HR_PUMP_BATCH_LINES_S — Stores the individual staging lines belonging to a batch. Dependent, beneficiary, and enrollment rows are validated and prepared at this line level.

These tables form the standard HR datapump staging infrastructure, which is why the package is positioned as a pre-datapump wrapper rather than as a direct transactional API.

Usage Notes

BEN_PRE_DATAPUMP_PROCESS is typically invoked by concurrent programs and by other Benefits packages rather than directly from a form. ETRM records that the package is referenced by one other package, indicating that it is called programmatically within the Benefits datapump orchestration rather than exposed as an end-user action. The validate flag supports a dry-run invocation, which is appropriate for diagnostics and for confirming batch contents before committing the datapump run.

Because the package is compiled with AUTHID CURRENT_USER, callers must hold appropriate privileges on the underlying HR_PUMP tables. Custom code should follow the same pattern: supply a valid batch identifier, execute with validation enabled first, and only then run the processing mode to finalize staging. This ordering preserves data integrity and keeps the pre-datapump stage consistent with the downstream load.