SAP ABAP Message Class WXP (Retail Planning)
Basic Data
Hierarchy
☛
SAP_APPL (Software Component) Logistics and Accounting
⤷ LO-MAP (Application Component) Merchandise and Assortment Planning
⤷ WIS_PLAN (Package) Retail: Planning
⤷ LO-MAP (Application Component) Merchandise and Assortment Planning
⤷ WIS_PLAN (Package) Retail: Planning
Attributes
Message class | WXP | |
Short Description | Retail Planning | |
Changed On | 19990219 | |
Last Changed At | 151527 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 000 | *** Messages for manual planning | Space: object requires documentation | |
2 | 001 | Not all plan data could be locked (see log) | Space: object requires documentation | |
3 | 002 | No entry exists in the planning hierarchy for your selection criteria | Space: object requires documentation | |
4 | 003 | Error no. & occured during verification with the planning hierarchy | Space: object requires documentation | |
5 | 004 | Step &2 of planning layout &3 is not defined in scenario &1 | Space: object requires documentation | |
6 | 005 | Plng layout &1 is not assigned to plng step &3 in plng scenario &2 | Space: object requires documentation | |
7 | 006 | Now activate planning scenario &1 | Space: object requires documentation | |
8 | 007 | The planning hierarchy version must be clear | Space: object requires documentation | |
9 | 008 | Manual planning variant number & is not defined | Space: object requires documentation | |
10 | 009 | Plan version & was not assigned to a planning hierarchy version | Space: object requires documentation | |
11 | 010 | Planning step & is not defined for manual planning | Space: object requires documentation | |
12 | 011 | Divide by zero when calculating the formula for key figure & | Space: object requires documentation | |
13 | 012 | Errors occurred in the key figure formula type "during selection" | Space: object requires documentation | |
14 | 013 | Plan version &2 is not defined in layout &1 | Space: object requires documentation | |
15 | 014 | No plan version is defined for intervals &2 - &3 in layout &1 | Space: object requires documentation | |
16 | 015 | Errors occurred in the key figure formula type "after input" | Space: object requires documentation | |
17 | 016 | Error occurred during master data checks (see log) | Space: object requires documentation | |
18 | 017 | No errors have yet occurred during master data checks | Space: object requires documentation | |
19 | 018 | You do not have change authorization for planning in version & | Space: object requires documentation | |
20 | 019 | Incorrect authorization may exist in the user master | Space: object requires documentation | |
21 | 020 | No display authorization for planning in version & | Space: object requires documentation | |
22 | 021 | No authorization for planning in version & | Space: object requires documentation | |
23 | 022 | Determine an exchange rate type for plan version & | Space: object requires documentation | |
24 | 023 | Save function is not possible as user warnings still exist | Space: object requires documentation | |
25 | 024 | No planning-specific warnings exist | Space: object requires documentation | |
26 | 025 | Column value &1 for characteristic &2 not defined in planning hierarchy | Space: object requires documentation | |
27 | 026 | Column value &1 for characteristic &2 is not defined | Space: object requires documentation | |
28 | 027 | Plan data updated successfully | Space: object requires documentation | |
29 | 028 | The combination of season year/fiscal year &/& is not defined | Space: object requires documentation | |
30 | 029 | The combination of season type/fiscal year is not defined | Space: object requires documentation | |
31 | 030 | The combination of season type/year/fiscal year &/&/& is not defined | Space: object requires documentation | |
32 | 031 | No database lock errors have occurred yet | Space: object requires documentation | |
33 | 032 | IS/version/combination &1 locked by user &2 | Space: object requires documentation | |
34 | 033 | Plan version &1 is not assigned to planning step &2/&3 | Space: object requires documentation | |
35 | 034 | Function code &1 cannot be defined | Space: object requires documentation | |
36 | 035 | Enter a planning scenario | Space: object requires documentation | |
37 | 036 | Enter a planning layout | Space: object requires documentation | |
38 | 037 | Planning layout &1 successfully deleted | Space: object requires documentation | |
39 | 038 | Planning layout not deleted successfully | Space: object requires documentation | |
40 | 039 | Period cat. for reference layout &1 deviates from the desired period cat. | Space: object requires documentation | |
41 | 040 | Maintain a fiscal year variant for calendar months | Space: object requires documentation | |
42 | 041 | Maintain a fiscal year variant for calendar weeks | Space: object requires documentation | |
43 | 042 | Enter a planning step | Space: object requires documentation | |
44 | 043 | Planning step &2 is not defined for planning scenario &1 | Space: object requires documentation | |
45 | 044 | No documents are defined for planning step &1 | Space: object requires documentation | |
46 | 045 | Incorrect parameters when calling Business Document Service | Space: object requires documentation | |
47 | 046 | No authorization to execute Business Document Service | Space: object requires documentation | |
48 | 047 | Fatal error in the Knowledge Provider | Space: object requires documentation | |
49 | 048 | Internal error in the Business Document Service | Space: object requires documentation | |
50 | 049 | Planning step &1 is not defined for manual planning | Space: object requires documentation | |
51 | 050 | Define plan versions for every version you use | Space: object requires documentation | |
52 | 051 | Some quantity key figures are not ready for input | Space: object requires documentation | |
53 | 052 | Messages exist (see log) | Space: object requires documentation | |
54 | 053 | No errors occurred when checking interfaces | Space: object requires documentation | |
55 | 054 | Period &1 not maintained for fiscal year variant/fiscal year &2/&3 | Space: object requires documentation | |
56 | 055 | Missing declaration for database table &1 | Space: object requires documentation | |
57 | 056 | Too many temporary programs generated | Space: object requires documentation | |
58 | 057 | Character. value &2 is not defined for characteristic &1 in the hierarchy | Space: object requires documentation | |
59 | 058 | Characteristic value &1 is not supported for characteristic &2 | Space: object requires documentation | |
60 | 059 | Attribute &1 does not have a numerical value (&2-&3, &4) | Space: object requires documentation | |
61 | 060 | Attribute &3 for characteristic &2 does not exist | Space: object requires documentation | |
62 | 061 | Attribute &3 has inconsistent properties | Space: object requires documentation | |
63 | 080 | Planning scenario does not contain planning characteristic &1 | Space: object requires documentation | |
64 | 081 | Character. &2 cannot be used as "Classification System Characteristic &1" | Space: object requires documentation | |
65 | 082 | Classification system character. &3 for planning character. &2 is invalid | Space: object requires documentation | |
66 | 083 | Planning characteristic &3 is not a planning level for planning step &1 | Space: object requires documentation | |
67 | 084 | Characteristic "Article" is missing and article planning is not possible | Space: object requires documentation | |
68 | 085 | Article characteristic &3 is not a planning level for planning step &1 | Space: object requires documentation | |
69 | 086 | Classification system characteristic &3 belongs to type &4, not CHAR | Space: object requires documentation | |
70 | 087 | No characteristic can be entered for characteristic planning in layout &2 | Space: object requires documentation | |
71 | 088 | Planning characteristic &3 is not intended for characteristic planning | Space: object requires documentation | |
72 | 089 | Classification system characteristic &3 has the wrong value check method | Space: object requires documentation | |
73 | 090 | Characteristic &3 should not be used for article planning in layout &2 | Space: object requires documentation | |
74 | 100 | *** Messages for network dialogs | Space: object requires documentation | |
75 | 101 | Operating system is not defined for OCX control standard | Space: object requires documentation | |
76 | 102 | Action cannot be executed in the present processing mode '&1/&2' | Space: object requires documentation | |
77 | 103 | Maintenance is not possible in planning hierarchy for planning step &1 | Space: object requires documentation | |
78 | 104 | Select a planning step | Space: object requires documentation | |
79 | 105 | Planning scenario &1 has already been created | Space: object requires documentation | |
80 | 106 | Planning scenario &1 has not yet been created | Space: object requires documentation | |
81 | 107 | Changes have been saved | Space: object requires documentation | |
82 | 108 | Planning step &1 already exists. Select a different name | Space: object requires documentation | |
83 | 109 | The selected objects have been flagged for deletion | Space: object requires documentation | |
84 | 110 | A planning step cannot be linked to itself | Space: object requires documentation | |
85 | 111 | Caution: planning scenario &1 is not yet activated | Space: object requires documentation | |
86 | 112 | Planning scenario &1 is already active | Space: object requires documentation | |
87 | 113 | SAP link programs have not yet been generated | Space: object requires documentation | |
88 | 114 | SAP link programs have not yet been generated | Space: object requires documentation | |
89 | 115 | Enter a program name | Space: object requires documentation | |
90 | 116 | Link was executed | Space: object requires documentation | |
91 | 117 | Mark a line in the list | Space: object requires documentation | |
92 | 118 | Entry &1 has been flagged for deletion | Space: object requires documentation | |
93 | 119 | Planning step &1 is still flagged for deletion | Space: object requires documentation | |
94 | 120 | &1 entries have been restored | Space: object requires documentation | |
95 | 121 | SAP planning programs have not been generated yet | Space: object requires documentation | |
96 | 122 | Automatic planning was executed | Space: object requires documentation | |
97 | 123 | Select "Manual planning" or "Program/Transaction" | Space: object requires documentation | |
98 | 124 | Planning scenario &1 does not have active / saved status | Space: object requires documentation | |
99 | 125 | Entry &1 already exists. Select a different name | Space: object requires documentation | |
100 | 126 | The planing scenario cannot be saved with this structure | Space: object requires documentation | |
101 | 127 | Entry &1 has been moved to the clipboard | Space: object requires documentation | |
102 | 128 | Entry &1 was used from the temporary storage | Space: object requires documentation | |
103 | 129 | Entry &1 already exists | Space: object requires documentation | |
104 | 130 | Entry &1 was transferred | Space: object requires documentation | |
105 | 131 | Formula group &1 has not yet been created for planning step &2 | Space: object requires documentation | |
106 | 132 | Assign characteristics to planning step &1 | Space: object requires documentation | |
107 | 133 | Hierarchy tables have not yet been generated | Space: object requires documentation | |
108 | 134 | Entry &1 is neither a program nor a transaction | Space: object requires documentation | |
109 | 135 | Save and activate planning scenario &1 | Space: object requires documentation | |
110 | 136 | The planning scenario contains provisional objects | Space: object requires documentation | |
111 | 137 | The name for planning scenario &1 is not within the allowed name range | Space: object requires documentation | |
112 | 138 | Caution: name &1 is in the customer name range | Space: object requires documentation | |
113 | 139 | Delete all planning steps and links | Space: object requires documentation | |
114 | 140 | Hierarchy table for plng step /char./hier. version &1/&2/&3 contains data | Space: object requires documentation | |
115 | 141 | Hierarchy table &2 for plan scenario &1 still exists | Space: object requires documentation | |
116 | 142 | &1 entries have been marked for deletion | Space: object requires documentation | |
117 | 143 | Select a description without blank characters | Space: object requires documentation | |
118 | 144 | Hierarchy table &1 could not be deleted | Space: object requires documentation | |
119 | 145 | Hierarchy table &1 still contains data | Space: object requires documentation | |
120 | 146 | User &2 has no authorization for planning scenario &1 | Space: object requires documentation | |
121 | 147 | Incorrect authorization in the user master for user &1 | Space: object requires documentation | |
122 | 148 | User &2 has no authorization for planning step &1 | Space: object requires documentation | |
123 | 149 | Choose a description without special characters | Space: object requires documentation | |
124 | 150 | No planning hierarchy can be maintained for planning step &1 | Space: object requires documentation | |
125 | 151 | User &1 is entering planning scenario &2 | Space: object requires documentation | |
126 | 152 | Data still exists for plan version &1 in planning step &2 | Space: object requires documentation | |
127 | 153 | Error occurred when transporting the planning scenario | Space: object requires documentation | |
128 | 154 | Entry &1 was moved | Space: object requires documentation | |
129 | 155 | Event generated | Space: object requires documentation | |
130 | 156 | Select one line only in the list | Space: object requires documentation | |
131 | 157 | Select at least one line in the list | Space: object requires documentation | |
132 | 158 | &1&2&3&4 | Space: object requires documentation | |
133 | 159 | Assignment &1 <-> &2 was deleted | Space: object requires documentation | |
134 | 160 | Select one line in both lists | Space: object requires documentation | |
135 | 161 | Field & has not yet been assigned to an infocube field | Space: object requires documentation | |
136 | 162 | The list of the planning scenario fields used was updated | Space: object requires documentation | |
137 | 163 | Enter the RFC destination for the BW system | Space: object requires documentation | |
138 | 164 | Length of characteristic name exceeds the allowed length of & characters | Space: object requires documentation | |
139 | 165 | Infocube field &2 is already assigned to scenario field &1 | Space: object requires documentation | |
140 | 166 | Infocube &2 does not contain version field &1 | Space: object requires documentation | |
141 | 167 | Cube field &1 is already assigned to scenario field &2 | Space: object requires documentation | |
142 | 168 | Fields &1 and &2 have different field types | Space: object requires documentation | |
143 | 169 | Infocube &1 does not contain the field for fiscal year variants | Space: object requires documentation | |
144 | 170 | The user settings were saved | Space: object requires documentation | |
145 | 171 | No connection to the BW system | Space: object requires documentation | |
146 | 172 | Data has already been saved | Space: object requires documentation | |
147 | 173 | Info structure &1 was deleted | Space: object requires documentation | |
148 | 174 | No changes were made | Space: object requires documentation | |
149 | 175 | Data was changed. Save before exiting | Space: object requires documentation | |
150 | 176 | The link method must be reset | Space: object requires documentation | |
151 | 177 | Planning steps &1 and &2 have no common key figure | Space: object requires documentation | |
152 | 178 | Different period/fiscal year variants used in source and target steps | Space: object requires documentation | |
153 | 179 | Link method cannot be defined (see long text) | Space: object requires documentation | |
154 | 180 | Character string &2 was not found in template source text &1 | Space: object requires documentation | |
155 | 181 | Planning steps &1 and &2 have over 99 common key figures | Space: object requires documentation | |
156 | 182 | The planning step link program cannot be generated | Space: object requires documentation | |
157 | 183 | &1 data records were aggregated in &2 data records | Space: object requires documentation | |
158 | 184 | &1 data records were disaggregated at &2 data records | Space: object requires documentation | |
159 | 185 | An error was generated when the planning steps were being linked | Space: object requires documentation | |
160 | 186 | Scenario was incorrectly transported (see long text) | Space: object requires documentation | |
161 | 187 | Planning scenario &1 was adjusted | Space: object requires documentation | |
162 | 188 | Scenarios delivered by SAP cannot be transported | Space: object requires documentation | |
163 | 189 | Unable to determine master data table | Space: object requires documentation | |
164 | 190 | Choose at least one key figure | Space: object requires documentation | |
165 | 191 | Attribute &1 is already assigned to characteristic &2 | Space: object requires documentation | |
166 | 192 | Attribute &1 is already being used as a plan characteristic | Space: object requires documentation | |
167 | 193 | Plan characteristic &1 is already being used as an attribute | Space: object requires documentation | |
168 | 199 | Database table &1 is not active in the Data Dictionary | Space: object requires documentation | |
169 | 200 | *** Messages for view maintenance and view cluster maintenance | Space: object requires documentation | |
170 | 201 | Planning scenario &1 is already active | Space: object requires documentation | |
171 | 202 | Save the data first | Space: object requires documentation | |
172 | 203 | Version numeber &1 has already been assigned | Space: object requires documentation | |
173 | 204 | Assign characteristics to planning step &1 | Space: object requires documentation | |
174 | 205 | Assign key figures to planning step &1 | Space: object requires documentation | |
175 | 206 | The reference table is copied from the field catalog | Space: object requires documentation | |
176 | 207 | Enter a field catalog | Space: object requires documentation | |
177 | 208 | Enter the current number within the field catalog | Space: object requires documentation | |
178 | 209 | Assign a database table to planning step &1 | Space: object requires documentation | |
179 | 210 | Assign a planning periodicity to planning step &1 | Space: object requires documentation | |
180 | 211 | Entry number &1 is not defined in field catalog &2 | Space: object requires documentation | |
181 | 212 | Database table &1 has already been defined; further entries not required | Space: object requires documentation | |
182 | 213 | Field name for the plan characteristic is copied from the field catalog | Space: object requires documentation | |
183 | 214 | Enter a plan characteristic | Space: object requires documentation | |
184 | 215 | No fiscal year variant has yet been assigned for planning step &1 | Space: object requires documentation | |
185 | 216 | Characteristic &1 is not defined within database table &2 | Space: object requires documentation | |
186 | 217 | Field catalog &1 has not been defined | Space: object requires documentation | |
187 | 218 | Select at least one planning step method | Space: object requires documentation | |
188 | 219 | Enter a field catalog of type "Characteristic catalog" | Space: object requires documentation | |
189 | 220 | Plan data also exists for version &1: the data will also be deleted | Space: object requires documentation | |
190 | 221 | Enter a storage currency for planning scenario &1 | Space: object requires documentation | |
191 | 222 | Assign a layout or automatic planning to planning step &1 | Space: object requires documentation | |
192 | 223 | Enter a planning key figure | Space: object requires documentation | |
193 | 224 | Key figure &1 is not defined within database table &2 | Space: object requires documentation | |
194 | 225 | Enter a field catalog of type "Key figure catalog" | Space: object requires documentation | |
195 | 226 | A field name for the planning key figure is copied from the field catalog | Space: object requires documentation | |
196 | 227 | Assign sequence numbers to the characteristics for planning step &1 | Space: object requires documentation | |
197 | 228 | No errors occurred when checking planning scenario &1 | Space: object requires documentation | |
198 | 229 | No characteristics or key figures are defined for planning step & | Space: object requires documentation | |
199 | 230 | Planning scenario &1 activated successfully | Space: object requires documentation | |
200 | 231 | Planning scenario &1 could not be activated | Space: object requires documentation | |
201 | 232 | No values found | Space: object requires documentation | |
202 | 233 | Source planning step &1 is not defined in planning scenario &2 | Space: object requires documentation | |
203 | 234 | Target planning step &1 is not defined in planning scenario &2 | Space: object requires documentation | |
204 | 235 | A planning step cannot be linked to itself | Space: object requires documentation | |
205 | 236 | Database table &1 is not defined | Space: object requires documentation | |
206 | 237 | Define the database table for the active planning version | Space: object requires documentation | |
207 | 238 | Actual version &1 cannot be used as a plan version | Space: object requires documentation | |
208 | 239 | Version &1 is reserved for setup of statistical data | Space: object requires documentation | |
209 | 240 | Plan version &1 is not defined | Space: object requires documentation | |
210 | 241 | Plan version &1 is not defined for planning step &2 | Space: object requires documentation | |
211 | 242 | Database table &1 is not defined for planning | Space: object requires documentation | |
212 | 243 | Enter an existing planning step link | Space: object requires documentation | |
213 | 244 | Enter different planning steps as source and target | Space: object requires documentation | |
214 | 245 | No planning step links have been created | Space: object requires documentation | |
215 | 246 | No links have been created for planning scenario &1 | Space: object requires documentation | |
216 | 247 | DB table &1 does not match the characteristics/keyfigs for the plng step | Space: object requires documentation | |
217 | 248 | Assign a transaction or a program name | Space: object requires documentation | |
218 | 249 | Selected link is unavailable in planning scenario &1 | Space: object requires documentation | |
219 | 250 | Enter &1 | Space: object requires documentation | |
220 | 251 | Enter a program name or a transaction code | Space: object requires documentation | |
221 | 252 | Do not enter a program/transaction for this link method | Space: object requires documentation | |
222 | 253 | Planning scenario &1 is not yet active | Space: object requires documentation | |
223 | 254 | Enter a program name | Space: object requires documentation | |
224 | 255 | The selected program &1 does not exist | Space: object requires documentation | |
225 | 256 | Variant &1 has not yet been created for program &2 | Space: object requires documentation | |
226 | 257 | Enter a target version that is different from "000" | Space: object requires documentation | |
227 | 258 | Plan version &1 is already assigned to planning scenario/step &2/&3 | Space: object requires documentation | |
228 | 259 | Target plan version &1 has not yet been created | Space: object requires documentation | |
229 | 260 | Plan version &1 is already assigned to planning scenario/step &2/&3 | Space: object requires documentation | |
230 | 261 | Source plan version &1 has not yet been created | Space: object requires documentation | |
231 | 262 | Plan characteristic &1 is used in more than one planning hierarchy level | Space: object requires documentation | |
232 | 263 | Data in planning hierarchy table &1 has been deleted | Space: object requires documentation | |
233 | 264 | Enter a program name or transaction code | Space: object requires documentation | |
234 | 265 | An error occurred when generating link program &3 | Space: object requires documentation | |
235 | 266 | Enter the name of an existing program | Space: object requires documentation | |
236 | 267 | Enter the name for automatic planning | Space: object requires documentation | |
237 | 268 | Enter a plan version that is different from "000" | Space: object requires documentation | |
238 | 269 | Planning periodicity & is not defined | Space: object requires documentation | |
239 | 270 | Assign a database table to planning step &1 | Space: object requires documentation | |
240 | 271 | Enter the name of an existing planning program | Space: object requires documentation | |
241 | 272 | Enter the name of an existing planning program | Space: object requires documentation | |
242 | 273 | Enter the name of an existing link program | Space: object requires documentation | |
243 | 274 | No active version for planning step &2 exists in planning scenario &1 | Space: object requires documentation | |
244 | 275 | Planning step &1 exists solely as a documentation step | Space: object requires documentation | |
245 | 276 | Select a &1 that is different from &2 | Space: object requires documentation | |
246 | 277 | Planning scenario &1 does not have active / saved status | Space: object requires documentation | |
247 | 278 | Planning step &1 does not exist in planning scenario &2 | Space: object requires documentation | |
248 | 279 | Automatic planning &1 not yet created for planning step &2 | Space: object requires documentation | |
249 | 280 | No program that can be executed is assigned to automatic planning &1 | Space: object requires documentation | |
250 | 281 | The program assigned to automatic planning &1 does not exist | Space: object requires documentation | |
251 | 282 | Variant &2 that has been assigned does not exist | Space: object requires documentation | |
252 | 283 | No authorization to execute transaction &2 | Space: object requires documentation | |
253 | 284 | Variant &1 not yet created for program &2 | Space: object requires documentation | |
254 | 285 | Variant &1 not yet created for program &2 | Space: object requires documentation | |
255 | 286 | Planning step &2 is not defined for automatic planning | Space: object requires documentation | |
256 | 287 | Enter a target version that is different to active version &1 | Space: object requires documentation | |
257 | 288 | &1 entries for planning version &2 have been deleted | Space: object requires documentation | |
258 | 289 | Generation was successful | Space: object requires documentation | |
259 | 290 | Enter a fiscal year variant for the periodicity 'posting period' | Space: object requires documentation | |
260 | 291 | System assigns fiscal year variant to periodicity 'Week' | Space: object requires documentation | |
261 | 292 | System assigns fiscal year variant to periodicity 'Month' | Space: object requires documentation | |
262 | 293 | Define the storage periodicity | Space: object requires documentation | |
263 | 294 | Day planning is not yet supported | Space: object requires documentation | |
264 | 295 | The formula editor is only defined for arithmetical formulas | Space: object requires documentation | |
265 | 296 | Program & does not exist | Space: object requires documentation | |
266 | 297 | Transaction & does not exist | Space: object requires documentation | |
267 | 298 | Program/transaction & not yet created for planning step &2 | Space: object requires documentation | |
268 | 299 | &1 entries were copied | Space: object requires documentation | |
269 | 300 | *** Messages for layout maintenance | Space: object requires documentation | |
270 | 301 | Number range for info structure libraries is exceeded | Space: object requires documentation | |
271 | 302 | Database table &1 contains key figure field types FLTP or INT | Space: object requires documentation | |
272 | 303 | Planning scenario &1 has not been created | Space: object requires documentation | |
273 | 304 | Unknown field "&1" in database table "&2" (message only in SAP System) | Space: object requires documentation | |
274 | 305 | Characteristic name "&1" is within the SAP name range | Space: object requires documentation | |
275 | 306 | Planning step &1 cannot be planned manually for planning scenario &2 | Space: object requires documentation | |
276 | 307 | Selection / target value for characteristic incorrect when copying | Space: object requires documentation | |
277 | 308 | Overlapping start and target time intervals are not permitted | Space: object requires documentation | |
278 | 310 | Text table &1 is not active or no entries are maintained | Space: object requires documentation | |
279 | 311 | Language key "SPRAS" in text table &1 must be a "LANG" data type | Space: object requires documentation | |
280 | 312 | Field "&2" is not in the active version of text table &1 | Space: object requires documentation | |
281 | 313 | Field "&2" in text table &1 must contain the data type "CHAR" | Space: object requires documentation | |
282 | 314 | Characteristic &1 is not in the key for text table &2 | Space: object requires documentation | |
283 | 315 | Field "&1" in text table &2 does not have the required CHAR data type | Space: object requires documentation | |
284 | 316 | No file descriptions exist | Space: object requires documentation | |
285 | 317 | Variables for charateristic "&1" (type NUMC) are not optional | Space: object requires documentation | |
286 | 318 | You do not have the authorization for activity &4 with layout &3 | Space: object requires documentation | |
287 | 349 | *** Update message for view maintenance and view cluster maintenance | Space: object requires documentation | |
288 | 350 | Key figure &1 does not exist | Space: object requires documentation | |
289 | 351 | State the source key figure for "Values from previous period" | Space: object requires documentation | |
290 | 352 | Also enter the stock key figure for "Calculation of day's supply" | Space: object requires documentation | |
291 | 353 | Also enter the issue figure for "Calculation of day's supply" | Space: object requires documentation | |
292 | 354 | Define a calculation date | Space: object requires documentation | |
293 | 355 | Reference field &1-&2 does not exist in the data dictionary | Space: object requires documentation | |
294 | 356 | Source client & does not exist | Space: object requires documentation | |
295 | 357 | Target client & does not exist | Space: object requires documentation | |
296 | 358 | Planning scenrios to be transported do not exist in the source client | Space: object requires documentation | |
297 | 359 | Select at least one distribution key for the transport | Space: object requires documentation | |
298 | 360 | No distribution keys exist for the selection conditions that you entered | Space: object requires documentation | |
299 | 361 | No characteristics are assigned to planning step &1/&2 | Space: object requires documentation | |
300 | 362 | Now activate planning scenario &1 | Space: object requires documentation | |
301 | 363 | Planning step &1/&2 cannot be used for derivating | Space: object requires documentation | |
302 | 364 | Determine an active plan version for planning step &1/&2 | Space: object requires documentation | |
303 | 365 | Active plan version &1 does not exist | Space: object requires documentation | |
304 | 366 | Not all plan characteristics exist in hierarchy table &1 | Space: object requires documentation | |
305 | 367 | ABAP coding is adjusted for derivation after being saved | Space: object requires documentation | |
306 | 368 | Enter a material group | Space: object requires documentation | |
307 | 369 | Material group &1 has not been created yet | Space: object requires documentation | |
308 | 370 | No reference material has been entered for material group &1 | Space: object requires documentation | |
309 | 371 | Reference material &1 has not yet been created | Space: object requires documentation | |
310 | 372 | Enter a reference material | Space: object requires documentation | |
311 | 373 | Material &1 already exists in master data | Space: object requires documentation | |
312 | 374 | Planning layout &1 has not yet been created | Space: object requires documentation | |
313 | 375 | Data is presently locked by user &1 | Space: object requires documentation | |
314 | 376 | Enter different currencies | Space: object requires documentation | |
315 | 377 | No log entries currently exist | Space: object requires documentation | |
316 | 378 | Planning version &1 is currently locked by user &2 | Space: object requires documentation | |
317 | 379 | Hierarchy version &1 is currently locked by user &2 | Space: object requires documentation | |
318 | 380 | Planning scenario &1, planning step &2 does not exist | Space: object requires documentation | |
319 | 381 | Plan version &1 is active plan version | Space: object requires documentation | |
320 | 382 | Plan version &1 is used in interface &2 | Space: object requires documentation | |
321 | 383 | Plan version &1 is required for external application &2 | Space: object requires documentation | |
322 | 400 | *** Messages for planning hierarchy maintenance | Space: object requires documentation | |
323 | 401 | No plan characteristics are assigned to planning steps &1 &2 | Space: object requires documentation | |
324 | 402 | Enter a version of a planning hierarchy | Space: object requires documentation | |
325 | 403 | Enter a value for plan characteristic & | Space: object requires documentation | |
326 | 404 | &1 &2 cannot be checked; characteristic &3 does not exist | Space: object requires documentation | |
327 | 405 | &1 &2 does not exist | Space: object requires documentation | |
328 | 406 | Characteristic &1 does not exist as a plan characteristic | Space: object requires documentation | |
329 | 407 | Enter a function module | Space: object requires documentation | |
330 | 408 | Characteristic &1 is in customer name range YY* or ZZ* | Space: object requires documentation | |
331 | 409 | Characteristic &1 is not in customer name range YY* or ZZ* | Space: object requires documentation | |
332 | 410 | Distribution channel &1 is not defined for sales organization &2 | Space: object requires documentation | |
333 | 411 | Planning hierarchy was saved successfully | Space: object requires documentation | |
334 | 412 | Select at least one entry | Space: object requires documentation | |
335 | 413 | Select only one entry | Space: object requires documentation | |
336 | 414 | Position the cursor on an entry | Space: object requires documentation | |
337 | 415 | No previous situation has been saved | Space: object requires documentation | |
338 | 416 | No further situation has been saved | Space: object requires documentation | |
339 | 417 | More than one entry exists with the same key | Space: object requires documentation | |
340 | 418 | First create &1 &2 under &3 &4 | Space: object requires documentation | |
341 | 419 | Now enter &1 &2 by maintaining the whole hierarchy | Space: object requires documentation | |
342 | 420 | Select at least one proportional factor | Space: object requires documentation | |
343 | 421 | Enter a plan version for "Setup based on plan data" | Space: object requires documentation | |
344 | 422 | Enter a key figure for the selected proportional factor | Space: object requires documentation | |
345 | 423 | Enter a version of a planning hierarchy version | Space: object requires documentation | |
346 | 424 | Key figure &1 does not exist for planning step &2 | Space: object requires documentation | |
347 | 425 | Enter a complete planning period | Space: object requires documentation | |
348 | 426 | Select a node in the tree control | Space: object requires documentation | |
349 | 427 | You have already opened the lowest planning level | Space: object requires documentation | |
350 | 428 | Place the cursor on a node | Space: object requires documentation | |
351 | 429 | Select a level for the breakdown list <= & | Space: object requires documentation | |
352 | 430 | Enter a material group (& is a material group) | Space: object requires documentation | |
353 | 431 | You can only paste at planning level & | Space: object requires documentation | |
354 | 432 | Now overwrite the new entries with the required values | Space: object requires documentation | |
355 | 433 | No data is in the buffer | Space: object requires documentation | |
356 | 434 | "Delete" function is not executed | Space: object requires documentation | |
357 | 435 | Maintain the entries before placing them | Space: object requires documentation | |
358 | 436 | Only one entry has already been made available | Space: object requires documentation | |
359 | 437 | &1 &2 does not exist in the table | Space: object requires documentation | |
360 | 438 | Hierarchy version & is presently being processed by user & | Space: object requires documentation | |
361 | 439 | Units of measure or distribution keys are copied into nodes further down | Space: object requires documentation | |
362 | 440 | The new value & is already in the table | Space: object requires documentation | |
363 | 441 | No entries for the selected data were found in the info structure | Space: object requires documentation | |
364 | 442 | Setup of the planning hierarchy using actual data is not possible | Space: object requires documentation | |
365 | 443 | In the selection period, the end must be after the start date | Space: object requires documentation | |
366 | 444 | Planning hierarchy version &1 has been successfully copied to &2 | Space: object requires documentation | |
367 | 445 | Enter a source and a target version of a planning hierarchy | Space: object requires documentation | |
368 | 446 | Enter the planning hierarchy versions that are to be deleted | Space: object requires documentation | |
369 | 447 | The selected data was successfully deleted | Space: object requires documentation | |
370 | 448 | Enter &1 &2 in target version in the hierarchy | Space: object requires documentation | |
371 | 449 | Enter &1 &2 in the target version below &3 &4 | Space: object requires documentation | |
372 | 450 | Source version must be different from the target version | Space: object requires documentation | |
373 | 451 | Planning hierarchy is not defined for this planning step | Space: object requires documentation | |
374 | 452 | Automatic setup is not possible: info structure &1 has incomplete entries | Space: object requires documentation | |
375 | 453 | Material &1 does not exist | Space: object requires documentation | |
376 | 454 | & entries copied to the clipboard | Space: object requires documentation | |
377 | 455 | 1 entry copied to the clipboard | Space: object requires documentation | |
378 | 456 | Enter values for the selected planning level only | Space: object requires documentation | |
379 | 457 | & & was not found in any subtrees | Space: object requires documentation | |
380 | 458 | & & was deleted from & subtrees | Space: object requires documentation | |
381 | 459 | & & was not added to any subtrees | Space: object requires documentation | |
382 | 460 | & & was added to & subtrees | Space: object requires documentation | |
383 | 461 | Enter the base unit of measure and the conversion factor | Space: object requires documentation | |
384 | 462 | The base unit of measure matches the planning unit of measure | Space: object requires documentation | |
385 | 463 | You do not have authorization for scenario &1 or hierarchy version &2 | Space: object requires documentation | |
386 | 464 | Unit of measure could not be passed on fully | Space: object requires documentation | |
387 | 465 | Planned unit of measure does not match base unit of measure | Space: object requires documentation | |
388 | 500 | **Continuation of interface processing 500-540 | Space: object requires documentation | |
389 | 501 | Material grouping &2 could not be broken down | Space: object requires documentation | |
390 | 502 | &1 &2 does not exist | Space: object requires documentation | |
391 | 503 | Store grouping &2 could not be broken down | Space: object requires documentation | |
392 | 504 | Only one quantity key figure can be assigned to interface &1 | Space: object requires documentation | |
393 | 505 | Only two break-downs must be assigned to interface &1 | Space: object requires documentation | |
394 | 506 | Purchasing organization &1 is not assigned to plant &2 | Space: object requires documentation | |
395 | 507 | Unknown error when processing interface &1 | Space: object requires documentation | |
396 | 508 | Select an allocation rule or an allocation strategy | Space: object requires documentation | |
397 | 509 | Your supply source determination cannot be used for MAP allocation tables | Space: object requires documentation | |
398 | 510 | No log could be created for allocation table &1 | Space: object requires documentation | |
399 | 511 | No plant quantity could be determined for material &1 | Space: object requires documentation | |
400 | 512 | Key figure &2 for interface &1 is not a quantity key figure | Space: object requires documentation | |
401 | 513 | Plant &1 does not exist | Space: object requires documentation | |
402 | 514 | Material &1 does not exist | Space: object requires documentation | |
403 | 515 | Allocation table creation cancelled: internal error | Space: object requires documentation | |
404 | 516 | The listing screen is defined correctly | Space: object requires documentation | |
405 | 517 | No articles can be located from the screen | Space: object requires documentation | |
406 | 518 | Multiple dimension assignment in listing screen &1 | Space: object requires documentation | |
407 | 519 | Listing: Season dimensions are only used to determine the date | Space: object requires documentation | |
408 | 520 | No season/season year combination assigned in scenario | Space: object requires documentation | |
409 | 521 | Request ID &1 cannot be deleted (see long text) | Space: object requires documentation | |
410 | 530 | Entries were changed to &1 | Space: object requires documentation | |
411 | 540 | *** Scenario consistency | Space: object requires documentation | |
412 | 541 | Different storage periodicities for database table &1 | Space: object requires documentation | |
413 | 542 | Different fiscal year variants for database table &1 | Space: object requires documentation | |
414 | 543 | Inconsistent periodicity for database table &1 in planning scenario &4 | Space: object requires documentation | |
415 | 544 | Different fiscal year variant for database table &1 in plng scenario &4 | Space: object requires documentation | |
416 | 545 | Different database currency &3 in planning scenario &4 | Space: object requires documentation | |
417 | 546 | Source key figure &3 for key figure &2 is not in planning step &1 | Space: object requires documentation | |
418 | 550 | *** Messages for BW only | Space: object requires documentation | |
419 | 551 | No RFC destination is assigned to scenario &1 for the BW system | Space: object requires documentation | |
420 | 552 | Missing infocube for posting period/fiscal year variant &2 | Space: object requires documentation | |
421 | 553 | Time characteristic &1 is not assigned to an infocube field | Space: object requires documentation | |
422 | 554 | Obsolete planning scenario field & in assignments for infocube fields | Space: object requires documentation | |
423 | 555 | No infocube field is assigned to planning scenario field &1 | Space: object requires documentation | |
424 | 556 | No assignments exist for planning scenario field & | Space: object requires documentation | |
425 | 557 | Version field &1 is not assigned to any infocube fields | Space: object requires documentation | |
426 | 558 | No assignments exist for the fiscal year variant field | Space: object requires documentation | |
427 | 559 | Assignments to cube fields are only deleted for complete cube information | Space: object requires documentation | |
428 | 560 | Fiscal year variant field is not assigned to an infocube field | Space: object requires documentation | |
429 | 561 | No fiscal year variant entered in planning step &1 | Space: object requires documentation | |
430 | 562 | Key figure field &1 is not assigned to an infocube field | Space: object requires documentation | |
431 | 563 | Unit field &2 for key figure field &1 is not assigned to infocube field | Space: object requires documentation | |
432 | 564 | Missing infocube for periodicity of type &2 | Space: object requires documentation | |
433 | 565 | Infocube &3 does not contain planning scenario field &2 | Space: object requires documentation | |
434 | 566 | Infocube &3 does not contain key figure field &2 | Space: object requires documentation | |
435 | 567 | Unregistered type &1 periodicity (fiscal year variant &2) | Space: object requires documentation | |
436 | 568 | Create RFC destination &1 | Space: object requires documentation | |
437 | 569 | Planning step &1 cannot be used for SAP BW | Space: object requires documentation | |
438 | 570 | Key figure &1 is not of type P -> BW read is not supported | Space: object requires documentation | |
439 | 571 | Aggregation behavior for key figure &1 is not "Total" | Space: object requires documentation | |
440 | 600 | *** Messages for interface usage in manual planning | Space: object requires documentation | |
441 | 601 | No interfaces exist for planning scenarios/planning steps &1/&2 | Space: object requires documentation | |
442 | 602 | Assign an interface for promotions to layout &3 | Space: object requires documentation | |
443 | 603 | Errors/warnings have occurred. Read the log ... | Space: object requires documentation | |
444 | 604 | A maximum of two characteristics can be assigned to interface &1 | Space: object requires documentation | |
445 | 605 | A maximum of two break-downs can be assigned to interface &1 | Space: object requires documentation | |
446 | 606 | No extra break-downs can be assigned to interface &1 | Space: object requires documentation | |
447 | 607 | A 'material' characteristic must be assigned to interface &1 | Space: object requires documentation | |
448 | 608 | No 'plant group/plant' characteristic is assigned to interface &1 | Space: object requires documentation | |
449 | 609 | No parameters for promotions are assigned to interface &1 | Space: object requires documentation | |
450 | 610 | Only one quantity key figure can be assigned to interface &1 | Space: object requires documentation | |
451 | 611 | Only one break-down can be assigned to interface &1 | Space: object requires documentation | |
452 | 612 | Interface &1 contains an unrecognized external characteristic (&4) | Space: object requires documentation | |
453 | 613 | Break-down &2 must be the material dimension | Space: object requires documentation | |
454 | 614 | Break-down &1 has not been entered in the system | Space: object requires documentation | |
455 | 615 | Break-down method &2 does not exist (break-down &1) | Space: object requires documentation | |
456 | 616 | Grouping characteristic &4 is not the planning level for planning step &3 | Space: object requires documentation | |
457 | 617 | No grouping characteristic is assigned to break-down &1 | Space: object requires documentation | |
458 | 618 | Class type '&2' does not exist in the system | Space: object requires documentation | |
459 | 619 | Object table &1 for break-down &2 can only have one key field | Space: object requires documentation | |
460 | 620 | A break-down table must be assigned to break-down &1 | Space: object requires documentation | |
461 | 621 | A basic characteristic must be assigned to break-down &1 | Space: object requires documentation | |
462 | 622 | Break-down table &2 for break-down &1 does not exist in the DDIC | Space: object requires documentation | |
463 | 623 | Basic characteristic &1 for break-down &2 must exist in table &3 | Space: object requires documentation | |
464 | 624 | Basic characteristic &1 must be the key field for break-down table &3 | Space: object requires documentation | |
465 | 625 | Grouping characteristic &1 (break-down &2) does not exist in table &3 | Space: object requires documentation | |
466 | 626 | Grouping characteristic &1 cannot be the key field for table &3 | Space: object requires documentation | |
467 | 627 | Enter a (active) planning version for interface &1 | Space: object requires documentation | |
468 | 628 | Unknown type '&2' for interface &1 | Space: object requires documentation | |
469 | 629 | No active version is assigned to planning step &3 | Space: object requires documentation | |
470 | 630 | Characteristic &1 is not available in the selected area or in the layout | Space: object requires documentation | |
471 | 631 | Key figure &1 is not available in the selected area or in the layout | Space: object requires documentation | |
472 | 632 | Processing interface &1 for promotions was canceled | Space: object requires documentation | |
473 | 633 | Grouping characteristic &1 is not in the selected area or in the layout | Space: object requires documentation | |
474 | 634 | Assign a promotion type to interface &1 | Space: object requires documentation | |
475 | 635 | Only two break-downs must be assigned to interface &1 | Space: object requires documentation | |
476 | 636 | Assign a material dimension and a plant dimension to interface &1 | Space: object requires documentation | |
477 | 637 | The selected area for interface &2 contains an incorrect planning version | Space: object requires documentation | |
478 | 638 | For interface &2, only select data for planning version &1 | Space: object requires documentation | |
479 | 639 | More than one planning version is available in the selected area | Space: object requires documentation | |
480 | 640 | Processing of the promotion interface is complete (see log) | Space: object requires documentation | |
481 | 641 | Promotion &1 for interface &2 was simulated successfully | Space: object requires documentation | |
482 | 642 | RFC error when creating a promotion in the target system: &1 | Space: object requires documentation | |
483 | 643 | RFC error when creating a class in the target system: &1 | Space: object requires documentation | |
484 | 644 | No errors occurred when checking interface &1 | Space: object requires documentation | |
485 | 645 | Break-down &2 must be the plant dimension | Space: object requires documentation | |
486 | 646 | No parameters for specific allocation table are assigned to interface &1 | Space: object requires documentation | |
487 | 647 | Enter an allocation table type | Space: object requires documentation | |
488 | 648 | &1 | Space: object requires documentation | |
489 | 649 | Assin an "allocation table" interface to the layout | Space: object requires documentation | |
490 | 650 | Interface &1 complete (for allocation table number &2, see log) | Space: object requires documentation | |
491 | 651 | Different purchasing organizations for planning/plant/distribution center | Space: object requires documentation | |
492 | 652 | Planned sales org. &1 is different to sales org. &2 (plant &3) | Space: object requires documentation | |
493 | 653 | Selected area does not contain the key figure for interface &1 | Space: object requires documentation | |
494 | 654 | RFC error when calling promotion maintenance: &1 | Space: object requires documentation | |
495 | 655 | The system could not generate the log for promotion &1 | Space: object requires documentation | |
496 | 656 | Company code for plant &1 does not exist | Space: object requires documentation | |
497 | 657 | Company code for distribution center &1 does not exist | Space: object requires documentation | |
498 | 658 | Customer &1 is not entered as a plant | Space: object requires documentation | |
499 | 659 | Distribution center &1 is not maintained as a plant | Space: object requires documentation | |
500 | 660 | &1 | Space: object requires documentation | |
501 | 661 | No class processing run in the simulation mode | Space: object requires documentation | |
502 | 662 | &1 created | Space: object requires documentation | |
503 | 663 | Planned mtrl grp &1 is not the same as mtrl grp &2 for material &3 | Space: object requires documentation | |
504 | 664 | Purch. grp &1 is not the same as purc. grp &2 from interface &3 | Space: object requires documentation | |
505 | 665 | Dist. channel &1 is different from dist. channel &2 (plant &3) | Space: object requires documentation | |
506 | 666 | Planned division &1 is different from division &2 (plant &3) | Space: object requires documentation | |
507 | 667 | Country key &1 is different from country key &2 (plant &3) | Space: object requires documentation | |
508 | 668 | The delivery phase for the plant does not equal 100% | Space: object requires documentation | |
509 | 669 | The delivery phase for the distribution center does not equal 100% | Space: object requires documentation | |
510 | 670 | The delivery phases are complete | Space: object requires documentation | |
511 | 671 | Enter at least date category, delivery date, and percent rate | Space: object requires documentation | |
512 | 672 | Entry with delivery date and delivery category already exists | Space: object requires documentation | |
513 | 673 | Creation of allocation table cancelled | Space: object requires documentation | |
514 | 674 | Allocation table &1 was not created in the planning session | Space: object requires documentation | |
515 | 675 | Company codes &1 and company code &2 (plang &3) are different | Space: object requires documentation | |
516 | 676 | &1 deleted | Space: object requires documentation | |
517 | 677 | &1 exists more than once in your selection | Space: object requires documentation | |
518 | 678 | You cannot convert a store into a customer | Space: object requires documentation | |
519 | 679 | Break-down &1 does not exist in system | Space: object requires documentation | |
520 | 680 | Interface &1 cannot be used for planning step &2 | Space: object requires documentation | |
521 | 681 | Interface &1 is not a "promotions" interface | Space: object requires documentation | |
522 | 682 | Interface &1 is not an "allocation table" interface | Space: object requires documentation | |
523 | 683 | Promotion &1 was not created in the planning session | Space: object requires documentation | |
524 | 684 | Error '&1' occurred when updating the application log | Space: object requires documentation | |
525 | 685 | Mode '&1' is not permitted for processing planning data | Space: object requires documentation | |
526 | 686 | Error in manual planning (scenario/step/layout/variant) = (&1,&2,&3,&4) | Space: object requires documentation | |
527 | 687 | User &4 does not have authorization to change interface &3 | Space: object requires documentation | |
528 | 688 | No authorization to change the interface for planning step &2 | Space: object requires documentation | |
529 | 689 | User &4 has no authorization for displaying interface &3 | Space: object requires documentation | |
530 | 690 | No authorization for displaying the interface for planning step &2 | Space: object requires documentation | |
531 | 691 | User &4 has no authorization to run interface &3 | Space: object requires documentation | |
532 | 692 | Enter a break-down table and a basic characteristic | Space: object requires documentation | |
533 | 693 | Enter a class type | Space: object requires documentation | |
534 | 694 | Database table &1 does not exist | Space: object requires documentation | |
535 | 695 | DDIC object &1 is not a transparent table | Space: object requires documentation | |
536 | 696 | Background processing has begun | Space: object requires documentation | |
537 | 697 | Last promotion unavailable | Space: object requires documentation | |
538 | 698 | Last allocation table unavailable | Space: object requires documentation | |
539 | 699 | Break-down &1 could find no values for grouping &2 | Space: object requires documentation | |
540 | 700 | X messages: 701 - 799 | Space: object requires documentation | |
541 | 701 | Unexpected return code in task SYNTAX CHECK: & | Space: object requires documentation | |
542 | 702 | Unexpected field content in &1: &2 | Space: object requires documentation | |
543 | 703 | Unexpected field content | Space: object requires documentation | |
544 | 704 | Entry for internal table &1 does not exist: &2 | Space: object requires documentation | |
545 | 705 | No entry exists for library & in table TWISPS01 | Space: object requires documentation | |
546 | 706 | No entry exists For library/planning layout &1/&2 in table TWISPC_TKES1L | Space: object requires documentation | |
547 | 707 | Unexpected return code FB MC_GSTRU_PRUEFEN: &1 | Space: object requires documentation | |
548 | 708 | Unexpected return code FB DDIF_TABL_GET: &1 | Space: object requires documentation | |
549 | 709 | Error occurred when creating hierarchy table &1 | Space: object requires documentation | |
550 | 710 | Error occurred when activating hierarchy table &1 | Space: object requires documentation | |
551 | 711 | Unexpected return code for & : & | Space: object requires documentation | |
552 | 712 | Unknown table type when calling FB 'WIS_PLAN_CHECK_TABNAME' | Space: object requires documentation | |
553 | 713 | Syntax error in generated coding | Space: object requires documentation | |
554 | 714 | Unexpected return code FB DDIF_STATE_GET for &1 | Space: object requires documentation | |
555 | 715 | Unexpected return code FB DDUT_OBJECT_COPY for &1, &2 | Space: object requires documentation | |
556 | 716 | TADIR entry for &1 already exists | Space: object requires documentation | |
557 | 717 | Error occurred when reading the TADIR entry for &1 | Space: object requires documentation | |
558 | 718 | Error occurred when writing the TADIR for &1 | Space: object requires documentation | |
559 | 719 | Layout &1 cannot be assigned as it does not exist | Space: object requires documentation | |
560 | 720 | Error when reading table TWISPC_PLSCH for &1/&2 | Space: object requires documentation | |
561 | 721 | Error when reading table TWISPS01 for &1 | Space: object requires documentation | |
562 | 722 | Missing entry in table T_TWISPC_KENNZ for &1/&2/&3 | Space: object requires documentation | |
563 | 723 | Unexpected constellation for F4_PLSZN/F4_PLSCH: &1/&2 | Space: object requires documentation | |
564 | 724 | Error when reading table TWISPC_ZKENN for &1/&2 | Space: object requires documentation | |
565 | 725 | Error when reading table TWISPC_ZMERK for &1/&2 | Space: object requires documentation | |
566 | 726 | Inconsitency in info structure/planning scenario/DB table: &1/&2/&3/&4 | Space: object requires documentation | |
567 | 727 | Inconsistency because of IMPORT of scenario/step &1/&2 | Space: object requires documentation | |
568 | 728 | Error when reading table TWISPC_PLSZN for &1 | Space: object requires documentation | |
569 | 729 | Error when reading table TWISPC_ZPSPL for &1/&2 | Space: object requires documentation | |
570 | 730 | Unexpected return code FB WIS_PLAN_DIALOG_HIER: & | Space: object requires documentation | |
571 | 731 | Unexpected return code FB WIS_PLAN_DIALOG: & | Space: object requires documentation | |
572 | 732 | Unexpected return code FB_K_PLAN_DICTIONARY_READ: & | Space: object requires documentation | |
573 | 733 | Unexpected return code FB WIS_PLAN_PLSCH_COMLETE | Space: object requires documentation | |
574 | 734 | Unexpected error in FB WIS_PLAN_PLSZN_CHECK | Space: object requires documentation | |
575 | 735 | Unexpected return code in FB WIS_PLAN_PLSZN_ACTIVATE | Space: object requires documentation | |
576 | 736 | Unexpected return code in FB DDUT_DOMVALUES_GET | Space: object requires documentation | |
577 | 737 | Unexpected return code in FB REUSE_ALV_POPUP_TO_SELEC | Space: object requires documentation | |
578 | 738 | Unexpected return code &1 for FB WIS_PLAN_EXEC_CONNECTION | Space: object requires documentation | |
579 | 739 | Unexpected return code &1 in FB RS_VARIANT_EXISTS | Space: object requires documentation | |
580 | 740 | Error in copy man generation for scenario/step/DB tab/report &1/&2/&3/&4 | Space: object requires documentation | |
581 | 741 | Unexpected return code &1 for FB RV_REPORT_READ | Space: object requires documentation | |
582 | 742 | Unexpected return code for FB WIS_PLAN_GET_IS_FIELDS (info structure &1) | Space: object requires documentation | |
583 | 743 | Error occurred when generating the service program &3 | Space: object requires documentation | |
584 | 744 | Missing error &1 in internal table T_HTAB_STRUC | Space: object requires documentation | |
585 | 745 | Plan characteristic &1 was expected in database table &2 | Space: object requires documentation | |
586 | 746 | Unexpected return code &1 in FB DDIF_NAMETAB_GET | Space: object requires documentation | |
587 | 747 | Unexpected constellation in radio buttons MERK1_R - MERK8_R | Space: object requires documentation | |
588 | 748 | Unexpected constellation in radio buttons HKOMP and HTEIL | Space: object requires documentation | |
589 | 749 | Unexpected return code &1 in FB 'AUTHORITY_CHECK_TCODE' (Tcode = &2) | Space: object requires documentation | |
590 | 750 | Invalid generation mode &1 | Space: object requires documentation | |
591 | 751 | Unexpected return code &1 for FB WIS_PLAN_PLVER_REPORTS_GENER | Space: object requires documentation | |
592 | 752 | No system program can be assigned to automatic planning method &1 | Space: object requires documentation | |
593 | 753 | Unexpected constellation for radio buttons MERK1_R - MERK9_R | Space: object requires documentation | |
594 | 754 | Unexpected return code &1 for FB WIS_PLAN_EXEC_MASCHPL | Space: object requires documentation | |
595 | 755 | Unexpected return code &1 for FB SPLITTERCONTROL_CREATE | Space: object requires documentation | |
596 | 756 | Error when reading table TWISPC_PLSCHT for &1/&2 | Space: object requires documentation | |
597 | 757 | Unexpected internal status &1 in hierarchy table &2 in DB activation | Space: object requires documentation | |
598 | 758 | Hier.tab. &1 could not be deleted from the DB although it has no entries | Space: object requires documentation | |
599 | 759 | Database object &1 is not a transparent table. Error in DB activation | Space: object requires documentation | |
600 | 760 | Unknown internal status "&1" in hierarchy table &2 | Space: object requires documentation | |
601 | 761 | Unexpected error in the automatic setup of the planning hierarchy | Space: object requires documentation | |
602 | 762 | Error when reading table TWISPC_DPLVA for &1/&2/&2/&4 | Space: object requires documentation | |
603 | 763 | Unexpected return code when reading key table for &1 | Space: object requires documentation | |
604 | 764 | Error when reading table twispc_plsznt with &1 | Space: object requires documentation | |
605 | 765 | Unexpected error when reading table IT_KEYS with &1 | Space: object requires documentation | |
606 | 766 | Error when reading table twispc_plscht with &1 &2 | Space: object requires documentation | |
607 | 767 | Error when reading table twispc_plvert with &1 &2 &3 &4 | Space: object requires documentation | |
608 | 768 | Unexpected return code for GET_PRINT_PARAMETERS with value &1 | Space: object requires documentation | |
609 | 769 | Unexpected error when deleting element &1 from node it_tctrl | Space: object requires documentation | |
610 | 770 | Unexpected error when reading entry &1 from table t_tctrl | Space: object requires documentation | |
611 | 771 | Unexpected error when reading the DDIC info for additional key figure &1 | Space: object requires documentation | |
612 | 772 | Additional key figure &1 does not exist any more | Space: object requires documentation | |
613 | 773 | Unexpected return code &1 for FB 'ENWUEUE_E_WISP_PLSZN' | Space: object requires documentation | |
614 | 774 | Unexpected return code &1 for FB 'EVAL_FORMULA' | Space: object requires documentation | |
615 | 775 | Unexpected return (&1, &2) for FB CHECK_CUSTOMER_NAMES | Space: object requires documentation | |
616 | 776 | Error when updating table TWISPC_PLSZN: & | Space: object requires documentation | |
617 | 777 | Error when updating table TWISPC_PLSZNT: & | Space: object requires documentation | |
618 | 778 | Error when inserting table TWISPC_PLSCH: & | Space: object requires documentation | |
619 | 779 | Error when inserting table TWISPC_PLSCH_W: & | Space: object requires documentation | |
620 | 780 | Error when inserting table TWISPC_ZMERK: & | Space: object requires documentation | |
621 | 781 | Error when inserting table TWISPC_ZMERK_W: & | Space: object requires documentation | |
622 | 782 | Error when inserting table TWISPC_ZKENN: & | Space: object requires documentation | |
623 | 783 | Error when inserting table TWISPC_ZKENN_W: & | Space: object requires documentation | |
624 | 784 | Error when inserting table TWISPC_PLSCHT: & | Space: object requires documentation | |
625 | 785 | Error when updating table TWISPC_ZUSKZ: & | Space: object requires documentation | |
626 | 786 | Error when updating table TWISPC_KENNPAR: & | Space: object requires documentation | |
627 | 787 | Error when inserting table TWISPC_MASCHPL: & | Space: object requires documentation | |
628 | 788 | Error when inserting table TWISPC_MASCHPLT: & | Space: object requires documentation | |
629 | 789 | Error when inserting table TWISPC_PLVER: & | Space: object requires documentation | |
630 | 790 | Error when inserting table TWISPC_PLVERT: & | Space: object requires documentation | |
631 | 791 | Error when updating table TWISPS01: & | Space: object requires documentation | |
632 | 792 | Error when inserting table TWISPC_TKES1L: & | Space: object requires documentation | |
633 | 793 | Error when updating table TWISPC_VRSIO: & | Space: object requires documentation | |
634 | 794 | Error when updating table TWISPC_VRSIOT: & | Space: object requires documentation | |
635 | 795 | Error when updating table P44V: & | Space: object requires documentation | |
636 | 796 | Error when updating table TWISPC_PLHVS: & | Space: object requires documentation | |
637 | 797 | Error when updating table TWISPC_PLHVST: & | Space: object requires documentation | |
638 | 798 | Error when updating table MCSMET: & | Space: object requires documentation | |
639 | 799 | Error when inserting table TWISPC_KENNFG: & | Space: object requires documentation | |
640 | 800 | Error when inserting table TWISPC_KENNF: & | Space: object requires documentation | |
641 | 801 | Error when inserting table TWISPC_KENNFZ: & | Space: object requires documentation | |
642 | 802 | Error when inserting table TWISPC_ZPSPL: & | Space: object requires documentation | |
643 | 803 | Error when inserting table TWISPC_KENNFGT: & | Space: object requires documentation | |
644 | 804 | Unexpected return code &1 for FB DDIF_FIELDINFO_GET | Space: object requires documentation | |
645 | 805 | Error when updating table TCNG: & | Space: object requires documentation | |
646 | 806 | Error when updating table TCNGT: & | Space: object requires documentation | |
647 | 807 | Error when updating table TCNO: & | Space: object requires documentation | |
648 | 808 | Error when updating table TCNOT: & | Space: object requires documentation | |
649 | 809 | Error when updating table TCNN: & | Space: object requires documentation | |
650 | 810 | Error when updating table TCNNT: & | Space: object requires documentation | |
651 | 811 | Error when updating table TCNL: & | Space: object requires documentation | |
652 | 812 | Error when updating table TCNLT: & | Space: object requires documentation | |
653 | 813 | Error when updating table TFAT: & | Space: object requires documentation | |
654 | 814 | Error when updating table TFATT: & | Space: object requires documentation | |
655 | 815 | Error when updating table TFMT: & | Space: object requires documentation | |
656 | 816 | Error when updating table TFMTT: & | Space: object requires documentation | |
657 | 817 | Error when updating table THLT: & | Space: object requires documentation | |
658 | 818 | Error when updating table THLTT: & | Space: object requires documentation | |
659 | 819 | Error when inserting table TWISPC_MPLSCH: & | Space: object requires documentation | |
660 | 820 | Unexpected return code &1 for FB MARA_SINGLE_READ | Space: object requires documentation | |
661 | 821 | Error when updating table TWISPC_MTEXT: & | Space: object requires documentation | |
662 | 822 | Unexpected return code &1 for FB WIS_PLAN_PLSZN_TRANSPORT | Space: object requires documentation | |
663 | 823 | Unexpected return code &1 for FB WIS_PLAN_DISP_INTERF_LOG | Space: object requires documentation | |
664 | 824 | Unexpected return code &1 for function module &2 | Space: object requires documentation | |
665 | 825 | No fields are assigned to infocube fields for planning scenario &1 | Space: object requires documentation | |
666 | 826 | Error occurred when reading table TWISPC_PLSZN_BW for &1 | Space: object requires documentation | |
667 | 827 | Error occurred when updating table TWISPC_BREAKD: & | Space: object requires documentation | |
668 | 828 | Error occurred when inserting table &2: &1 | Space: object requires documentation | |
669 | 829 | Actual data updated | Space: object requires documentation | |
670 | 830 | No infocube is assigned to periodicity &1 &2 | Space: object requires documentation | |
671 | 831 | Infocube &1 does not contain information object &2 | Space: object requires documentation |
History
Last changed on/by | 19990219 | SAP | |
SAP Release Created in |