Search Results update_proc_pay_wkr




Overview

APPS.PAY_SLA_UPDATE_PKG is a payroll Subledger Accounting (SLA) migration utility delivered within the Oracle E-Business Suite Payroll application. Its principal business purpose is to upgrade historical payroll data into the Subledger Accounting data model, a process normally performed during the transition from the pre-SLA accounting engine to the SLA architecture introduced in Oracle EBS 12. The package is classified as a standalone utility (API classification OTHER) rather than a public accounting or business API, meaning it is intended for controlled, typically one-time or administrative use rather than routine transactional integration.

The package exposes both a manager process and a worker process, employing a parallel-processing pattern. The manager orchestrates execution by subdividing the range of payroll actions into work units, while multiple worker processes consume those units concurrently. This design accommodates the potentially large volume of historical payroll actions that must be converted when SLA is enabled for payroll.

Key Procedures and Functions

  • UPDATE_PROC_PAY_MGR — The manager (driver) process, intended to be invoked as a concurrent program. It accepts the ledger identifier, a start and end accounting period, a debug flag, batch size, number of workers, and additional generic arguments, then coordinates the overall upgrade of historical payroll data to SLA.
  • UPDATE_PROC_PAY_WKR — The worker process called by the manager. It receives parameters including batch size, a worker identifier, the total number of workers, and the same generic arguments, and performs the actual conversion of a subset of payroll subledger data into the SLA model.
  • UPDATE_PAYROLL_SUBLEDGER — The core procedure that carries out the substantive update of payroll subledger information into the SLA accounting structures.
  • GET_SEQUENCE_VALUE — A utility function used to obtain unique sequence values required during the migration, typically for generating identifiers or controlling processing ranges.
  • GET_FULL_NAME — A helper function that returns the formatted full name of a person or entity, used internally to populate descriptive accounting information or error diagnostics. Because it is documented as a helper rather than a public interface, applications should not rely on it as a supported standalone API.

Tables Accessed

The package reads and writes across payroll, general ledger, and SLA tables through APPS synonyms. Payroll-side tables include PAY_PAYROLL_ACTIONS, PAY_ASSIGNMENT_ACTIONS, PAY_ALL_PAYROLLS_F, PAY_ACTION_CLASSIFICATIONS, PAY_ACTION_INTERLOCKS, and PER_ALL_ASSIGNMENTS_F, which supply the source payroll actions and assignment details being migrated. PAY_PATCH_STATUS and PAY_PATCH_STATUS_S track the progress and status of the migration process itself across phases or workers. PAY_XLA_EVENTS and the XLA_AE_HEADERS / XLA_AE_HEADERS_S tables represent the SLA-side targets, where accounting events and journal header information are created. GL_JE_HEADERS, GL_JE_LINES, and GL_IMPORT_REFERENCES hold the resulting journal entries and linkage references in the general ledger, while GL_PERIOD_STATUSES is consulted to resolve and validate the accounting periods supplied as parameters.

Usage Notes

PAY_SLA_UPDATE_PKG is typically invoked through Oracle Payroll concurrent programs rather than from Oracle Forms. The manager procedure is designed as the concurrent program entry point, with the worker procedure being spawned as parallel child processes. It is used during the SLA enablement or migration exercise, generally against a defined ledger and accounting period range. Because the package manipulates core payroll and subledger accounting data, it should be executed only during controlled implementation activities, with appropriate backups and in coordination with the prescribed Oracle migration steps. Custom code may reference documented procedures, but the generic X_Argument parameters and helper procedures such as GET_FULL_NAME should be treated as internal implementation details. The package is referenced by no other packages per the documented metadata, confirming its role as a top-level migration driver.