Hierarchy
⤷ IS-U (Application Component) SAP Utilities
⤷ EE80 (Package) IS-U: Customizing
IMG Activity
ID | _ISUEDMBS_000023 | Define User Status |
Transaction Code | S_KK4_82000975 | (empty) |
Created on | 20020927 | |
Customizing Attributes | _ISUEDMBS_000023 | Define User Status |
Customizing Activity | _ISUEDMBS_000023 | Define User Status |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | _ISUEDMBS_000023 |
This IMG activity describes how you adapt the SAP status management to meet your own requirements.
General Information on Status Management
The SAP system differentiates between the following statuses in status management:
System Status
The SAP system contains a central table of statuses that are valid for, and can by used by, all applications.
These statuses are maintained by SAP and cannot be changed. They are called system statuses.
Business Transactions
The SAP system contains another central table of business transactionsthat are valid for, and can by used by, all applications.
These business transactions are maintained by SAP and cannot be changed.
Business Transaction - System Status
In another central table, also predefined by SAP, a system status is allocated to every business transaction and it is determined whether thecorresponding system status is deleted or set during the transaction.
Objects - Business Transactions
Another table defines which business transactions are permitted for which SAP objects (order, EDM profile, EDM profile values). This allocation is also predetermined by SAP.
Result
The above allocations result in:
- Which system statuses can be used for an object
- Which system statuses are set for the individual transactions
Status Profile
In the Define Status Profile activity, you can create your own status profiles. You must allocate at least one object (equipment, technicallocation, for example) to each status profile.
Every status profile contains one or more permissible statuses.
For each of these statuses you can determine the system response within the limits of the business transactions predefined by SAP.
In the status profile you:
- Define your own statuses (user status) and document their functions in a corresponding long text
- Determine status numbers to define the possible order of user statuses
- Define an initial status, which is automatically activated when you create the object.
- Determine which user status is automatically activated whenyou execute a business transaction
- Define which transactions are permitted or forbidden if a certain status is active.
Status Number
You can define a status number for every user status.
The status number determines the order in which the user statuses can be activated.
If you do not allocate a status number to the user status, it can be used at any time. However, only one user status with a status number may be active at any time.
If you do allocate a status number to a user status, you also have to specify a lowest and a highest status number for that status. Thesenumbers restrict the status number interval from which the ensuinguser status can be selected.
Notes
There are a number of restrictions regarding the status profile for EDM profile values. This implies that the user status for EDM profile values really only serves as additional information. It is possible for theuser status to have more controlling characteristics, however, only to a certain degree:
- Only one status profile can be actively allocated for EDM profile values
- If an initial status is specified, it is ignored
- During profile value import and the interpolation/extrapolationof profile values, the user status is not set by means of atransaction but directly by the application.
- This keeps the number of transactions small and the application flexible.
- Before profile value import and interpolation/extrapolationof profile values, the customer must mark the user statuses fordeletion in the status profile.
Activities
Define your user status for EDM profile values.
Business Attributes
ASAP Roadmap ID | 203 | Establish Master Data |
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 | _ISUEDMBS_000023 | 0 | I500000200 | Energy Data 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 | OIBS | OLI0 | Define User Status |
History
Last changed by/on | SAP | 20020927 |
SAP Release Created in | 471 |