SAP ABAP IMG Activity OLIA_OIMX (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_OIMX | Define Follow-Up Actions for Tasks |
Transaction Code | S_ALR_87000940 | IMG Activity: OLIA_OIMX |
Created on | 19981222 | |
Customizing Attributes | OLIA_OIMX | Define follow-up actions for tasks |
Customizing Activity | OLIA_OIMX | Define follow-up actions for tasks |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | OLIA_OIMX |
In this step you define the follow-up actions for tasks.
You can define chains of follow-up actions that the system performs in sequence by means of a counter.
For each follow-up action you must determine
- the level at which it should work
(task level only) - how the update is processed
- the time at which the follow-up action is initiated.
You can also determine
- the business operation that is performed with this follow-up action. You can find more information on this in the chapter on basic settings, Maintaining user status.
Requirements
The task catalog should be completed and the assignment of follow-up actions should be activated.
Standard settings
The follow-up actions predefined as standard are just examples; if required, you can define and program your own complete set of follow-up actions.
As follow-up actions vary from user to user, the standard setting contains only
- a non-executable sample of follow-up action modules
From this sample you can derive the interface which must form the basis of the function module. - executable examples of follow-up action modules
Recommendation
- Describe the follow-up actions belonging to a task detailed in the long text of the task code.
- Do not change the example modules; you should work with copies that you identify with your own name assignment.
Activities
- Determine the follow-up actions for tasks in your company, taking all notification types into account.
- Maintain the table of follow-up actions.
- Create appropriate function modules.
Further notes
- SAP PM enables you to introcuce automatic follow-up actions in the form of function modules. If a follow-up action comprises several individual actions, these sub-actions are numbered in the sequence of your procedure and each is linked to one function module. You must determine the required time of update for each follow-up action procedure.
- If you want to assign an operation from general status management to the follow-up action, this operation must be compatible with the object type "Task for PM notification/service notification". Call up F4 help on the field "Operation" to see the relevant operations.
Refer also to the chapter User status for notifications.
Business Attributes
ASAP Roadmap ID | 255 | Create Interfaces |
Mandatory / Optional | 3 | Nonrequired 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 | OLIA_OIMX | 0 | HLA0009594 O | |
SIMG | OLIA_OIMX | 1 | HLA0006647 | Maintenance 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 | IH | Follow-up actions for tasks |
History
Last changed by/on | SAP | 20040302 |
SAP Release Created in |