/SAPAPO/OUTLDET - Message Class for Outlier Detection
The following messages are stored in message class /SAPAPO/OUTLDET: Message Class for Outlier Detection.
It is part of development package /SAPAPO/DP_EVENTS in software component SCM-APO-FCS. This development package consists of objects that can be grouped under "Event Management & Outlier Detection".
It is part of development package /SAPAPO/DP_EVENTS in software component SCM-APO-FCS. This development package consists of objects that can be grouped under "Event Management & Outlier Detection".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Planning area parameter is missing |
| 001 | Planning area &1 does not exist |
| 002 | The selection ID you provided for planning area &1 does not exist |
| 003 | Planning area &1 is not assigned |
| 004 | Only one type of selection can be used |
| 005 | The outlier detection profile &1 is not valid or incomplete |
| 006 | Provide the history key figure |
| 007 | Provide the event and promotion key figures |
| 008 | Planning level &1 was not found for planning area &2 |
| 009 | Planning level &1 in planning area &2 is empty |
| 010 | Event created with type &1 (&2 period(s) long, with startdate &3, ID &4) |
| 011 | Event with event type &1 has been created (ID: &2) |
| 012 | Processing completed |
| 013 | Error creating event with type &1 (&2 period(s) long, with startdate &3) |
| 014 | Selection on planning area &1 is locked |
| 015 | The to and from dates have been adjusted to match the period boundaries |
| 016 | Specify both to and from dates and the periodicity |
| 017 | Effects of existing events and promotions are removed during detection |
| 018 | Previous automatically estimated events were deleted |
| 019 | Corrected history was saved into key figure &1 |
| 020 | Fill all required fields |
| 021 | Specify either the lower or upper values (or both) |
| 022 | Provide the event type field |
| 023 | The upper limit value must be higher than the lower limit |
| 024 | There can only be one entry that has an infinite lower limit |
| 025 | There can only be one entry that has an infinite upper limit |
| 026 | The limit interval specified overlaps with an already specified interval |
| 027 | No event key figure exists for planning area &1 |
| 028 | Specify corrected history key figure |
| 029 | No forecast profile assigned to selection (see details for selection) |
| 030 | The system does not consider the number of historical events |
| 031 | Exp. weight factor is only used for exponentially weighted calculation |
| 032 | Error reading event catalog &1 |
| 033 | Generic event type &1 not included in event catalog &2 |
| 034 | Assign also the generic event types to the used event catalog |
| 035 | Event catalog parameter is not specified |
| 036 | Planning version &1 does not exist for planning area &2 |
| 037 | No event catalog is specified in forecast profile for combination |
| 038 | The system does not consider existing events |
| 039 | Detection horizon end date &1 lies in the future, processing not possible |
| 040 | Outlier detection is executed on selection &1 |
| 041 | Detection horizon is from &1 to &2 (periodicity &3) |
| 042 | Outlier detection profile &1 is selected |
| 043 | Event catalog &1 is selected |
| 044 | Planning level &1 is used for the detection process |
| 045 | Planning area &1, version &2 is selected |
| 046 | Planning level not specified for planning area in Customizing |
| 047 | You have not maintained an event key figure for the planning area |
| 048 | History (with kf. &1) for combination is empty; combination is skipped |
| 049 | Event type &1 that has different periodicity than &2 is not considered |
| 050 | Event impact for event with startdate &1, type &2 was reestimated |
| 051 | An existing selection or a newly created selection must be provided |
| 052 | The event date parameter must be provided |
| 053 | Price hist. (with k.f. &1) for comb. is empty; no price change processing |
| 054 | Forecast was triggered with profile &1 |
| 055 | Planning level is not specified |
| 056 | The period before or period after value is not specified |
| 057 | The planning area field is not maintained |
| 058 | The periodicity field is not maintained |
| 059 | Event type &1 in outlier detection profile &2 has incorrect periodicity |
| 060 | The specified event type &1 does not exist |
| 061 | The specified period contains existing events; no new events are created |
| 062 | End date of the event to be created falls outside the history horizon |
| 063 | Selected date lies outside the planning horizon defined in fcst. profile |
| 064 | Selected date lies outside the history horizon defined in fcst. profile |
| 070 | Specify either the number of hist. periods or indicate using all periods |
| 071 | Maintain the weight factor for the exponentially weighted calc. method |
| 072 | Select a calculation method |
| 073 | Event type &1 startdate &2 could not been re-estimated properly. |
| 074 | Specify a valid outlier detection profile |
| 090 | Error in event creation during event processing |
| 091 | Error in event locking during event activation |
| 092 | Error in event saving during event activation |
| 100 | Outlier detection profile &1 not found |
| 101 | Outlier detection decision table is missing for profile &1 |
| 102 | Error while reading historical data for outlier detection |
| 103 | Error while cleaning historical data for past events and promotions |
| 104 | Error in creating events |
| 105 | Error while saving corrected history into liveCache |
| 106 | Error while locking data for selection |
| 107 | Error while reading period before and after for &1, periodicity &2 |
| 108 | The selected period lies outside the (non-zero) history horizon |
| 109 | Event to be created would start earlier than history horizon |
| 110 | Error when deleting events |
| 111 | Number of deleted events: &1 |
| 112 | Event type &1 determined by the BADI implementation is invalid |
| 113 | |
| 120 | Could not clean the history from impact of past evts |
| 121 | No evt. cat. specified in profile, no cleaning |
| 130 | Business function not turned on. You are not allowed to run this program |
| 150 | No MLR profile specified in univ. profile &1; price changes not detected |
| 151 | Input periodicity does not match master forecast profile (&1) periodicity |
| 152 | Error when reading MLR forecast profile &1 |
| 153 | Price key figure &1 is not in MLR profile &2; price changes not detected |
| 154 | Error when reading price change event type &1 |
| 155 | Input periodicity does not match price change event type periodicity &1 |
| 156 | Price change event with type &1, start date &2 and ID &3 created |
| 157 | Error when creating price change event (type &1, start date &2) |
| 158 | Values of price change event with start date &1 (prev. ID &2) reestimated |
| 159 | Error when running MLR calculation; price changes not detected |
| 160 | Periodicity &1 is not supported |
| 161 | Periodicity &1 is not valid for planning area &2 |
| 162 | MLR t-test negative for price; price changes not detected |
| 170 | Specified history keyfigure &1 is not valid |
| 200 | Specify the event type to be deleted |
| 201 | Cannot create price change events using "Mass Creation of Events" |
| 202 | Program can not be run in batch mode |
| 203 | No existing event types found for selection |
| 204 | Report running in simulation mode, no event types were deleted |
| 205 | No existing events found for selection |
| 210 | Cannot read price key figure from forecast settings |