Results for “hrdpp_create_org_structure_ver”

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

Overview

HRDPP_CREATE_ORG_STRUCTURE_VER is an Oracle E-Business Suite PL/SQL package owned by the APPS schema. It is a Data Pump wrapper package generated by the HR Pump metadata mapper, and its purpose is to expose the public API PER_ORG_STRUCTURE_VERSION_API.CREATE_ORG_STRUCTURE_VERSION to the Oracle HRMS Data Pump (HRDPP) bulk-processing framework. The package header carries a generation timestamp of 2007/01/03 and identifies $Revision: 120.4 $ as its generator version.

In business terms, the package creates new versions of an organization structure — the hierarchy that groups internal organizations, positions, and reporting relationships — so that dated, versioned snapshots of the structure can be loaded or moved in bulk. The Data Pump layer decouples the source data (staged in batch and batch-line tables) from the underlying API call, validating and transforming record-level data before invoking the API. This is the mechanism used by HRMS Data Pump and related concurrent processes to create organization structure versions in Oracle EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

The documented package exposes seven program units:

• DC — a conversion function that transforms a DATE value into a VARCHAR2 representation, used for date columns carried through the pump staging records. Declared with PRAGMA RESTRICT_REFERENCES(WNDS).
• D — the inverse conversion, translating a VARCHAR2 value into a DATE. Also WNDS-restricted.
• N — a conversion function returning a NUMBER from a VARCHAR2 value, WNDS-restricted.
• DD — a formatted date conversion returning VARCHAR2, accepting a date and a format indicator; generated for display of date attributes. WNDS-restricted.
• ND — a formatted number conversion returning VARCHAR2, accepting a number and a format indicator. WNDS-restricted.
• INSERT_BATCH_LINES — the staging procedure. It accepts a batch identifier, an optional data pump batch line identifier and business group name, user sequence and link values, and the API-level parameters required to create an organization structure version (effective date, date from, version number, optional copy-structure version, date to, program update date, the TOPNODE_POS_CTRL_ENABLED flag, and the organization structure version and organization structure user keys). Its role is to insert the incoming record into the HR_PUMP batch line tables for subsequent processing by the CALL procedure.
• CALL — the execution procedure. It accepts a business group identifier and a batch line identifier and passes the staged row to PER_ORG_STRUCTURE_VERSION_API.CREATE_ORG_STRUCTURE_VERSION, recording the outcome in the batch exception tables.

No parameter lists beyond those documented in the package header are asserted here.

Tables Accessed

Per the ETRM metadata, the package references five tables through APPS synonyms, all belonging to the HR Pump staging and error-handling schema:

• HR_PUMP_BATCH_LINES and HR_PUMP_BATCH_LINES_S — the primary staging tables where INSERT_BATCH_LINES writes each organization structure version record prior to processing.
• HR_PUMP_BATCH_LINE_USER_KEYS and HR_PUMP_BATCH_LINE_USER_KEYS_S — store the user keys (P_ORG_STR_VERSION_USER_KEY and P_ORG_STRUCTURE_USER_KEY) that resolve the staged row to the correct organization structure and version.
• HR_PUMP_BATCH_EXCEPTIONS — captures rows and messages that fail validation or the API call, enabling correction and reprocessing.

Usage Notes

This package is an internal component of the HRMS Data Pump infrastructure and is not intended for ad hoc invocation from forms. It is typically driven by a concurrent program or a higher-level Data Pump workflow that populates the HR_PUMP_BATCH_LINES tables and then calls the generated wrapper. Custom code should not call INSERT_BATCH_LINES or CALL directly; instead, use PER_ORG_STRUCTURE_VERSION_API for direct API integration, or the supported Data Pump business process. The metadata shows that one other package references this package, confirming its role as a dependent, generated unit within a larger pump call graph. Because the package was generated by hr_pump_meta_mapper, regeneration may overwrite site-level modifications; any extensions should be applied outside the generated source.