Search Results submit_sync_names

Overview

HR_NMF_SYNC is an Oracle E-Business Suite package owned by the APPS schema that supports the Name Management Framework (NMF) infrastructure used to generate, format, and synchronize person names according to legislation-specific rules. The package header comment (hrnmfsyn.pkh 120.4, dated 2006) confirms it as a long-standing component of the Oracle HRMS naming architecture, and it is shipped across both the 12.1.1 and 12.2.2 releases. Its principal business role is to reconcile the name format definitions held in the HR_NAME_FORMATS table with the seeded naming packages and procedures that actually perform name construction for a given legislation. In addition, the package participates in the concurrent-manager request lifecycle by supplying a range cursor, performing request initialization and validation, and archiving processed data. It is classified under ETRM as "OTHER," indicating that it is an internal infrastructure package rather than a documented public API.

Key Procedures and Functions

The ETRM documentation for 12.2.2 enumerates six procedures and functions:

• RANGE_CURSOR — Supplies the driving SQL cursor for the concurrent program. It receives the request identifier and returns the SQL statement to be executed, following the standard Oracle concurrent processing "range cursor" pattern used to partition work across parallel workers.
• ACTION_CREATION — Creates the action records required by the synchronization process, populating the action tables that drive subsequent processing steps.
• INITIALIZATION — Performs setup for the synchronization run, preparing in-memory state and environment for the procedures that follow.
• ARCHIVE_DATA — Moves or copies processed synchronization data into an archival structure, preserving history and supporting purging of transient working data.
• SUBMIT_SYNC_NAMES — The procedure most commonly sought by users, this is the entry point that submits the name synchronization work, initiating the process by which name formats and seeded naming logic are aligned with the current legislation configuration.
• VALIDATERUN — Validates that the synchronization run is eligible to proceed, confirming prerequisites such as legislation and format setup before the main processing executes.

The package header also declares several PL/SQL collection types (number, varchar2(30), varchar2(80), varchar2(250) index-by tables) and three record types used as in-memory caches: a legislation mask cache, a business group cache, and a seeded-package cache. These caches, together with global variables such as g_prm_legislation_code and g_prm_format_name, support efficient bulk processing of name formats across business groups.

Tables Accessed

Through APPS synonyms, HR_NMF_SYNC references the following tables:

• HR_NAME_FORMATS — Stores the name format definitions, format masks, user format choices, and seeded package/procedure references that are the subject of the synchronization.
• PAY_ASSIGNMENT_ACTIONS and PAY_ASSIGNMENT_ACTIONS_S — Hold assignment-level payroll action records, including the shadow table used for date-tracked history.
• PAY_PAYROLL_ACTIONS — Stores payroll action definitions that provide context for actions created during synchronization.
• PER_ALL_PEOPLE_F — The date-tracked person record, used to identify affected employees.
• ALL_TRIGGERS, USER_TRIGGERS, and DUAL — Data dictionary views used to detect trigger state and to evaluate standard singleton queries.
• PLITBLM — The PL/SQL table used by the concurrent manager to pass range parameters between the range cursor and the worker sessions.

Usage Notes

HR_NMF_SYNC is invoked internally by the Oracle HRMS Name Management Framework and is not intended for direct customer calls. Its presence in a concurrent program definition explains the RANGE_CURSOR, INITIALIZATION, VALIDATERUN, and ARCHIVE_DATA procedures, which conform to the standard Oracle concurrent processing protocol. Custom code should not call SUBMIT_SYNC_NAMES directly; instead, the corresponding concurrent program should be submitted through the standard request submission flow so that request identifiers, validation, and archival behavior are handled correctly. Because the ETRM metadata records zero dependent packages, modifications to this package carry limited downstream package-level risk, but any change may affect name synchronization behavior across all legislations and business groups configured in the instance.