The system allows you to determine the efficacy of proposed overdue process templates using a small subset of taxpayers before implementing the templates on the entire taxpayer base. We use the term "champion / challenger" to reference this functionality.
We'll use an example to explain. Let's assume your prevailing overdue process template for individual taxpayers starts with a "gentle reminder" letter followed 10 days later by a letter threatening to place a lien to secure the debt if payment is not received. You may want to experiment with the impact of a change to this template. For example, you may want to change the "gentle reminder" to something more assertive and follow this up 5 days later with an even sterner warning. You can use the "champion / challenger" functionality to perform this experiment.
The following points describe how to implement "champion / challenger" functionality:
Set up a "challenger" overdue process template for each template that you want to experiment with.
Insert a new Champion/Challenger option on the Overdue Processing Feature Configuration for every champion template. Each option's value defines:
the "champion" overdue process template code
the "challenger" overdue process template code
the percentage of the time the system should use the "challenger" template
Keep in mind that you can only experiment with one challenger template per champion template.
After setting up the above, the Overdue Rule Plug-In will use the challenger template X% of the time rather than the champion template.
Copyright © 2011, Oracle and/or its affiliates. All rights reserved.