Hierarchy
⤷ PLM-RM (Application Component) Recipe Management
⤷ RMXTTLS (Package) Main Package - Trial: Tools
Basic Data
Data Element | RMXTE_ESTAT |
Short Description | User Status |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | J_ESTAT | |
Data Type | CHAR | Character String |
Length | 5 | |
Decimal Places | 0 | |
Output Length | 5 | |
Value Table | TJ30 |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | UserStatus |
Medium | 15 | User Status |
Long | 20 | User Status |
Heading | 14 | User Status |
Documentation
Definition
You can assign a user status to a trial monitor task. The trial monitor sets the user status in general status management once the task has been executed successfully.
Use
Instead of a user status, the tasks provided by SAP use a system status that is programmed in the task and that cannot be changed.
The user status is intended for assignment to customer-specific tasks, which enables you to extend the system statuses provided (that cannot be changed).
SAP provides the generic task class CL_RMXT_TASK_ESTAT which you can use for tasks. When this task is executed, it sets a user status. It does not contain any additional logic.
If you want the task to contain additional logic, you have to implement a separate task class.
Even if you do not want the monitor to set the user status automatically after the task has been executed, leave the user status in Customizing blank and set the user status in the task itself (if you want to set one user status and reset a different one, for example).
Dependencies
Example
History
Last changed by/on | SAP | 20031212 |
SAP Release Created in | 471 |