Hierarchy
⤷
⤷
Basic Data
| Data Element | SAUSNA |
| Short Description | Exception message bar |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | TEXT30 | |
| Data Type | CHAR | Character String |
| Length | 30 | |
| Decimal Places | 0 | |
| Output Length | 30 | |
| 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 | Exception |
| Medium | 15 | Exceptions |
| Long | 20 | Exceptions |
| Heading | 30 | Exception messages |
Documentation
Definition
The exception messages have the following meanings:
K No historical values exist.
I There are too few historical values for an initialization.
L There are too few historical values for the initialization of the
"weighted sliding mean value" forecast model.
P The system has not executed an ex-post forecast.
W The system has reset the count of ex-post forecast values
because there are too few historical values for an initialization.
N The basic value is zero.
U The historical values are instable.
F The quotient of the mean forecast error and the mean absolute
deviation exceeded the tracking limit. Check the chosen forecast
model.
G A seasonal index with value zero has occurred in a seasonal model.
S The basic value is zero in a seasonal model.
E The forecast value is less than zero.
M The forecast value is greater than the maximum value.
Z There are too few historical values for a parameter optimization
O The system could not select a forecast model because there are too
few historical values.
D The system chose the constant model because
there are too few historical values.
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in |