Search Results process_assignments

Overview

APPS.PAY_HK_IR56_MAGTAPE is a Hong Kong statutory reporting package body within the Oracle E-Business Suite Payroll module. Its business purpose is to support the generation of IR56 magtape (magnetic media) output — the machine-readable annual employer's return of remuneration and pensions that Hong Kong employers are required to submit to the Inland Revenue Department (IRD). The package encapsulates the range-selection and assignment-action logic that a payroll action requires when producing this statutory file, isolating the Hong Kong localisation behaviour from the core payroll engine.

The package body carries a change list indicating an initial version dated 17 September 2001, followed by a series of corrections addressing cursor behaviour, parameter modes, secured views, and record locking. These entries confirm that the package has been maintained across multiple release cycles up to release 12.1.1 and 12.2.2, and that its logic is tightly coupled to payroll action processing rather than to interactive data entry.

Key Procedures and Functions

The ETRM metadata documents two procedures for this package.

• RANGE_CODE — Returns a SQL statement fragment used to select the population of people to be processed for a given payroll action. The change history records that the nocopy option was added for its OUT parameter in December 2002 to improve performance by avoiding unnecessary copying of the returned string. This procedure forms the "range" phase of the payroll action, defining which person records the magtape process will subsequently act upon.
• ASSIGNMENT_ACTION_CODE — Handles the assignment-action phase of the payroll action, determining the assignment-level records associated with the selected population. It is invoked in the action phase of the payroll process to drive the processing and locking of assignment actions relevant to magtape generation.

The change list references an internal process_assignments cursor within the package, which is the object most relevant to the searched term "process_assignments". Documented corrections to this cursor include joining paa.action_status = 'C' (March 2003) so that errored archive records are not fetched onto magtape, and an August 2008 amendment ensuring that the cursor locks assignments for which magtape has been generated, rather than locking assignments associated with archive records. A June 2002 change restricted the eit cursor so that it opens only when the archive message is null.

Tables Accessed

• PAY_PAYROLL_ACTIONS — the driving payroll action record; supplies the payroll_action_id and business group used by RANGE_CODE.
• PER_ALL_PEOPLE_F / secured views PER_PEOPLE_F and PER_ASSIGNMENTS_F — the date-tracked person and assignment records. The May 2003 change replaced direct references to the base tables with the secured views to enforce security profiles.
• PAY_ASSIGNMENT_ACTIONS and PAY_ASSIGNMENT_ACTIONS_S — assignment-level action records examined and locked by the process_assignments logic.
• PAY_ACTION_INTERLOCKS — payroll action interlock information used to coordinate processing phases.
• FF_ARCHIVE_ITEMS and FF_USER_ENTITIES — archive-related entities consulted by the archive message and error-status checks.
• PER_ASSIGNMENT_EXTRA_INFO and PER_ASSIGNMENT_INFO_TYPES — assignment-level descriptive flexfield and extra information used during population of magtape data.
• DUAL — used for single-row selection constructs.

Usage Notes

PAY_HK_IR56_MAGTAPE is not a general-purpose API. It is classified as OTHER and is referenced by zero other packages, which indicates that it is invoked indirectly through the payroll action framework rather than being called by other PL/SQL units. It is executed as part of a Hong Kong IR56 magtape concurrent program or payroll action, with RANGE_CODE driving the range phase and ASSIGNMENT_ACTION_CODE driving the assignment-action phase. The HR_UTILITY.SET_LOCATION calls embedded in the code support runtime tracing during payroll action execution. Because it depends on secured HR views and on assignment action locking behaviour, customisations should not call the package directly; instead they should invoke the associated concurrent program or payroll action so that the standard range and action sequencing, security, and locking semantics are preserved. Inspecting the process_assignments cursor within the package body is the appropriate way to understand assignment selection and locking for magtape generation.