The Overdue Event Manager (C1-ODET) is configured to activate all events whose trigger date has arrived. However, there are some implementations that want to control volumes and types of overdue events that are activated. The product provides an object called Overdue Control that may be used by implementations that prefer to work this way. The topics in this section describe overdue control functionality.
A user manually creates an overdue control and defines criteria for selecting overdue events to process.
After a user creates the overdue controls, there shouldn't be any additional work for a user to do. Background processes process the overdue control records in two steps. One step selects overdue processes with events that satisfy the selection criteria. The second step processes the selected overdue processes and activates them.
Copyright © 2007, 2016, Oracle and/or its affiliates. All rights reserved. Documentation build: 2.5.2016 10:21:45 [T1_1454696505000]