Creating a new Notification Type

Objective

After completing this lesson, you will be able to create a new Notification Type

Notification Category and Notification Type

The graphic shows notification categories and notification types. Information is provided in the next paragraph.

The advantage of using general notifications is that you can make a central, coordinated entry for any kind of requirement. The person making the entry does not have to be a trained maintenance planner.

In the Enterprise system, the notification type is assigned to an application such as customer service, quality management, or plant maintenance.

You can use the individual notification types to define different classes of maintenance notifications and then use these classes when making selections. You can use the notification type to define the use of the maintenance notification for particular business processes. In the standard system, notification types are structured according to functional criteria (malfunction notification, maintenance request, activity report).

Settings for Notification Types

  • Long text control:

    This setting allows you to lock a text and add a line to the log (changed by, date of change, and so on).

  • Notification origin:

    This defines the basic character of a notification (for example, requirement or malfunction report).

  • Reference time:

    The reference time is the proposed time for the completion of the notification. Once the time is set, it identifies the historical reference for completion.

  • Order type:

    A default order type can be specified when creating an order from a notification.

  • Number assignment:

    The number range used.

  • Priority/priority type:

    This setting allows you to prioritize notifications in connection with date proposals.

  • Partners:

    Contact persons who should be available in notification and order processing (supplier, customer, and so on).

  • Object information:

    Information concerning the reference object of the notification or order and that can be displayed from the notification or the order.

  • Field selection:

    Identifies what fields of data in the notification are required, optional for entry, display only, or hidden from view.

  • Catalog/catalog profile:

    A variety of catalogs can be assigned to a notification, such as the object part, damage, cause of damage, task, and activity catalogs. The catalog profile limits the selection of available code groups referring to specific subject areas (car type, data processing, production machines, and so on).

General Settings for Maintenance Notifications

In this section, we will look at the settings that can be applied to all types of maintenance notifications.

Maintenance Notifications Settings

The following settings can be used for all types of notification:

  • Field selection:

    The field selection for notifications allows you to control certain fields together for all notification types (for example, light color for the notification from and notification date fields).

  • List editing:

    You can set up list processing for notifications in Customizing so that it contains standard values for selection screens, field selection, and the display variant.

  • The system condition indicator:

    The system condition indicator defines the conditions that a technical system can have (operational, out of order, and so on). These settings are defined at client level and are not dependent on the notification type.

  • Transaction start values:

    The transaction start values for a notification transaction define whether an initial screen should be displayed and which default notification type should be used. Initial Screen must be selected if you want to access the initial screen with the field for the notification number and notification type. You can also define which screen should be the first detail screen. The notification header screen is the initial screen in the standard system, but this can be changed.

How to Configure a Notification Type

Notification Screen Configuration (SAP GUI)

Screenshot of the Change PM Notification: Malfunction Report with the tabs and subscreen/fields highlighted in yellow. Information about the configuration of the screen layout is provided in the next paragraph.

The notification interface can be configured to meet the needs of your organization.

You can configure tabs for each notification type. A total of 26 different tab pages are available (22 notification-based, 4 item-based).

You can define a simple view or an enhanced view for each notification type. This means that a simple screen appears for the person entering the notification and a detailed appears for the person processing it.

The type of transaction determines the view displayed:

  • The plant maintenance transactions IW24 (Malfunction Report), IW25 (Activity Report), and IW26 (Request) access the enhanced view.

  • Transaction IQS21 accesses the basic view.

You can define screen areas (sub-screens) for each tab. 21 different screen areas are available.

You can assign the tabs their own internal heading and a graphical symbol, if required.

You can easily activate or deactivate predefined tabs.

Within a notification type, you can also specify different layouts for the notification screen, for example, to distinguish between display mode and change mode. You might want only the core data to be visible in display mode, and all data to display in change mode. This is controlled using activity categories (create, change, and display).

How to Configure the Notification Screen  (SAP GUI)

Log in to track your progress & complete quizzes