SAP ABAP IMG Activity OLIA_V_TQ07 (Define Follow-Up Actions for Tasks)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM-CIC (Application Component) Interaction Center WinClient
     ⤷ INSC (Package) Application Development R/3 Plant Maintenance Customizing
IMG Activity
ID OLIA_V_TQ07 Define Follow-Up Actions for Tasks  
Transaction Code S_ALR_87001000   IMG Activity: OLIA_V_TQ07 
Created on 19981222    
Customizing Attributes OLIA_V_TQ07   Define Follow-Up Actions for Tasks 
Customizing Activity OLIA_V_TQ07   Define Follow-Up Actions for Tasks 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name OLQN-MF    

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:
    1. the series of function modules and their update form
    2. 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.

Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG OLQN-MF 0 ALR0077563 O  
SIMG OLQN-MF 1 BIO0000031 O  
SIMG OLQN-MF 2 HLA0006832 Processing Quality Notifications 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
V_TQ07_QN C - View cluster SM34 PM/SM PA Define follow-up actions 
IMGDUMMY D - Dummy object BS33 PM/SM002PA Display Business Operations 
History
Last changed by/on SAP  19991217 
SAP Release Created in