Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM-BTX-BF-XIF (Application Component) External Interface Business Transaction⤷
CRMEDI_ORDER_R3 (Package) Data Objects for Order Idocs from R/3
Basic Data
| Data Element | PRI |
| Short Description | Order Priority |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | PRI | |
| Data Type | CHAR | Character String |
| Length | 3 | |
| Decimal Places | 0 | |
| Output Length | 3 | |
| Value Table |
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 | Priority |
| Medium | 20 | Order priority |
| Long | 22 | Order priority |
| Heading | 22 | Order priority |
Supplementary Documentation - PRIMARY 0001
Use
In this field, you can define the report function. The two parameter values are:
- FROM: The report checks all selected modules (generic entry possible) for references. These references are written to the XRef index.
- TO: If this parameter is set to TO, you must specify a module (generic entry only possible for FROM). The report then searches only for those references which point to the specified module and enters these in the XRef index.
Procedure
Examples
Dependencies
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
Supplementary Documentation - PRIOX 0001
Use
When qualifications are related with jobs, positions or work centers as requirements, the priority indicates the importance of the requirement concerned. The priority indicates to what extent a person should meet the requirement in order to fulfil the tasks of the job, position or work center.
The requirement priority is included in the calculation of the suitability percentage, in which the requirements of a job (position or a work center) are compared to the person's qualifications. Greater consideration is given to high priority requirements (e.g. '1').
Examples
0 --> Unvalued requirement priority (= initial value).
1 --> Very important requirement (essential requirement that must be
fulfilled).
... --> Scale of requirement priorities ranging from important to
not so important.
9 --> Not so important requirement.
Supplementary Documentation - PRIOX 0002
Priority for order of budget structure elements
This field enables you to determine the order in which budget structure elements are displayed.
If more than one budget structure element is displayed on the same level of a hierarchical structure, they must be arranged in descending order according to priority.
To do this, you assign alphanumeric priority values where 1 or A is the highest priority (at the top) and 99 or Z is the lowest priority (at the bottom).
If you do not assign priorities to the budget structure elements, the system puts the budget structure elements in the order of their object IDs.
Procedure
- Create mode
This field enables you to assign a priority to the budget structure elements that you want to put in order. Enter an alphanumeric value (1, 2, 3... or A, B, C...) for each budget structure element.
- Change mode
Change mode enables you to overwrite existing values.
Examples
The following budget structure is displayed:
BU 50002 - Personnel expenses (= root object)
|
|BU 50010 - Civil servants )
|BU 50012 - Salaried employees )= subordinate BS elements
|BU 50015 - Hourly paid )
However, you want the budget structure elements to be displayed below the root object in the following order:
1. Hourly paid
2. Civil servants
3. Salaried employees
Therefore, you assign the following priorities to the budget structure elements:
BS element Priority
BU 50010 - Civil servants 2
BU 50012 - Salaried employees 3
BU 50015 - Hourly paid 1
After you have saved the priorities, the budget structure elements are displayed in the order you require.
Dependencies
History
| Last changed by/on | SAP | 20020829 |
| SAP Release Created in |
