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-SST | Define Status Profile |
| Transaction Code | S_ALN_01000483 | (empty) |
| Created on | 20011221 | |
| Customizing Attributes | OLQN-SST | Define Status Profile for Stability Study |
| Customizing Activity | OLQN-SST | Define Status Profile for Stability Study |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFMENUOLQNOQNM3 |
In this step, you define the status management function for the notifications.
Notifications use the general status management function for SAP objects. A brief explanation of this concept is provided at the end of this text. For a detailed description of the status management function and related technical information, refer to the chapter "Basic Settings and Environment" in the section Status Profile.
Using the general status management function, you can also define your own status profiles to supplement the predefined system statuses. You can use these status profiles to control the sequence of certain transactions. Examples of such transactions are:
- Releasing a task
- Completing a notification
For each notification type, you can define different status profiles for:
- The notification header
- A task
Activities
- Determine whether additional user statuses are required for certain notification types.
- Define the status profiles for the notifications. For each notification type, you can define appropriate status profiles for the following object types:
- Notification header
- Task
- Choose the appropriate status profiles for each notification type.
Additional Information
In the SAP system, a distinction is made between a system status and a user status.
- System Status
The SAP system contains a collection of statuses that apply to and can be used by all applications. These statuses cannot be changed.
- Business Transaction
The SAP system contains all business transactions that apply to and can be used by all applications. These business transactions cannot be changed.
- Business Transaction / System Status
A system status is assigned to each business transaction. A determination is also made whether the corresponding system status is to be deleted or set when the transaction is carried out.
- Objects / Business Transaction
In addition, which business transactions can be used with which SAP objects is also defined. This definition specifies the maximum number of system statuses allowed for an object and which statuses can be set for individual transactions.
- Status Profile
You can define your own status profiles. You must assign at least one object to each status profile. Each status profile contains one or more allowed statuses. Within the scope of the business transactions predefined by SAP, you can specify how the system will behave for each of these statuses. In the status profile, you define:
- Your own statuses (user statuses) and document their functions in a corresponding long text
The user status allows you to refine the sequence of system statuses predefined by SAP to your own requirements. However, this is only possible within the fixed profile defined by SAP; you cannot override the system status with the user status. - The status order numbers for user statuses which determine the possible sequence of user statuses
- An initial status that is automatically activated when you create the object
- Which user status is automatically activated when you execute a business transaction
- Which transactions are allowed or not allowed when a certain status is active
- Status Order Number
You can define a status order number for each user status. With the help of the status order number, you determine the sequence in which the user statuses can be activated. If you do not assign a status order number to a user status, this user status can always be set. However, only one user status with status order number may be active at one time. If you assign a status order number to a user status, you must also specify a lowest and a highest status order number for this status. These numbers limit the order number interval from which the next user status can be chosen.
- Changeability of the User Status
You can use the Business Add-In for Control of Changeability of the User Status to determine for each notification type whether or not a particular user status can be changed.
When you maintain the status profile, you can, for example, specify whether quality notifications can be processed in this status or whether a deletion flag can be set. You can also specify whether a deletion flag is to be set automatically and whether the system should respond with a warning message or an error message when a deletion flag is set.
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 | SIMG_CFMENUOLQNOQNM3 | 0 | ALR0077563 O | |
| SIMG | SIMG_CFMENUOLQNOQNM3 | 1 | BIO0000031 O | |
| SIMG | SIMG_CFMENUOLQNOQNM3 | 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 |
| BSVS | L - Logical transport object | OIBS | OLQN | Maintain Status Profiles | ||
| V_TQ80_T | V - View | SM30 | 01 | Status Profile for Notification Type |
History
| Last changed by/on | SAP | 20020205 |
| SAP Release Created in | 110 |
