Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM-MSE (Application Component) Mobile Service⤷
IWOC (Package) Application Development R/3 Work Order Cycle
Basic Data
| Data Element | PRIOK |
| Short Description | Priority |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | PRIOK | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table | T356 |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | PRIORITY | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Priority |
| Medium | 15 | Priority |
| Long | 20 | Priority |
| Heading | 1 | P |
Documentation
Definition
The key in this field indicates the importance of the processing of the order/notification.
Supplementary Documentation - PRIOK 0001
Dependencies
If you enter a key for the priority in this field, the system completes the fields desired start and desired end automatically.
Supplementary Documentation - PRIOK 0002
Use
The priority will be copied to the notification or order during scheduling.
Dependencies
The maintenance call object notification has the following particular feature:
Values are first available for the priority if you have specified a notification type in the maintenance item.
Example
Supplementary Documentation - PRIOK 9999
Use
Very high
A notification with priority "very high" is justified if normal business process flows are severely restricted or damaged. Tasks requiring immediate performance cannot be performed. This is caused by a complete system shutdown or by the malfunction of central functions of the productive SAP system.
The notification must be processed immediately as otherwise the malfunction can lead to considerable losses.
High
A notification with priority "high" is justified if normal business process flows are restricted or damaged. Necessary tasks cannot be performed. This is caused by faulty or failed functionality in the SAP system that is urgently required in the current situation.
The notification must be processed as soon as possible as the continuing malfunction can lead to a serious malfunction in the entire productive business process flows.
Medium
A notification with priority "medium" is justified if normal business process flows are restricted or damaged to a certain degree. This is caused by faulty or failed system functionality.
Low
A notification with priority "low" is justified if normal business process flows are either only slightly resticted or damaged or not at all. This is caused by faulty or failed system functionality in the SAP system that is not required on a daily basis or is little used.
Classification of test systems
As a general rule, the same problems in test systems have a priority one lower than in productive systems.
Procedure
Examples
Dependencies
History
| Last changed by/on | SAP | 19991102 |
| SAP Release Created in |
