Show TOC

 Simplified Notification Processing

Purpose

With the transactions for simplified notification processing, you are presented with a simplified view of a notification in terms of structure and functions. In this processing view, the system only provides the functions that you need to process the notifications quickly and efficiently. This view is primarily designed for users who:

  • Use the notification transactions only occasionally and do not need the full scope of notification processing functions

  • Want to record information in notifications quickly and easily

The transactions for simplified notification processing differ from the transactions for extended notification processing in the following ways:

  • The scope of functions and complexity of the notification structure have been reduced:

  • The recording of notification data is confined to the notification header data, execution data, and partner data.

  • The hierarchical levels and data fields for items, causes, tasks and activities are not visible.

  • You can only create tasks and activities using the action box.

If you have the authorization, you can switch from the transactions for simplified notification processing to the transactions for extended notification processing.

You can use the transactions for simplified notification processing in both the SAP System and on the Intranet.

Prerequisites

In Customizing for Cross Application Components under Start of the navigation path Notification Next navigation step Notification Creation Next navigation step Notification Type Next navigation step : End of the navigation path

  • Allocate Start Values for Transactions , a notification type is maintained for transaction IQS21 and the indicator Proc. initial screen is not set

  • Define Screen Templates , the subscreens for simplified notification processing (subject, execution, partner overview) have been maintained

Process Flow

  1. You create a notification to record a problem or information about a subject matter.

  2. The system automatically selects the notification type that was predefined in Customizing or in the user default values as the default notification type. In the standard system, the General notification is defined as the default notification type.

  3. If the notification type that the system proposes when you create a notification does not suit your problem, you can change the notification type.

  4. You record the required information on the notification screen (for example, short and long texts for subject matter, partner information, and notification priority).

Among other things, you can also:

  1. After you have entered all of the required data, you save the notification.

The system saves the notification data and returns an empty notification screen, so you can create a new notification.

Result

Once you have created and saved a notification in the system, you or another authorized person can process the notification further (for example, as a result of a workflow being triggered or by means of a worklist).