Results for “hr_navigation_paths_s”

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

Overview

The APPS.HR_NAVIGATION_PATHS_PKG package body is a database-tier API within the Oracle E-Business Suite Human Resources (HR) module. It provides the core data manipulation and language-handling logic for HR navigation paths, which are the configurable menu and navigation structures used to organize and present HR self-service and administrative functions to end users. Navigation paths define the ordered sequences and hierarchical groupings through which users traverse HR responsibilities, and this package manages the persistence, locking, translation, and bulk loading of that configuration data.

The package operates across the three base tables that form the navigation paths data model — the primary table HR_NAVIGATION_PATHS, its translated (language) table HR_NAVIGATION_PATHS_TL, and its sequence HR_NAVIGATION_PATHS_S — while also validating related navigation nodes and usages. It is classified as an OTHER API (not a public user-facing HR API), indicating it is intended for internal use by the navigation configuration infrastructure and seed-data loading processes rather than direct invocation by application developers. The package body is VALID and resides in the APPS schema in both EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

The package exposes eight documented procedures, grouped by purpose:

• OWNER_TO_WHO — Populates the standard "WHO" audit columns (created_by, creation_date, last_updated_by, last_update_date) according to the current session context, ensuring consistent audit tracking on rows manipulated by the package.
• INSERT_ROW — Inserts a new navigation path definition, generating the primary key from the sequence and inserting the base-language row along with required audit defaults.
• LOCK_ROW — Acquires a row-level lock on an existing navigation path, supporting the concurrency control discipline required before an update or delete.
• UPDATE_ROW — Modifies an existing navigation path record, applying the supplied attribute changes and refreshing audit columns.
• DELETE_ROW — Removes a navigation path definition and its associated translated rows.
• ADD_LANGUAGE — Inserts a translation row for a navigation path into HR_NAVIGATION_PATHS_TL for a specified language, supporting multilingual deployment.
• LOAD_ROW — Bulk inserts or updates navigation path data, typically used by seed-data and patch (FNDLOAD-style) driven population of navigation configuration.
• TRANSLATE_ROW — Loads translated attribute values into the translation table, used during language-installation and translation-upload processes.

Tables Accessed

• HR_NAVIGATION_PATHS — the primary configuration table; the target of INSERT, UPDATE, DELETE, and LOCK operations.
• HR_NAVIGATION_PATHS_S — the sequence supplying new primary key values.
• HR_NAVIGATION_PATHS_TL — stores language-specific (translated) text for navigation paths, populated by ADD_LANGUAGE and TRANSLATE_ROW.
• FND_LANGUAGES — validates language codes during translation operations.
• HR_NAVIGATION_NODES and HR_NAVIGATION_NODE_USAGES — referenced to validate that navigation path entries reference valid nodes and node usages.
• HR_WORKFLOWS — accessed through HR_WORKFLOWS_PKG for workflow-related validation or lookup.
• FND_MESSAGE / APP_EXCEPTION — used to raise standardized error messages on validation failure.

Usage Notes

Because HR_NAVIGATION_PATHS_PKG is classified as an internal (OTHER) API and is not referenced by any other database object, it is not a general-purpose integration point. It is most commonly invoked indirectly by HR self-service configuration forms, by the seed-data loading and translation-upload machinery (for example, FNDLOAD-driven population of navigation definitions), and by setup migration between environments. The user search for hr_navigation_paths_s reflects the underlying sequence object; the sequence is consumed internally by INSERT_ROW and is not typically referenced directly in custom code. Customizations should call the documented procedures rather than manipulating the base tables directly, in order to preserve audit, locking, and translation integrity.