Show TOC

Notification Creation

In this section, you define notification types. You define the screen structure and the basic data that you require in the notification for each notification type.

The basic data includes:

• The catalogs used in the catalog profile to define the subject matter, defect characteristics and tasks.
  You can find general instructions for impementing catalogs in the section Quality Management -> Quality Planning -> Basic Data -> Catalogs. The information below therefore only relates to the additional steps that are required for notifications.

• Partners Involved in a Notification
  You can use various partner types in notifications, such as, vendors, customers, administrative office, system user. This means that you access master data from other applications. At the moment, there are the following master record types available in the R/3 System:

The notification can relate to one or more objects that appear as master data or movement data in Logistics. A prerequisite for this is that the relevant components of the R/3 System are active.

• Master Data

• Movement data

Notification items can reference ( assemblies ).
(Note: You can define a special default for the use of bills of material
in the settings at client level).

You require different basic data and reference objects, together with different screens, depending on the origin of the notification. You define various notification types to serve this purpose.
You can define notification types for the following origins:

• Maintenance Notification

• Service Notification

• Quality Notification

• Claim

• General Notification