Search Results hr_nonrun_asact




Overview
Explore in AI Chat

Overview

APPS.HR_NONRUN_ASACT is a valid PL/SQL package body residing in the APPS schema that supports Oracle EBS Payroll processing in release 12.1.1 and 12.2.2. Its name denotes the generation of non-run assignment actions — that is, assignment action records that are created outside the normal payroll run path, such as reversals, retropay-related adjustments, third-party payment corrections, and interlock-driven re-processing. The package operates as an internal orchestration layer between the payroll action framework (PAY_ACTION_*) and the assignment-level action records maintained in PAY_ASSIGNMENT_ACTIONS. It is not intended for direct customer invocation; it is referenced by 259 other database objects, confirming its role as a low-level engine component invoked by payroll concurrent processes and other payroll packages.

Key Procedures and Functions

  • NAME — A standard package-level identifier function returning the owning object name, used for logging and diagnostic context by the payroll processing framework.
  • GET_NEXT_PROC_CHUNK — Selects the next available processing chunk for the current payroll action, coordinating with the chunk-status and batch infrastructure to distribute work units across parallel payroll processes.
  • ASACT — The principal driver that creates and manages assignment action records for non-run processing. It evaluates the action interlock context and writes the corresponding entries into the assignment action tables.
  • INSACT — Performs insertion of assignment action rows, applying the classification and parameter attributes supplied by the calling action definition.
  • INSINT — Creates or updates action interlock records, ensuring that dependent or mutually exclusive payroll actions are serialized and cannot execute concurrently against the same population.
  • REINTERLOCK — Re-establishes interlock entries when an action is retried, reversed, or re-queued, restoring the lock state required for correct sequencing.
  • INS_ADDITIONAL_ASG_ACTION — Inserts supplementary assignment actions that flow from a primary action, such as follow-on adjustments, contributing payment entries, or reconciliation-driven actions.

Tables Accessed

The package reads and writes the full spectrum of payroll action and assignment tables. Action definitions and parameters are sourced from PAY_ACTION_CLASSIFICATIONS, PAY_ACTION_PARAMETERS, and PAY_PAYROLL_ACTIONS. Assignment-level state is maintained in PAY_ASSIGNMENT_ACTIONS and PAY_ASSIGNMENT_ACTIONS_S, with concurrency governed through PAY_ACTION_INTERLOCKS. Batch and chunk orchestration uses PAY_BATCH_HEADERS, PAY_BATCH_LINES, and PAY_CHUNK_STATUS.

Population selection and payroll scope are derived from PAY_POPULATION_RANGES, PAY_ALL_PAYROLLS_F, HR_ASSIGNMENT_SETS, and HR_ASSIGNMENT_SET_AMENDMENTS. Payment and reconciliation data is touched via PAY_PRE_PAYMENTS, PAY_CE_RECONCILED_PAYMENTS, PAY_CONTRIBUTING_PAYMENTS, and PAY_ORG_PAYMENT_METHODS_F. Employee context comes from PER_ALL_ASSIGNMENTS_F, PER_ALL_PEOPLE_F, PER_PERIODS_OF_SERVICE, PER_TIME_PERIODS, and HR_ORGANIZATION_UNITS. Utility services including PAY_CORE_UTILS, PAY_PROC_ENVIRONMENT_PKG, PAY_PROC_LOGGING, HR_UTILITY, DBMS_LOCK, and DBMS_SQL provide runtime support.

Usage Notes

HR_NONRUN_ASACT is almost always invoked indirectly. In typical operation it is called from payroll concurrent programs — the payroll run, reversal, retropay, and prepayment processes — when an action must create assignment actions without executing a full payroll run. It is also reached from Oracle Payroll forms when a user initiates a reversal, recalculates an assignment, or corrects a payment, since those flows must generate the correct non-run action records before further processing.

Because the package writes directly to assignment action and interlock tables and depends on DBMS_LOCK for concurrency control, custom code should never call its procedures directly. Any custom extension should be implemented through the supported payroll action APIs instead. Diagnosis of failures involving this package typically centres on interlock contention, invalid population ranges, or orphaned batch chunk records, which are visible through the payroll processing logs written by PAY_PROC_LOGGING.