Executing a Rollback When Using the “Add More“ Feature in the Payroll Wizards

Note: This page is accessible to non-customer users only.

When you execute a Rollback to the Payroll Deduction Codes wizard or the Payroll Earning Codes wizard in Activate, the result is unique when any of the following situations apply:

• You used the Add More feature to change existing codes.
• You used the Add More feature an additional time to create new mappings.
• You have remaining Work in Progress.

Scenarios

What happens to codes that I've updated in “Add More“ runs when I execute a rollback?

For categorization, Activate manages codes in “clusters.“ It groups together codes with the same code name, description, and country, but with different Payroll Identifiers, as a single cluster in the Payroll wizards.

Scenario:

1. During the initial installation of deductions, you installed a deduction with a Payroll Identifier value of PID1 and categorized the deduction as “pre tax.”
2. During the “second installation,” you used the Add More feature to add a deduction with the same codename, description, and country, but with a Payroll Identifier value of PID2 and it was categorized it as “post tax.”
3. Rollback the system to before the first installation.

Outcome:

Because the two deduction codes have a conflicting categorization, they can’t be clustered and must be recategorized. Activate shows a page explaining what has happened, and you return to the start of the Payroll Deduction Codes wizard to recategorize the cluster. You must decide whether this cluster is pre or post tax.

This situation applies to any kind of categorization of clusters of codes. You have to adjust only clusters that are invalid due to a Rollback. All other previous work remains as is. Although you’re required to complete all pages of the wizard, some pages might not require that decisions be made and you can click Next to move forward quickly.

What happens to mappings that I've created in a second “Add More“ run when I execute a rollback?

Mappings created in “Add More“ runs might depend on items created in previous installs and can be lost as a result of Rollbacks.

Scenario:

1. In the initial installation of deductions in the Payroll Deduction Codes wizard, you create Deduction A.

2. During the “second install“ using the Add More feature, you map Deduction B to the existing Deduction A.

3. You Rollback to before the first installation.

Outcome:

Without the items created in the initial installation, the mapping created in the second run no longer exists and must be regenerated. Activate shows a page explaining what has happened, and you return to the start of the Payroll Deduction Code wizard. You can complete the wizard, treating Deduction B as a new code and/or merging it with Deduction A.

What happens to work left “In Progress“ when I execute a rollback?

In general, work that is currently “in progress” is lost when you roll back to a previous install in the same module.

Scenario:

1. You complete the initial installation in the Payroll Deduction Codes wizard.
2. You start a “second install“ using the Add More feature, but you don’t complete the install.
3. You rollback Activate to before the initial installation of the Payroll Deduction Codes wizard.

Outcome:

The work in Step 2 (Add More) is lost. In-progress work in any module is lost when you Rollback to an earlier completed installation in that same wizard. For example, in progress deduction code work is lost when a Rollback returns you to a prior, completed deduction code installation.