Mass Update Architecture

The Mass Update feature enables you to make changes to the data of large groups of people. For example, you can use the Mass Update feature to perform company-wide compensation increases, department transfers, job code changes, labor agreement changes, and reorganizations.

The Mass Update feature consists of the following modules:

  • Mass Update Manager: This is the front-end module that provides the user interfaces for the Mass Update feature. It consists of:

    • The Define Mass Update component (MU_SETUP ) for setting up mass update definitions.

    • The Create Mass Updates component (RUNCTL_MU_CREATE) and related Application Engine (AE) process for generating mass update transactions.

    • The Report Mass Updates component (RUNCTL_MU_PRINT) and related Structured Query Report (SQR) report for reviewing and printing lists of mass update transactions.

    • The Manage Mass Updates component (MU_MANAGE) for reviewing or previewing mass update transactions, managing statuses, and processing mass update transactions individually online.

    • The Execute Mass Update component (RUNCTL_MU_EXECUTE) and related AE process for running mass updates in batch.

    • The Delete Mass Updates component (RUNCTL_MU_DELETE) and related AE process for deleting pending mass update transactions.

  • Transaction Processor: This is a back-end module that consists of the Configure Processor component for setting up and managing system data that is available for mass updates and an application class that provides access to transaction processing functionality. The role of the Transaction Processor application class is to provide access to services within the Services Oriented Architecture (SOA) to read (select and write, or update, information. Each transaction is an XML message that contains the list of elements that are involved in the update for a specific employee and employee record combination. The Transaction Processor application class interprets this XML message, provides access to the correct service, and returns acknowledgements and any exceptions to the online or batch process that calls it.

  • Execution Manager: This is a back-end module that is a mechanism in the batch mass update process to manage and monitor parallel processing through spawning. Spawning is a method of simultaneously running multiple instances of a child process by a parent process. The Execution Manager enables you to run multiple instances of the batch mass update process and run these instances in parallel to improve performance.

Note:

The Mass Update framework relies on SOA framework.