An obligation type may be configured to allow obligations of that type to renew. This would only apply to an obligation that supports the concept of expiration. It is also supported on pay plan if the pay plan is being used as a proactive payment collection mechanism (rather than as a method of recovering unpaid debt for other obligations). Renewal may be performed manually or via a background process. When an obligation is created, the expiration date and renewal date may be defined for the obligation. A renewal flag on the obligation type controls if a renewal is required, optional or not allowed. If renewal is required, a user must specify a renewal date when creating the obligation. The renewal date is defaulted on to an obligation based on the valued of the Days Before Expiration for Renewal field on the obligation type.
An algorithm on the obligation type can customize the processing required to renew an obligation.
The Obligation Renewal background process (batch control SARENEW) does the following:
Executes the obligation renewal algorithm (specified on the obligation type) when the renewal date is reached (i.e., it is on or before the process date). This algorithm is responsible for determining the new expiration and renewal dates.
If the renewal algorithm is successful, the renewal and expiration date fields on the obligation / pay plan are updated with the new values.
For pay plan obligations, a new payment schedule may be returned from the renewal algorithm and is appended to the existing schedule.
A user can manually launch the renewal process for a pay plan obligation by clicking Renew on the pay plan maintenance page.
Copyright © 2007, 2016, Oracle and/or its affiliates. All rights reserved. Documentation build: 2.5.2016 10:21:45 [T1_1454696505000]