The Overdue Monitor determines if an account violates your overdue rules at least every X days, where X is defined on the Account Type - Controls associated with the account's account type and division (in the field Min Compliance Review Freq (Days)).
In addition, the Overdue Monitor examines an account's debt 'on demand' by looking at a special table called Compliance Review Schedule, which contains the account ID and a review date. Processes can insert a record into this table if something happens to the account. Some examples of base processes that insert a row in this table include:
Bill completion. A row is inserted for the account for the bill due date plus the Compliance Review Grace Days specified on account type control.
FT freeze. A row is inserted for the account for the current date if the obligation's balance is considered overdue or for the payment due date plus the Compliance Review Grace Days specified on account type if the obligation's balance is not yet due.
If a payment is canceled with a cancellation reason that indicates non-sufficient funds.
If a match event is added, changed or deleted.
Additional events. Your implementation can have other events trigger the analysis of an account by the Overdue Monitor. To do this, add logic to insert a row on the Compliance Review Schedule table (CI_ADM_RVW_SCH) when the event occurs populating the account ID and an appropriate review date. Note that the Compliance Review Grace Days on the account type is available for use by any process when determining an appropriate review date.
Copyright © 2011, Oracle and/or its affiliates. All rights reserved.