Search Results pre_datapump_process

Overview

PER_RI_PRE_DATAPUMP is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified under the ETRM "OTHER" API category. Its business purpose is to act as a wrapper for Oracle Data Pump functionality invoked from the Oracle HRMS workbench, specifically within the context of the Enrollment Process. The package header, delivered under the source file perripmp.pkh (version 120.0, dated 11 April 2006), carries the internal name "Enrollment Process" and describes itself explicitly as "a wrapper procedure for Datapump functionality from workbench."

In the EBS Release 12.1.1 and 12.2.2 architecture, this package forms part of the broader "PER_RI" (Human Resources Reporting and Integration) family of utilities that support the rapid, batch-oriented movement of HR-related data. By front-ending Data Pump operations, PER_RI_PRE_DATAPUMP allows the workbench to stage and validate data prior to a full export or import cycle. The package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking user rather than the defining APPS user, an important consideration for security and schema resolution.

Key Procedures and Functions

The package exposes a single documented procedure, PRE_DATAPUMP_PROCESS, which matches the user's search term "pre_datapump_process." Its role is to perform the pre-processing stage required before a Data Pump operation can proceed. This includes coordination of the batch identified by the caller and, where requested, validation-only execution so that no persistent changes occur.

• PRE_DATAPUMP_PROCESS — the sole documented entry point. It accepts a standard concurrent-program style calling interface (an out error buffer and out return code) together with a batch identifier and a validation flag. It prepares and validates the batch data so that a subsequent Data Pump export or import can be executed reliably.

No other procedures or functions are documented in the ETRM metadata for this package. The header also shows no packaged constants, types, or cursors declared outside the single procedure, indicating a narrowly scoped wrapper utility.

Tables Accessed

The package references three tables via APPS synonyms:

• FND_CONCURRENT_REQUESTS — the standard Oracle Application Object Library table for concurrent request state. It is read to determine the status, phase, and parameters of the parent concurrent request that has invoked the pre-Data Pump processing, and may be used to derive the batch context.
• HR_API_MODULES — the HRMS API registry. It identifies the HR API module under which the Data Pump operation is being performed, ensuring the batch is associated with the correct business API context.
• HR_PUMP_BATCH_LINES — the HR Data Pump batch line table. This is the primary transactional table the procedure reads and prepares, holding the individual records belonging to the identified batch that will be subsequently processed by the Data Pump engine.

Usage Notes

PER_RI_PRE_DATAPUMP is not intended for direct invocation by end users. It is invoked programmatically by the HRMS workbench whenever a Data Pump-driven operation is initiated, and is typically executed either from a form-based workbench action or from a concurrent program that requires batch staging prior to export/import.

Because the procedure follows the standard concurrent-program signature (errbuf, retcode), custom code may call it through FND_REQUEST.SUBMIT_REQUEST using the appropriate concurrent program registration. Developers should note that the package is marked "noship" in its header comment, which historically indicates it is not shipped as a public, supported API; customer extensions should treat it as an internal utility and validate behavior on the specific EBS release (12.1.1 or 12.2.2) in use before relying on it.