Severance Process - Severance Events
The events page contains the activities that will be performed to persuade the customer to pay the outstanding debt. Open this page using and navigate to the Events page.
The Description of Page section below describes the fields on this page. Refer to How To Perform Common Severance Process Functions for more instructions describing how to use this transaction.
We strongly recommend that you understand the information described in How Are Severance Events Completed? before using this page.
The number and type of events associated with a severance process are defined by the process's severance process template (which is defined on the first page). Refer to Setting Up Severance Process Templates for more information.
Description of Page
The top portion of every page in this page contains the following information:
Severance Process is a concatenation of summary information about this severance process. It is composed of the name of the main customer on the account, the SA business unit and SA type, set ID and severance process template name, the process status, the reason code for the process status and the creation date of the process.
ID is the unique system-generated identifier for this severance process.
The Severance Events scroll contains the severance events that comprise the severance process. The grid at the bottom (when visible) shows the events that must be completed before the severance event is triggered. Only one severance event is displayed at a time.
Event Sequence is the unique identifier of the event.
Severance Event Status defines the state of the event.
For more information, refer to Severance Event Lifecycle.
The Severance Event Type defines the event's activity (e.g., a field order is generated, a To Do entry is generated, a letter is sent).
For more information, refer to Setting Up Severance Event Templates.
If Dependent on Other Events is turned on, then the event's trigger date is only determined after the event(s) on which it depends are completed. When this switch is on, a grid appears at the bottom of the page in which you define the event(s) on which this event depends.
For more information about dependent events, see Severance Event Dependencies & Trigger Date.
The Trigger Date defines the date when the system completes (i.e., executes) the event. This field is gray when the event is dependent on the completion of other events.
For more information about a severance event's trigger date, see Severance Event Dependencies & Trigger Date.
Days After Prev Response defines how a dependent event's trigger date is calculated. The trigger date is set equal to X days after the last dependent event is completed, where X is the number in this field. This field is gray when the event is not dependent on other events.
For more information about dependent events, see Severance Event Dependencies & Trigger Date.
If the status of the event is complete, the Completion Date is displayed with the date on which the system completes the event. If the status of the event is cancelled, the Canceled Date is displayed with the date on which the event was canceled.
The grid at the bottom of the page contains the events on which this event depends. This grid is only visible when the event is dependent on other events (as defined by the Dependent on Other Events switch). To add additional sequences press the + button (insert row), and define the sequence of the event on which this event depends.