Rework Order and Notification

SPRO>Quality Management>Quality
Notifications>Notification Processing>Additional Notification Functions>Define Action
Box>Define Functions for the Action Box

Define Action Box

In this step, you define additional functions (activities) that can be performed during the processing of
a notification. You define these functions using a key and an identifier and they are assigned to a
notification type. The follow-up functions appear in a separate screen section (action box) in the
header, when you process notifications.
You can control the structure of the action box in the following way:

To call the function, you can define an icon with descriptive quick info in addition to the identifier.

You use the sort number to define the order of the functions as they appear in the action box.

In addition to the notification type, you can enter a scenario. If you do this, the function only
appears in the action box if this scenario is assigned to the notification.

You define the transactions in which the function is to appear in the action box by choosing an
activity type.

The usage defines whether the function is available at notification level or at task level.

You can control the execution of the function in the following way:

You can document the processing of the function using a task or activity.

Note
: When you display the notification, the system only offers the functions that were defined with
attribute "No documentation". The assigned function module cannot make any changes to the
notification.

You can enter a user-defined function module for each function. This module is processed when
the function is called. You can also program a dialog box to be used with this function module.

If you link a business operation to the function, it will only be triggered if the status of the
operation in the quality notification allows this.
(The system checks the user authorization for this operation.)

If the function is generated for a task, there are two statuses for this task, either released or
completed. Additionally, you can define a workflow task that is activated when the notification is
saved. You can also enter a function module that changes the workflow container when the notification
is saved.
For each function, you can also define several dependent functions (dependent follow-up functions).
These dependent follow-up functions can be triggered from the action box, after the higher-level
function has been executed. In this way you can ensure the adherence to certain sequences during
processing. For more information about setting up these sequences, see the documentation for the
function module QM07_MERGE_ACTIONBOX.

here for your notification type you need to define the action here and follow up action

Task list level

SPRO>Quality Management>Quality Notifications>Notification Processing>Additional

Notification Functions-->Define Follow-Up Actions for Tasks

here if you want the action follow up for a task.in the notification..you need to defin here.

Define Follow-Up Actions for Tasks

In this step, you can define follow-up actions for tasks.
You can define a series of follow-up actions that the system will carry out sequentially.
For each follow-up action, you must define:

the level at which the follow-up action will be effective

(Only the task level is relevant.)

You can also define:

how the update will be processed

when the follow-up action will be triggered; that is, with which business transaction will the
follow-up action be carried out.
(The system will check whether the user has authorization for this transaction.)

hope youi have done following cofig:

QCC0>Quality inspection>maintain Inspection type>select 01 inspection type>Notification type:F2

Now

QCC0>quality planning>Basic data>Define catlog Class>select class -->Click on Active notification.

If you set this indicator, the quality notification (already existing) is immediately activated, when the defect data record
is created. This means, that the quality notification receives the status "Outstanding notification" (OSNO).
That means Notification will automatically remain in OSNO even if user do not create it manually.
even if user forget to trigger it it will be geenarted & remain open.