/SAPAPO/FCST - Message Class for Forecast
The following messages are stored in message class /SAPAPO/FCST: Message Class for Forecast.
It is part of development package /SAPAPO/MSDP in software component SCM-APO-SNP. This development package consists of objects that can be grouped under "Application Development Supply & Demand Planner".
It is part of development package /SAPAPO/MSDP in software component SCM-APO-SNP. This development package consists of objects that can be grouped under "Application Development Supply & Demand Planner".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Function obsolete |
| 001 | The following LIKE profile was used: &1 |
| 002 | The following phase-in profile was used: &1 |
| 003 | The following phase-out profile was used: &1 |
| 004 | Weighting group &1 from LIKE profile has no or little effect |
| 005 | Data check switched off |
| 006 | The data check switched on |
| 007 | The history horizon does not start on a workday |
| 008 | Forecast profile has been changed since the last forecast run |
| 009 | Characteristic for product &1 is not in the planning object structure |
| 010 | Using templates for lifecycle planning is prohibited |
| 011 | Conversion exit for the product characteristic is incompatible with PRODU |
| 012 | Output length of characteristic &1 is greater than 30 |
| 013 | The PRODU conversion exit is using leading zeros for output |
| 014 | You are not using conversion exit PRODU for the product characteristic |
| 015 | For detailed information, see consulting note #354660 |
| 016 | Errors have been found in your Customizing settings |
| 017 | There are warnings for your Customizing settings |
| 018 | The basic settings cannot be saved |
| 019 | The settings allow alphanumeric products only |
| 020 | The univariate forecast profile is currently locked |
| 021 | LIKE profile already used for another characteristic |
| 022 | Posting period is maintained incorrectly |
| 023 | Horizons in forecast profile are not valid |
| 024 | LIKE profile already exists, use another name |
| 025 | Phase-In/Out profile &1 does not exist |
| 026 | No reference objects defined in the LIKE profile |
| 027 | Phase-in/out profile &1 is already assigned, deletion not possible |
| 028 | &1 entries were deleted |
| 029 | Do you want to delete &1 entries? |
| 030 | Historical values changed by the promotion key figure |
| 031 | Minus values corrected to zero |
| 032 | Historical values selected by the promotion key figure |
| 033 | Enter a different key figure |
| 034 | Composite forecasting ignores single results with errors |
| 035 | Weighting factor for profile &1 adjusted to &2 |
| 036 | Different key figures or versions in history |
| 037 | Selection text is ambiguous; first possible selection used |
| 038 | Row totals cannot be calculated for more than 60 rows |
| 040 | Master profile used in activities, adjustment successful |
| 041 | Master profile used in activities, adjustment not possible |
| 042 | Single profile &1 is used in master profiles, deletion not possible |
| 044 | Property "Negative Allowed" must be identical for all key figures |
| 045 | Property "Zero Allowed" must be identical for all key figures |
| 046 | Negative values not allowed for key figure; Value set to zero |
| 047 | Previously calculated curve discarded, new curve being calculated |
| 048 | Do you want to adopt the auxiliary curve calculated? |
| 049 | Negative values are not allowed for the forecast key figure |
| 050 | &1 LIKE profiles deleted from database |
| 051 | Enter a name for the LIKE profile |
| 052 | Time series already assigned to another planning area |
| 053 | No time series exist without planning area assignment |
| 054 | Some entries are incomplete |
| 055 | There are no LIKE profiles without planning area assignment |
| 060 | Like profile &1 not used due to the offset that has been set |
| 061 | Aggregated lifecycle planning is active for like profiles |
| 062 | There is no basic setting for lifecycle planning |
| 063 | There is no like profile assignment |
| 064 | LIKE profile &1 for characteristic &2 used |
| 065 | Aggregation type of key figure &1 not suitable |
| 066 | Key figure &1 not in liveCache |
| 067 | Aggregated lifecycle planning is not active |
| 068 | Number of basic combinations processed is & |
| 069 | Number of like profiles processed is & |
| 070 | There are &1 like profile assignments for these basic combinations |
| 071 | There are &1 assignments of phase-in/out profiles |
| 072 | Combination &1 |
| 073 | Phase-in: &1 phase-out: &2 |
| 074 | Aggregated lifecycle planning is active for phase-in/out profiles |
| 075 | Phase-in/out profiles only affect past periods |
| 076 | Workdays cannot be corrected for aggregated phase-in/out |
| 078 | Aggregatd lifecycle planning cannot be executed for phase-in/out profiles |
| 079 | Key figure aggregation of &1 and &2 is different |
| 080 | You manually changed data after the forecast run |
| 081 | Forecast key figure is not initialized in the entire forecast horizon |
| 082 | Like profile: &1 |
| 083 | Maximum number of basic combinations to be processed is &1 |
| 084 | Maximum number of forecast periods to be processed is &1 |
| 085 | Aggregated lifecycle planning cannot be executed for like profiles |
| 087 | Display horizon should be smaller than or equal to the entire horizon |
| 088 | The start value is larger than or equal to the end value |
| 089 | Manual horizon of the trend curve has to contain the forecast horizon |
| 090 | Combination &1: No characteristic combination after Like replacement |
| 095 | Specify a start and end date for profile &1 |
| 096 | The start date for profile &1 is after the end date |
| 098 | Specify the key figure whose assignment you want to be considered |
| 099 | Forecast profile assignment is not unique |
| 100 | Select a suitable column |
| 101 | The number of periods cannot be reduced |
| 102 | You do not have authorization for &1 |
| 103 | No forecast profiles could be generated or assigned |
| 105 | The value entered does not correspond to the value of the preselection |
| 106 | Specify a value for the characteristic |
| 107 | Value entered does not correspond to the value of the filter that is set |
| 110 | Like profile: Number of combinations: &1; number of periods: &2 |
| 111 | Phase-in/out profiles: Number of combinations: &1; number of periods: &2 |
| 114 | Required Time for Forecast in Seconds: &1 |
| 115 | A single result cannot be adopted in the standard mode |
| 116 | The from-date of the history horizon is in the future |
| 117 | The to-date of the forecast horizon is in the past |
| 118 | The from-date of the forecast horizon must be checked |
| 119 | The to-date of the history horizon must be checked |
| 120 | &1 generated profiles and &2 assignments found |
| 121 | Profile generation is only supported by strategy 56 |
| 122 | Forecast profile &1 was generated and assigned using strategy &2 |
| 123 | Error measure too large, new forecast profile generated |
| 130 | The indicator cannot be set for this selection |
| 131 | Some objects were locked, locked objects were excluded |
| 140 | Select exactly &1 column(s) |
| 150 | MLR executed successfully |
| 151 | Not enough data to execute MLR forecasting using POS data |
| 152 | Internal error during MLR forecasting using POS data |
| 153 | MAPE for MLR forecasting using POS: &1 |
| 154 | MAPE for statistical forecasting: &1 |
| 155 | MAPE for MLR forecasting using POS bigger than MAPE for stat. forecast |
| 156 | Fill all mandatory fields |
| 157 | MLR forecasting using POS data executed successfully |
| 158 | Lifecyle Planning was activated for this MLR profile |
| 200 | Length Variation was adjusted |
| 250 | Calculation of forecast error MSE terminated due to field overflow |
| 255 | Arithmetic Overflow - value lies outside the permitted range |
| 256 | Conversion Overflow - value lies outside the permitted range |
| 300 | &1: MAD &2 ; FSUMM &3 ; MAPE &4 |
| 301 | &1: MPE &2 ; RMSE &3 ; USER &4 |