Define Action Box (SAP Library

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.

Standard Settings

To simplify the programming of your own function modules, the standard system contains non-operational examples for tasks, activities and change workflow container. You can take the interface that supports your own function modules from these examples.

The standard system contains various example functions that you can use as sources and copy models for your own definitions. You search for the appropriate function modules using the generic keys:

QM06_FA* Function modules for activities

QM06_FM* Function modules for tasks

The data relating to these examples (table settings and corresponding catalog entries) is contained in client 000 in the standard system and must be transferred to the current client if required.

Recommendation

Note that with each Release, there may be additional useful examples contained in the standard system. Transfer these examples if required into the current client.

Activities

1. Determine which recurring functions you can define, dependent on the notification type.

2. Define these functions. Perform any programming necessary for the function modules you require. Proceed as follows:

a) Define the key and identifier for the function

b) Assign a function to the notification type

c) Define the controls for the function

d) Enter a function module with the required flow logic (optional)

e) Define icons and text

f) Enter code group and code for the task or activity from the catalog that is assigned to the notification type, if the function is to be documented as a task or activity.
You must enter a status for the task that is to be included in the notification.

3. Determine if tasks are to be supplemented by the workflow and define the

workflow tasks if required. If the assigned function module has a container for the Workflow task, the container must also have an entry.

4. Determine whether the functions are to be triggered in a particular sequence and if so, define the dependent follow-up functions.

Further Notes

In the notification header, only those functions appear, for which the user has authorization. Tip: For tasks and activities, use the authorization for use of certain code groups.