SAP ABAP IMG Activity OLQN-SAB (Define Action Box)
Hierarchy
☛ EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials
   ⤷ QM-IM (Application Component) Quality Inspection
     ⤷ QSTABI (Package) Stability Study
IMG Activity
ID OLQN-SAB Define Action Box  
Transaction Code S_ALN_01000477   (empty) 
Created on 20011220    
Customizing Attributes OLQN-SAB   Define follow-up functions 
Customizing Activity OLQN-SAB   Define Action Box for Stability Study 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name OLQN-AB    

In this step, you define additional functions, known as actions, that can be performed during the processing of a notification. You define these functions using a key and an identifier and assign them to a notification type. The functions appear as actions in a separate screen section (action box) in the header, when you process notifications or tasks.

You can control the structure of the action box in the following way:

  • To call the function, you can define an icon with a descriptive quick info in addition to the identifier.
  • You use the sort number to define the order of the functions as they are to 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 also 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 for the notification or notification item.
    Note: When you display the notification, the system only offers the functions that were defined with the 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 transaction to the function, it will only be triggered if the respective status of the transaction in the quality notification allows this.
    (The system checks the user authorization for this transaction.)
  • 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). The system offers these dependent follow-up functions for selection in the action box after the higher-level function has been executed. In this way, you can ensure adherence to certain sequences during processing. For more information about setting up these sequences, see the documentation for the function module QM07_MERGE_ACTIONBOX.

Example

Requirements

Standard settings

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

The standard system contains various sample functions that you can use as sources and copy templates for your own definitions. You can find the relevant function modules using the following generic entries:

  • 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:
    1. Assign the function to the notification type.
      2. On the detail screen:
    2. Define the key and description for the function.
      3. If a function can be used for an item, you can make this clear in the description.
    3. Define the controls for the function.
    4. Enter a function module with the required flow logic (optional).
    5. Define icon and quick info.
      6. In the quick info, you can also indicate whether a function can be selected for an item.
    6. 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 a workflow and define the workflow tasks as 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.

Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG OLQN-AB 0 ALR0077563 O  
SIMG OLQN-AB 1 BIO0000031 O  
SIMG OLQN-AB 2 HLA0006832 Processing Quality Notifications 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
V_TQ85 C - View cluster SM34 0000000000 Define Functions for the Action Box 
IMGDUMMY D - Dummy object BS33 OLQN-SAB Display Business Transactions 
History
Last changed by/on SAP  20011220 
SAP Release Created in 110