SAP ABAP IMG Activity OLQN_CH_QM (Define Allowed Changes of Notification Type)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM (Application Component) Customer Relationship Management
     ⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       ⤷ QM00 (Package) QM central QM functions
IMG Activity
ID OLQN_CH_QM Define Allowed Changes of Notification Type  
Transaction Code S_EBS_44000340   (empty) 
Created on 20110112    
Customizing Attributes OLQN_CH_QM   Define Allowed Changes of Notification Type 
Customizing Activity OLQN_CH_QM   Define Allowed Changes of Notification Type 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name OLQN_CH_QM    

Use

In this Customizing activity, you define which changes of notification type are allowed.

Standard settings

Included with the scope of delivery are some changes of notification type that are regarded by SAP as being noncritical.

Simple Change of Notification Type

When creating or changing notifications using the non-QM-specific notification transactions (IQS21, IQS22), the following applies:

  • When creating notifications, you can change the notification type under the following conditions:
    • The change was explicitly allowed in this table.
    • The notification still has the status Outstanding Notification.
  • When changing notifications, you can change the notification type under the following conditions:
    • The change was explicitly allowed in this table.
    • The notification still has the status Outstanding Notification.
    • The original notification type has the notification category General Notification (G0).

You can only allow changes of notification type in which no inconsistencies can occur.

Example

You have created a notification of the category General Notification and want to change it to a notification of the category Quality Notification to be able to store defect data in the notification items.

Extended Change of Notification Type

The extended change of notification type using the QM-specific notification transactions (QM01, QM02) allows a change of notification type in the following cases:

  • The extended change was explicitly allowed in this table.
  • The original notification type and the target notification type have the notification category Quality Notification.
  • The notification does not yet have the status Notification Completed.

    Note that a subsequent change of notification type is also not possible if the notification was reset to the status Notification in Process after being completed.

  • The notification does not have the status Defects Recording.

Requirements

You have used the authorization object B_NOTIF_EX to specify for certain user groups whether an extended change of notification type is allowed for the current notification type.

Activities

After you have established which changes of notification type are necessary in your enterprise, proceed as follows:

  1. Enter the relevant combinations of notification types in the table.
  2. For the notification types for which you want to allow an extended change, set the relevant indicator.

Further notes

When the notification type is changed, the system does not assign a new notification number. For example, a customer complaint (Q1) still retains its original number from the Q1 number range even after being changed to a complaint against the vendor (Q2).

In the same manner, all data in the original notification type (such as reference objects) are retained after a change of notification type. This also applies even if specific data is irrelevant for the target notification type. To override this behavior, implement the Business Add-In (BAdI) BADI_IQS0_NOTIF_TYPE_CHANGE.

Example

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 OLQN_CH_QM 0 HLA0006831 Creating Quality 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  
History
Last changed by/on SAP  20110112 
SAP Release Created in 606