SAP ABAP IMG Activity OLQU_SS02 (Define Status Profile)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM (Application Component) Customer Relationship Management
     ⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       ⤷ QI (Package) QM IMG and area menu
IMG Activity
ID OLQU_SS02 Define Status Profile  
Transaction Code S_ALR_87004672   IMG Activity: OLQU_SS02 
Created on 19981222    
Customizing Attributes OLQU_SS02   Define status profile 
Customizing Activity OLQU_SS02   Define status profile 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name OLQU_SS02    

This section provides instructions on how to use the general status management function for system objects, to define your own status profiles.

General

This status management is used in the following objects of the QM component:

Features of general status management

In the SAP system, a distinction is made between the system status and user status.

  • System status

    The system contains a central set of statuses that apply to and can be used by all applications. These statuses are maintained by SAP and cannot be changed. This type of status is called a system status.

  • Business transactions

    The system also contains a set of business transactions that apply to and can be used by all applications. These business transactions are maintained by SAP and cannot be changed.

  • Business transaction - system status

    SAP predefines a system status for each business transaction and defines whether the corresponding system status is deleted or set during the transaction. SAP also defines the business transactions that are allowed for a particular system status. A business transaction is only allowed if it is not forbidden by a status.

  • Objects - business transactions

    SAP also defines which objects are allowed for which business transactions.

  • Result

    The assignments listed above indicate which system statuses are possible for an object, and which system statuses are set in the various transactions.

  • Status profile for user status

    You can define your own status profiles and assign them to an object. Each status profile contains one or more authorized user-defined statuses. For each of these statuses, you can determine the system response within the framework of the business transactions predefined by SAP. The user status refines the sequence of system statuses predefined by SAP to suit your requirements. However, this is only possible within the SAP fixed profile. You cannot overide the system status with the user status.

    In the status profile:

    • You define your own statuses (user status) and document their functions in an accompanying long text
    • You define the status numbers for the user status, which specify the possible sequence of user status changes
    • You define an initial status that is automatically activated when the object is created
    • You define which user status is automatically activated when a business transaction is carried out
    • You define which transactions are allowed or not allowed when a certain status is active
  • Status number

    You can define a status number for each user status. The status number determines the sequence in which the user statuses can be activated. There can only be one user status with a status number active at any one time. If you assign a status number to a user status, you must also specify a lowest and highest status number for this status. These values delimit the status number interval from which the next user status can be chosen.
    If you do not assign a status number to a user status, this user status can always be set, even in addition to a status with a status number.

  • Authorization key

    For each status, you can define an authorization key.

Execution

The following steps describe how you can supplement the general status management with your own user statuses and how to assign certain business transactions to these statuses.

  1. Create a status profile.
  2. Assign the status profile to the object types in question.
  3. Define user statuses.
  4. Assign business transactions to the user statuses.
  5. Translate the status profile and the user statuses.
    Note: The mnemonic keys (names) of the statuses are also translated, as well as the short text.
  6. If required, assign the authoriaztion keys that you previously defined to the statuses.
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 OLQU_SS02 0 HLA0009540 Quality Management 
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
BSVS L - Logical transport object BS02 OLQU Define status profile 
V_TJ10 V - View SM30 OLQU Define authorization key for status 
History
Last changed by/on SAP  19981222 
SAP Release Created in