Show TOC

Allowed Change of Notification Type

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).

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.

Standard Settings

The standard system contains several changes to the notification type that are not considered critical by SAP.

Recommendation

Use the customer exit '....', 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.