Hierarchy
⤷
⤷
Basic Data
| Data Element | AUSNA |
| 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 mean the following:
K No historical values exist.
I Not enough historical values for an initialization.
L Not enough historical values exist to be able to initialize the forecast model "Weighted moving average".
P The system has not carried out an ex-post forecast.
W The system has reset the number of ex-post
forecast values because there are not enough
historical values for an initialization.
N The basic value is zero.
U The historical values are not constant.
F The mean forecast error to mean absolute
deviation ratio has exceeded the tracking signal.
Please check the chosen forecast model.
G A seasonal index with the value zero has
ocurred in a seasonal model.
S The basic value in a seasonal model is zero.
E The forecast value is less than zero.
M The forecast value is greater than the maximum
value.
Z There are not enough historical values to be able to optimize
the parameters.
O The system could not choose a forecast model,
because there are not enough historical values.
D The system has chosen the constant model
because there are not enough historical values.
History
| Last changed by/on | SAP | 19950302 |
| SAP Release Created in |