Hierarchy
ECC-DIMP (Software Component) DIMP⤷
IS-AD-LBK (Application Component) R/3 Log Book⤷
DIACL_GUI_AD (Package) Logbook: presentation layer (A&D)
IMG Activity
| ID | LGEOIBS | Define Status Profile |
| Transaction Code | S_ALI_97000038 | (empty) |
| Created on | 20040316 | |
| Customizing Attributes | LGEOIBS | Define Status Profile |
| Customizing Activity | LGEOIBS | Define Status Profile |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | LGEOIBS |
Use
This activity explains how to adapt general SAP status management to your requirements.
General information on status management
Managing the different statuses in the SAP system is based on one of the following:
- System status
- User status
System status
In a central table, the SAP system contains a basic store of statuses that are valid for and can be used by all applications. These statuses are maintained by SAP and cannot be changed. They are referred to as system statuses.
Business transactions
In a central table, the SAP system contains a basic store of business transactions that are valid for and can be used by all applications. These business transactions are maintained by SAP and cannot be changed.
Business transaction - system status
In a predefined, central table, the SAP system contains system status definitons for every business transaction and indicates whether the corresponding system status is deleted or set during the business transaction.
Objects - business transactions
Another table defines the business transactions that are allowed for each SAP object (order, equipment, and so on). This allocation is also predefined by SAP.
Result
The allocations listed above define which system statuses:
- Are the maximum possible for an object
- Can be set for the different individual business transactions
Status profile
You can define your status profiles in the IMG activity Define Status Profiles. Each status profile must be allocated to at least one object and must contain one or more allowed statuses. For each of these statuses, you can determine the system response in the business transactions that are predefined by SAP.
In the status profile you can:
- Define your statuses (user statuses) and document their function in a long text
- Determine the status numbers for user statuses that predefine the possible sequence for processing user statuses
- Define an initial status that is activated automatically when creating the object
- Determine which user status is automatically activated when carrying out a business transaction
- Define which operations are allowed (or prohibited) if a certain status is active
Status number
You can define a status number for every user status. The status number determines the sequence in which the user statuses can be activated. If you do not assign a status number to a user status, this number can always be set. At any one time, however, there can only be one user status with an active status number .
If you assign a status number to a user status, you must also specify a lowest and a highest status number. These numbers limit the status number interval from which the following user status can be chosen.
Example of equipment status
SAP supplies the following business transactions for equipment:
- Set deletion indicator (From release 3.0B)
- Cancel deletion indicator (From release 3.0B)
- Install equipment
- Dismantle equipment
When maintaining the status profile, for every status in the profile you can determine whether the equipment of this status can be installed or dismantled and whether a deletion indicator can be set. In status maintenance, you can also determine whether, for example, the deletion indicator is set automatically and whether the system should respond with a warning or an error message after the indicator is set.
Maintenance objects for which status profiles can be maintained:
- Equipment
- Functional locations
- Maintenance notifications
- Service notifications
- Maintenance orders
- Service orders
Notes
In the menu for equipment configuration, you can specify a status profile as a default value for each equipment category. For maintenance notifications, only a single status profile is allowed.
Actions
Define the user statuses for the individual maintenance objects.
Requirements
Standard settings
Activities
Example
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 | LGEOIBS | 0 | KA50002490 | R/3 Log Book |
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 | Define User Status Profile for Log Entries |
History
| Last changed by/on | SAP | 20040429 |
| SAP Release Created in | 500 |
