In this section, you define the informational content of the
notifications and obtain the necessary basic data for this
The basic data includes the following objects:
The catalogs specified in the catalog
profile; these catalogs are used to define the subject
matter of the problem, defect criteria and tasks.
The chapter -> Quality Management -> Quality Planning ->
Basic data ->
contains general instructions on how to set up the catalogs. For
this reason, this section only covers the supplementary activities
for the Q-notifications.
The partners responsible for the problem solution.
You can use different partner types in the Q-notifications (for
example, vendors, customers, administrative offices, system users).
This means you must access the master data in other applications.
The following master record types are currently available in the
R/3 System for partners:
System user master record
The system user master record can be maintained centrally by the
system administrator in the R/3 System.
The organizational unit can be set via the following path: Basis
-> Workflow Management ->
HR master record
The HR master record can be maintained in the HR module (Personnel
Planning and Development).
Vendor master record
The vendor master record can be maintained in the MM module
(Purchasing Guide) and FI module (Accounts payable
Customer master record
The customer master record can be maintained in the SD module and
FI module (accounts receivable accounting).
Customer contact person
This is an additional segment in the customer master that can also
be maintained in the Q-notification.
These partner master records must be
created when the projects for the respective modules are
implemented. Contact the responsible persons or departments once
you have defined the required partners
for the quality notifications.
A quality notification can reference one or more objects that
serve as master data or transaction data in the Logistics
applications. A prerequisite is that the corresponding modules in
the R/3 System are active.
material / plant
equipment (only for category 'service notification')
purchasing document / material document
production order / process order / run schedule header
Depending on the
origin of the notification (customer complaint,
complaint against vendors, internal problem notifications), you
will require different basic data and reference objects; as a
result you will also need different screens. Different notification
types have been defined for this purpose.