Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
QI (Package) QM IMG and area menu
IMG Activity
| ID | SIMG_CFMENUOLQWOQV1 | Define Follow-Up Actions |
| Transaction Code | S_ALR_87005381 | IMG Activity: SIMG_CFMENUOLQWOQV1 |
| Created on | 19981222 | |
| Customizing Attributes | SIMG_CFMENUOLQWOQV1 | Define follow-up actions |
| Customizing Activity | SIMG_CFMENUOLQWOQV1 | Define Follow-Up Actions |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFMENUOLQWOQV1 |
Use
In this step, you define follow-up actions for the usage decisions.
Several processing variations are possible for follow-up actions:
- A manual trigger of activities to be carried out manually.
- A manual trigger of activities to be processed by the system.
- An automatic trigger of activities to be carried out manually -> Workflow link.
- An automatic trigger of activities to be processed by the system -> (subject of this step).
- The automatically triggered, system-supported follow-up actions are particularly important. You can define a series of follow-up actions the system will carry out in sequence.
For each follow-up action, you must define the level on which the follow-up action will take effect. The system carries out automatic follow-up actions when a usage decision has been made for:
- An inspection lot
- A partial lot in production
- Operation completion in results recording
You can also specify the business transaction that is to be linked to this follow-up action and how the update is to be processed.
Requirements
You should have maintained the catalog for the usage decision to such an extent that you only need to enter the name of the follow-up action in the selected set codes, once you complete this step.
Standard settings
To make it easier for users to program their own follow-up actions, the 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 to create your own function modules.
The standard system also contains several executable examples of function modules for follow-up actions:
- Sending a mail to a distribution list with information about the usage decision and quality score.
- Sending a mail to a distribution list with information about the usage decision, quality score and stock posting.
In the standard system, the distribution list only contains the name of the user who made the usage decision.
- Updating the equipment data in a calibration inspection (inspection lot origin 14).
Recommendation
- Provide a detailed description of the follow-up actions for a usage decision in the long text for the usage decision code (also include the follow-up actions that will be processed automatically).
- Do not change the function modules that are provided as examples. Make copies of these modules instead and save them under different names.
Activities
- Determine which follow-up actions for usage decisions are needed in your company. Be sure to consider all inspection types, plants and usage decisions.
- For the automatic follow-up actions, specify:
- The series of function modules to be used and the update form for each of these function modules.
- The operations for the follow-up actions (if the activities carried out by the function module are linked to the status management function for the inspection lot).
- Maintain the table of follow-up actions. You must do this before you can maintain selected sets in the usage decision catalog.
- Create the necessary function modules.
Additional Information
Maintaining the Usage Decision Catalog
The follow-up actions are defined for a code in a selected set of catalog 3 (usage decision). The catalog does not differentiate between the levels (inspection lot, operation completion, or partial lot), at which the follow-up action is defined. However, the usage decision transaction checks whether the follow-up action is valid for the relevant usage decision level, when you choose a usage decision code or change a follow-up action.
To prevent an invalid usage decision code from being chosen, we recommend that you define the level of the usage decisions or their related follow-up actions when maintaining catalog 3 by either defining your own code for each level, or creating a separate selected set for each level
If you do not want to trigger a follow-up action from the usage decision, leave the follow-up function field in the selected set blank.
Follow-up action chains
Quality Management 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 activities, these partial activities must be numbered in the sequence to be carried out and each activity must be linked to a separate function module.
Links to operations
- If you want to assign an operation from the general status management function to a follow-up action, the operation must be supported for the inspection lot's object type and it must be compatible with the status profile assigned to the inspection type. Also refer to the step Define status profile. The F4 help for the operation field shows you which operations are available for use.
Operations play an important role in managing the statuses of inspection lots. For more information on this subject, refer to Status Management.
To help you select an appropriate operation for a follow-up action, you can display the definitions of operations that support follow-up actions for usage decisions (you cannot, however, change these definitions). To do this, proceed as follows: - Display the list of operations. Call up the operations for inspection lots by entering QM*; then select the desired operation.
- Select the function Where-used list (not Follow-up action). In this view you see:
- That the operation applies to the object type insp. lot, ...
- Which inspection lot statuses this operation sets and deletes
- Which other statuses influence this operation
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 | SIMG_CFMENUOLQWOQV1 | 0 | HLA0006213 | Inspection Lot Completion |
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 | C - View cluster | SM34 | Follow-Up Actions | |||
| IMGDUMMY | D - Dummy object | BS33 | OLQW | Display Transactions |
History
| Last changed by/on | SAP | 20020116 |
| SAP Release Created in |
