Show TOC
Define
Follow-Up Actions for Tasks
In this step, you can define follow-up actions
for tasks.
You can define a series of follow-up actions
that the system will carry out sequentially.
For each follow-up action, you must
define:
- the level at which the follow-up action will
be effective
(Only the task level is relevant.)
You can also define:
- how the update will be processed
- when the follow-up action will be triggered;
that is, with which business transaction will the follow-up action be carried
out.
(The system will check whether the user has authorization for this
transaction.)
Requirements
The
task catalog must be set up to allow the assignment of follow-up
actions.
The task catalog should be maintained to such
an extent that you should only have to supplement the task codes with the
names of the follow-up actions, once you complete this step.
Standard
Settings
To make it easier for users to program their
own follow-up actions, the standard system contains a non-executable
example of a function module for follow-up actions. You can copy the
interface in this example and use it in your own function modules.
Recommendation
- Provide a detailed description of the
follow-up actions for a task in the long text for the task code. Make a
distinction between follow-up actions that:
- must be carried out manually by a
partner
- are carried out automatically by the
system
- Do not change the function modules that have
been provided as examples. Instead, make copies of these function modules and
save them under different names.
Activities
1. Determine
which follow-up actions for tasks are needed in your company and which should
be automated.
2. For
automatic follow-up actions, define:
a) the series
of function modules and their update form
b) the business
transactions for the follow-up actions (provided the function module is to be
linked to the status management function for the task)
3. Maintain the
table of follow-up actions.
4. Create the
corresponding function modules.
Further
Notes
- The system allows you to implement automatic
follow-up actions in the form of function modules. If a follow-up action
consists of a series of individual actions, these actions must be numbered in
the sequence they are to be carried out and each action must be linked to a
function module.
- If you want to assign a business transaction
from the general status management function to a follow-up action, the
transaction must be supported for the object type "Task for Quality
Notification." The F4-help for the "Transaction" field shows you which
transactions you can use.
Business transactions are pertinent to the status management of
tasks. Refer to the chapter Basic settings, Central functions,
Status management for additional information. Also refer to the
item
Status profile for notification type.
To be able to select an appropriate transaction for a follow-up action, you
can display the definitions of the business transactions for follow-up actions
for tasks. You cannot, however, change these definitions yourself. To select a
transaction, proceed as follows:
- Display the list of business transactions.
Select the transactions used for notification tasks by entering 'QN9*'; then
select the desired transaction.
- Select the 'Where-used list' function (not the
'Follow-up action' function). In the resulting display, you can see:
- that this transaction supports the object type 'task'
- which task status this transaction sets and deletes
- which statuses influence this transaction
- The follow-up actions for tasks use the same
techniques as the follow-up actions for the
usage decision.