Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-BMT-OM (Application Component) Organizational Management⤷
SP00 (Package) Organization and Planning
Basic Data
| Data Element | PRIOX |
| Short Description | Priority |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR2 | |
| Data Type | CHAR | Character String |
| Length | 2 | |
| Decimal Places | 0 | |
| Output Length | 2 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | PRIOX | |
| 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 | 33 | Priority |
| Heading | 2 | Pr |
Documentation
Use
Sequence Priority of Objects
The Priority field is optional. It is used to determine the sequence in which objects are presented in Simple Maintenance and Structural Graphics.
When multiple objects are located on the same hierarchical level of a structure, these must be ordered in a specific sequence from left to right (or from top to bottom).
This is done by assigning alphanumeric priority values, where the value 1 is the highest (far left or top) and 99 the lowest priority (far right or bottom).
If you specify no priority, the system places objects according to their object IDs.
Priority When Defining Evaluation Paths
It is only necessary to prioritize evaluation paths as an exception. Generally, you should use '*', so that all relationships are read.
Use the Priority field to define evaluation paths if you want only objects which are assigned a certain priority (see above) to be considered in an evaluation path.
Note
You can find more information on the meaning of the priority field with reference to evaluation paths in the online IMG documentation for 'Maintain evaluation paths'.
Priority for Responsibilities
If you are using responsibilities for role resolution in Workflow, you can provide individual responsibilities with priorities.
Example: There are various responsibilities for a standard role for processing orders, grouped, for example according to order value (one responsibility for orders up to a certain value, another for orders with a greater order value).
Assuming that orders for a particular customer are always to be processed with the same responsibility (and therefore by the same agent), you can access it via another responsibility with a higher priority that contains the customer name as the only criterion. The responsibility (-ies) with lower priority, and therefore the order value, is then no longer taken into account during agent determination.
Use only numeric values here, and note that, logically, the responsibility with the highest numberic value in this field has the highest priority.
Procedure
- Sequence Priority of Objects
In Create mode, assign a priority to the objects you wish to rank.
To do so, assign an alphanumeric value (1, 2, 3... or A, B, C...) to each object.
In Change mode, overwrite the value in the field.
- Priority When Defining Evaluation Paths
In the Priority field, enter the priority or priorities for objects that should be considered in evaluation paths. Enter "*" if you want to have no restriction.
- Priority for Responsibilities
Maintain the priority directly in the detail screen for the responsibility or in the overview screen for the responsibilities for the rule. Note that you must use numeric values here. On the overview screen, the system sorts the responsibilities in descending order of priority.
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 | 20041216 |
| SAP Release Created in |
