The lifecycle of a suppression object depends upon the configuration of the associated business object. The base package includes a sample C1-Suppression business object with a simple lifecycle, as follows:
The suppression is initially created in the Pending state. The suppression has no effect while in this state - the details may be edited without triggering other processing such as P&I updates. A deferred monitoring algorithm can be configured to automatically transition the suppression to Active if the start date is on or before the system date. Base algorithm C1-SUPP-AC provides an example of this logic.
The user can manually transition the suppression to the Active state once the details are finalized. Suppressions that are created by other processes will typically be activated by the initiating process. An enter algorithm may be configured to trigger validation specific to the Active state. The base algorithm C1-SUPP-VAAC provides an example of this logic.
A monitor algorithm may be configured on the Active state to check for suppressions that have been open too long. The base algorithm C1-SUPP-MAXD provides an example of this logic. An exit algorithm can be configured to complete all open monitoring to do entries when the suppression is no longer active. Base algorithm C1-SUPP-CTDO provides an example of this logic.
A suppression object can be released by transitioning to the Released state or by updating the end date and having the suppression transition automatically. Suppressions that are created by other processes will typically be released by the initiating process. A monitor algorithm may be configured on the Active state to check for suppressions whose end date is populated and automatically transition them to Released . The base algorithm C1-SUPP-REL provides an example of this logic. An enter algorithm may be configured to provide a default end date or validate the existing end date for a suppression transitioned to Released . The base algorithm C1-SUPP-END provides an example of this logic.
A suppression object can be Canceled from the Pending or Active states. Suppressions that are created by other processes will typically be canceled by the initiating process if appropriate.
If the suppression affects penalty and interest, P&I should be updated for the related obligations when the suppression period starts and ends. An enter algorithm may be configured to trigger P&I updates when the suppression enters the Active , Released or Canceled states. Base algorithm C1-SUPP-UPI provides an example of this logic
Copyright © 2011, Oracle and/or its affiliates. All rights reserved.