SAP ABAP Data Element LSO_T77S0_MAXMU (Maximum Priority for Essential Booking)
Hierarchy
☛
EA-HRGXX (Software Component) Sub component EA-HRGXX of EA-HR
⤷ PE-LSO-TM (Application Component) Training Management
⤷ LSO_TM_ND (Package) SAP Learning Solution - Core New Developments
⤷ PE-LSO-TM (Application Component) Training Management
⤷ LSO_TM_ND (Package) SAP Learning Solution - Core New Developments
Basic Data
Data Element | LSO_T77S0_MAXMU |
Short Description | Maximum Priority for Essential Booking |
Data Type
Category of Dictionary Type | Direct Type Entry | |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | ||
Data Type | NUMC | Character string with only digits |
Length | 2 | |
Decimal Places | 0 | |
Output Length | 2 | |
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 | 0 | |
Medium | 0 | |
Long | 40 | Maximum Priority for Essential Booking |
Heading | 40 | Maximum Priority for Essential Booking |
Documentation
Definition
Maximum Priority for Essential Bookings
Use
This switch defines the value in the range 00 to 99 as of which a booking is regarded as an essential booking and assigned essential booking priority.
Example
MAXMU = 09 => Only bookings with priority 09 are
considered essential bookings
In the SAP standard system, the value for an essential booking is set at 09.
If you change this value, you must ensure that the equation MAXMU < NPRIO < INPRI < MINWL (e.g. 09 < 50 < 55 < 90 ) is retained!
Note
You should specify this value one time only when you configure the system. Changing the value can result in inconsistencies during capacity checks for courses.
History
Last changed by/on | SAP | 20031212 |
SAP Release Created in | 300 |