Results for “hrdpp_update_position”

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

Overview

APPS.HRDPP_UPDATE_POSITION is a Data Pump generated PL/SQL package that serves as the batch-processing wrapper for the Oracle Human Resources position maintenance API, HR_POSITION_API.UPDATE_POSITION. Within Oracle EBS 12.1.1 and 12.2.2, this package enables mass updates to position definitions through the HR Data Pump framework rather than through interactive, single-record API calls. The generator metadata embedded in the package header identifies it as having been produced by hr_pump_meta_mapper and references API generation revision 120.4.12010000.1, confirming its role as an interface layer between the Data Pump engine and the underlying business API.

The package business function is to accept batch line records staged in the HR_PUMP_BATCH_LINES family of tables, validate and interpret the incoming attribute values (including date and number conversions), and invoke the update logic against position records. This supports enterprise scenarios such as large-scale reorganizations, amendment processing, and position attribute corrections where performing row-by-row updates through the Position form would be impractical.

Key Procedures and Functions

The ETRM metadata documents seven procedures and functions in this package. The conversion helper functions form the utility layer used to normalize Data Pump staging data before it is passed to the API:

• DC — converts a date value into its character representation, used when a date-formatted attribute must be rendered or compared as text. It is declared with a RESTRICT_REFERENCES pragma of WNDS, making it safe for use in SQL contexts.
• D — the inverse conversion, translating a character string into a date. This function supports staging columns where dates arrive as strings.
• N — converts a character string into a number, supporting numeric attributes such as identifiers passed through staging columns.
• DD — a date-to-character conversion that accepts a format or indicator argument, allowing date output in a caller-specified form.
• ND — a number-to-character conversion that accepts a format or indicator argument, providing formatted numeric output.
• INSERT_BATCH_LINES — the principal data ingestion routine. It accepts a batch identifier, batch line identifier, business group name, user sequence, link value, and the full positional attribute payload, then writes a line into the Data Pump batch structures for subsequent processing. Date and character indicator parameters accompanying the payload signal how each attribute should be interpreted.
• CALL — the execution routine that processes staged batch lines and invokes HR_POSITION_API.UPDATE_POSITION with the mapped attribute values.

Tables Accessed

The package operates directly against the Data Pump batch tables, referenced through APPS synonyms:

• HR_PUMP_BATCH_LINES and HR_PUMP_BATCH_LINES_S — the primary and secondary staging tables holding the position attribute rows queued for processing.
• HR_PUMP_BATCH_LINE_USER_KEYS and HR_PUMP_BATCH_LINE_USER_KEYS_S — store user-defined key values associated with each batch line, allowing callers to correlate staged rows with external identifiers.
• HR_PUMP_BATCH_EXCEPTIONS — captures errors and validation failures encountered during processing, enabling diagnosis of rejected update requests.

These tables are read and written to stage, track, and audit the batch update lifecycle.

Usage Notes

HRDPP_UPDATE_POSITION is typically invoked indirectly. It is called by the HR Data Pump concurrent program architecture, which reads a source file or staging table, calls INSERT_BATCH_LINES to populate the batch structures, and then invokes the package CALL routine to push each line through HR_POSITION_API.UPDATE_POSITION. Because of this design, direct invocation from custom code is uncommon; the recommended pattern is to populate the batch tables through the package's own insert routine and then trigger processing. Direct calls to the underlying HR_POSITION_API remain appropriate for single-record updates performed within forms or bespoke PL/SQL. No other packages in the documented inventory reference this package, indicating it sits at the top of its call chain rather than being a shared utility. Error handling should be anticipated via HR_PUMP_BATCH_EXCEPTIONS, as the API layer enforces HR business rules on position attributes such as effective dates and amendment data.