Hierarchy
⤷ CRM-CIC (Application Component) Interaction Center WinClient
⤷ INSC (Package) Application Development R/3 Plant Maintenance Customizing
IMG Activity
ID | OLIA_V_TQ85 | Define Action Box |
Transaction Code | S_ALR_87000995 | IMG Activity: OLIA_V_TQ85 |
Created on | 19981222 | |
Customizing Attributes | OLIA_V_TQ85 | Define Action Box |
Customizing Activity | OLIA_V_TQ85 | Define Action Box |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | OLIA_V_TQ85 |
In this step, you define the functions, with which you can generate tasks or activities (known as supplementary actions) for a notification. These functions should be defined using a key and a label. They are assigned to a notification type, and are available at header level when processing notifications. When the function is called up, the system copies the task or activity defined into the notification.
For calling up the function, you can define a label, and an icon together with explanatory quick information.
For each function, you can specify an internally programmed function module that is processed when the function is called up. A dialog with the user can also be programmed here.
If you link a business operation with the function, then the function is only executed if the status of the notification belonging to the operation allows this.
If a task is involved, you have released or completed the alternatives for this status. In addition, you can define a workflow task that is activated when the notification is saved. You can also enter a function module which still changes the workflow container when the notification is saved.
Example
Requirements
Standard settings
To simplify the programming of internal function modules for the users, the standard system contains non-executable references for tasks, activities and changes to the workflow container. You can withdraw the interface, which must form the basis of your own function modules, to these references.
The standard system contains some example functions as ideas and models for your own definition. You can find the relevant function modules using the following generic keys:
- QM06_FA* Funktion modules for activities
- QM06_FM* Funktion modules for tasks
- QM06_CO* Funktion modules for changes to the workflow container
The data for these examples (table settings and suitable catalog entries) is located in client 000 of the standard system, and must be copied into the current clients, where applicable.
Recommendation
Note that, with each release, further useful examples can be included in the standard system. Take note of these examples and copy them into the current clients, as required.
Activities
- Determine which recurring tasks and activities can be defined based on the notification type.
- Define functions linked to the generation of these tasks and activities. Exit the programming.
- Determine whether the tasks should be supplemented by a workflow, and define the workflow tasks.
Further notes
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 | OLIA_V_TQ85 | 0 | HLA0006647 O | |
SIMG | OLIA_V_TQ85 | 1 | HLA0009594 | Service 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_TQ85 | C - View cluster | SM34 | PM/SM PA | Define Follow-Up Functions (Generated Tasks/Activities) | ||
IMGDUMMY | D - Dummy object | BS33 | PM/SM001PA | Display Business Operations |
History
Last changed by/on | SAP | 20000128 |
SAP Release Created in |