Oracle Tasks is a component of CRM Foundation and has predefined task types. If you use dunning plans with callbacks, Oracle Advanced Collections creates tasks for the assigned collectors using the available callback task type. Run the IEX: Create Dunning And Broken Promise Call Backs concurrent program to display dunning callbacks in the Collector's Work Queue.
To prevent the tasks from failing, navigate to the Define Task Status page. Use CRM Administrator responsibility > Task and Escalation Manager > Setup
Make sure the query status is Cancelled and check if the Task Status Check box is checked or unchecked in the Task and Escalation Status window.
Refer to the Implementing Task Manager section of the Oracle Common Application Calendar Implementation Guide.
Oracle Advanced Collections functionality is limited to the following:
Defining Task Status (Status Transition and Rules is not supported)
Defining Task Priorities
Defining Task Types (Resource Requirements and Workflow are not supported)
Defining Task Templates (Dependencies and recurrences are not supported)
When setting up task types, you must map all task types.
Suggestion: Map the task types you want to use to Collections. Map all unwanted task types to another application, such as Sales. This will remove all unwanted task types from the drop down list in Oracle Advanced Collections.