An overpayment process may be put on hold for one or more reasons. The Standard Overpayment Process base business object supports putting an overpayment process on hold due to a Suppression of overpayments for the taxpayer. When the overpayment process is first created and when it transitions from any state where it may have been waiting for a time, an algorithm checks for suppression and if one is found, the overpayment transitions to On Hold, with “suppression” as the reason code. The base BO also supplies a monitor algorithm to check for the expiration of the suppression and will transition it out of On Hold accordingly. The algorithm will do this if the reason for being On Hold is “suppression”.
If an implementation has another condition that should cause the overpayment to be put on hold, the following should be done:
Design an algorithm that detects the condition and plug that algorithm into the appropriate place in the lifecycle. If the condition is detected, transition the record to On Hold with an appropriate On Hold reason.
Design a monitor algorithm for the On Hold state that checks if the condition still applies (based on the reason code). When the condition no longer applies, the algorithm should indicate that it should transition out of On Hold.
Copyright © 2007, 2016, Oracle and/or its affiliates. All rights reserved. Documentation build: 2.5.2016 10:21:45 [T1_1454696505000]