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 | OLQN_CH | Allowed Change of Notification Type |
| Transaction Code | S_ALR_87100661 | (empty) |
| Created on | 19991115 | |
| Customizing Attributes | OLQN_CH | Allowed Change of Notification Type |
| Customizing Activity | OLQN_CH | Allowed Change of Notification Type |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | OLQN_CH |
In this step, you define the changes to the notification type that are allowed.
This step only deals with the changes to the notification type that are made when you create or change notifications using the simplified transactions (IQS21 or IQS22).
- When creating notifications, you can only change the notification type under the following conditions:
- The change is explicitly allowed by the Customizing table.
- The notification still has the status 'Outstanding'.
- When changing notifications, you can only change the notification type under the following conditions:
- The change is explicitly allowed by the Customizing table.
- The notification still has the status 'Outstanding'.
- The original notification type has the origin "General notification".
You can only allow the notification type to be changed, if this will not lead to any inconsistencies.
Example
You have created a notification of type "General notification" and want to change this into a notification of type "Quality notification" to record defect data in the notification items.
Requirements
Standard settings
The standard system contains several changes to the notification type that are not considered critical by SAP.
Recommendation
Use the customer exit 'QQMA0029' to check for inconsistencies caused by the field values, when you change the notification type. If inconsistencies occur, you can use the exit to prevent this type of change. The standard system contains examples of function modules for each notification type for this customer exit. You can find the fields that are considered critical by SAP in the coding for the relevant examples.
Activities
Determine which changes to the notification type are required in your company and do not lead to inconsistencies.
Enter the corresponding pairs of notification types in the table.
Further notes
You can change the notification type, if you create a new notification by using an existing notification as a copy model. This type of change is not affected by this Customizing setting.
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| 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 | OLQN_CH | 0 | HLA0006831 O | |
| SIMG | OLQN_CH | 1 | ALR0077563 O | |
| SIMG | OLQN_CH | 2 | BIO0000031 O | |
| SIMG | OLQN_CH | 3 | HLA0009594 O | |
| SIMG | OLQN_CH | 4 | 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_TQ82 | V - View | SM30 | Allowed Change of Notification Type |
History
| Last changed by/on | SAP | 20000128 |
| SAP Release Created in |
