Results for “hrdpp_create_hierarchy_element”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The APPS.HRDPP_CREATE_HIERARCHY_ELEMENT package is a PL/SQL program unit within the Oracle E-Business Suite (EBS) Human Resources (HR) schema. It forms part of Oracle's Data Pump / hierarchy extraction infrastructure used to move and reconstruct HRMS configuration and setup data between environments, for example during a clone, upgrade, or implementation migration. The "HRDPP" prefix associates the package with the HR Data Pump family of utilities, and the "CREATE_HIERARCHY_ELEMENT" suffix identifies its role in materialising hierarchy elements — organisational, positional, or configuration nodes — as structured Data Pump records.

In practice, the package provides the programmatic logic that converts a logical hierarchy definition into serialisable Data Pump rows. It reads staging content and writes the batch, batch-line, and exception records that downstream Data Pump processing consumes. In ETRM the object is validated and classified as an OTHER API type, indicating that it is an internal utility rather than a public, supported interface.

Key Procedures and Functions

The documented package exposes seven callable units. Their abbreviated names reflect internal helper routines rather than descriptive public APIs:

• DC — a helper routine associated with delete/create processing of hierarchy element data.
• D — a delete-oriented helper, typically used to purge existing hierarchy element records before regeneration.
• N — a new-record helper, responsible for constructing a fresh hierarchy element entry.
• DD — a delete/derive helper, combining removal of stale rows with derivation of dependent values.
• ND — a new/derive helper, generating a new element together with its derived attribute set.
• INSERT_BATCH_LINES — the principal routine; it inserts batch line records into the Data Pump staging tables, representing each hierarchy element as a line item for later export.
• CALL — the orchestrating entry point that invokes the package's internal routines in sequence.

Consistent with the ETRM classification, these procedures are intended for internal invocation; parameter signatures are not published and should not be assumed.

Tables Accessed

The package operates against the following HR Data Pump tables, referenced through APPS synonyms:

• HR_PUMP_BATCH_LINES and HR_PUMP_BATCH_LINES_S — the core staging tables where hierarchy elements are serialised as batch line records; the _S variant holds the corresponding sequence/identifier information.
• HR_PUMP_BATCH_LINE_USER_KEYS and HR_PUMP_BATCH_LINE_USER_KEYS_S — store the user-defined key values that uniquely identify each hierarchy element during extraction and re-import.
• HR_PUMP_BATCH_EXCEPTIONS — captures errors and anomalies encountered while generating batch lines, supporting diagnosis and reconciliation.

Usage Notes

HRDPP_CREATE_HIERARCHY_ELEMENT is typically invoked indirectly. ETRM records that it is referenced by PER_RI_CONFIG_DATAPUMP_ENTITY and PER_RI_CREATE_HIER_ELEMENT, which are the user-facing or orchestration layers of the HR configuration Data Pump flow. It should therefore be treated as an internal component driven by concurrent programs and Data Pump processes rather than a routine called directly from Oracle Forms.

Because only two packages reference it, customisations should avoid direct calls to its abbreviated procedures. Instead, use the documented upstream packages so that hierarchy element generation remains consistent across EBS 12.1.1 and 12.2.2. Note that the object is proprietary and confidential, and its internal signatures may change between releases.