Very comprehensive controls are associated with the notification
type. You will find several of these controls directly in the view
in which you define the notification type. These controls are
covered in the first activity of this step.
Several of the notification type-dependent controls are
maintained in their own views. Additional information on these
controls is provided in the subsequent activities for this
There are also other notification processing controls that are
dependent on the notification type. Due to the scope of these
controls, they are described in their own sections of the
Implementation Guide. These controls include:
With the notification type, you define the use of the
Q-notification. This definition is normally made on the basis of
the origin of the notification:
General Q-notification types
Complaints against vendors
Complaints filed by customers
Internal problem notifications
Q-notification types for recording defects for inspection
Defect records for a goods receipt inspection
Defect records for a goods issue inspection
Defect records for an inspection during production
These notification types are predefined in the standard
Use the notification types predefined in the standard system. If
you define your own notification types, use the predefined
notification types as a reference.
Above all, determine which criteria will be used to distinguish
the notification types. The possible criteria might include:
This distinction is required because it allows you to provide the
appropriate screen controls.
The organizational units, departments or process stages in
which the notification originates or which the notification
If you use this criterion in the defects recording function to
categories , you can avoid subdividing the
notification types excessively.
The control parameters that are assigned to the notification
This additional means of differentiating between the notification
types allows you to implement different notification processing
sequences; they may be useful for this reason.
The grouping methods for evaluations
The QM information system summarizes the key figures for
Q-notifications on the basis of notification types. Make sure you
take this into consideration from the beginning!
1. Determine which notification types
will be used in your company and define their parameters:
partner function will be responsible for the tasks
Carry out this partial step after you have processed the section
group will be used for the summarization of data in
the QM information system
2. Define the basic data for this
a) Determine which problem criteria
will be recorded and then select the appropriate catalog from the
predefined catalogs and code groups in the catalog profile.
b) If you want to use class
characteristics as additional problem criteria, activate the
classification of the problem items.
3. You can have the system display
additional entry screens when the initial screens for the quality
notifications are called up. For this to occur, assign the
function modules and initial screens to the
Identify the notification origins and notification types for which
this is necessary. Use the examples provided or have a qualified
person program your own function modules.
4. You can control the formatting of
the long text in the notification screen. If desired, the system
Prevent the texts from being changed
For further details, refer to the online documentation for the
Determine whether such functions are needed for certain
5. If you use the vendor evaluation
in the MM-Purchasing component and you want to use the general
complaint valuation as a contribution to the
criterion , store a default value for the
nonconformity costs for each notification type.
In the settings for the quality inspection, you can reference a
notification type in the
type . The system uses this notification type to
defects for an inspection lot.