Results for “action_archive_data”

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

Overview

PAY_RUN_BALANCE_BUILD is an Oracle Payroll server-side PL/SQL package owned by the APPS schema. It participates in the payroll action framework used by Oracle Payroll in Oracle E-Business Suite 12.1.1 and 12.2.2 to build, validate, and maintain payroll balance definitions and their derived values. The package is declared with AUTHID CURRENT_USER, meaning its SQL statements execute under the privileges of the calling schema rather than the definer, which is consistent with other payroll action handler packages invoked by the concurrent manager.

The package implements the standard range cursor, action creation, archive initialization, archive data, and deinitialization entry points expected of a payroll action handler. These entry points let the payroll action framework partition the population of assignments into chunks, create PAY_ASSIGNMENT_ACTIONS rows, and manage archival and cleanup activity. Its broader business purpose is to support the balance build processing that maintains cumulative payroll balances used by payroll reporting, costing, and statutory returns.

Key Procedures and Functions

• FIND_CONTEXT — A context resolution helper referenced in the package specification, used to resolve a context identifier from a context name. In the documented source it is commented out, indicating it is retained for backwards compatibility rather than active use.
• ACTION_RANGE_CURSOR — Returns the SQL text used by the payroll action framework to select the range of assignment or person identifiers that the action must process.
• ACTION_ACTION_CREATION — Creates the PAY_ASSIGNMENT_ACTIONS rows for a payroll action, given the action identifier, start and end person identifiers, and a chunk number.
• ACTION_ARCHIVE_DATA — Performs archival of data associated with an assignment action, using the effective date supplied by the caller.
• ACTION_ARCHINIT — Initializes archival processing for a given payroll action. This is the procedure associated with the search term action_archinit; it prepares the action so that subsequent archive steps can complete consistently.
• DEINITIALISE — Performs cleanup for a payroll action once processing is complete, releasing transient state and temporary records.

Tables Accessed

The package reads and writes payroll action and balance metadata through APPS synonyms. PAY_PAYROLL_ACTIONS and PAY_ASSIGNMENT_ACTIONS (with its _S shadow table) provide the action and assignment-action context that drives processing. FND_CONCURRENT_PROGRAMS and FND_CONCURRENT_REQUESTS supply concurrent program and request information used when actions are submitted or tracked. Balance-related metadata is held in PAY_BALANCE_TYPES, PAY_BALANCE_DIMENSIONS, PAY_BALANCE_ATTRIBUTES (and _S), PAY_BAL_ATTRIBUTE_DEFINITIONS (and _S), PAY_DEFINED_BALANCES, PAY_BALANCE_VALIDATION (and _S), and PAY_LEGISLATION_RULES. These tables define which balances exist, how they are dimensioned, and which validation and legislation rules apply, allowing the package to construct or verify balance definitions during action processing.

Usage Notes

PAY_RUN_BALANCE_BUILD is not intended for direct invocation by end users or custom forms. It is called by the Oracle Payroll action framework, typically through a concurrent program that supplies a payroll action identifier. The framework first calls ACTION_RANGE_CURSOR to determine the population, then ACTION_ACTION_CREATION to create assignment actions, and later ACTION_ARCHINIT and ACTION_ARCHIVE_DATA for archival handling, with DEINITIALISE performing cleanup at the end. The package is not referenced by any other documented package, reinforcing its role as a handler invoked externally rather than as a reusable API. Custom code should not call these procedures directly; instead, balance build behavior should be triggered through supported payroll action configurations. Because the package is AUTHID CURRENT_USER, any diagnostic or wrapper code must be executed with sufficient privileges on the underlying PAY and FND tables.