/SAPAPO/TSM - Messages from Time Series Manager
The following messages are stored in message class /SAPAPO/TSM: Messages from Time Series Manager.
It is part of development package /SAPAPO/OO_TIMESERIES in software component SCM-APO-FCS. This development package consists of objects that can be grouped under "Time Series Management".
It is part of development package /SAPAPO/OO_TIMESERIES in software component SCM-APO-FCS. This development package consists of objects that can be grouped under "Time Series Management".
Message Nr ▲ | Message Text |
---|---|
000 | & & |
001 | Planning object structure ID & is invalid |
002 | Planning object structure name & is invalid |
003 | Planning object successfully created |
004 | Planning object structure name & already exists |
005 | Planning object structure & is not active |
006 | Planning object structure & does not have the type basis |
007 | Planning object structure & is not supported for SNP planning |
008 | Planning object structure name must not be blank |
009 | Standard SNP planning level already exists |
010 | There are no key figures in the specified planning area |
011 | Unexpected system situation or behavior; inform systems administrator |
012 | Master plng object structure & already exists for this char. combination |
013 | Planning object structure & is not determined for DP bill of materials |
014 | Planning objects successfully deleted |
015 | Database & not supported |
016 | Error while deleting characteristics combinations |
017 | Error when generating extract structure & |
018 | Internal error; multiple planning areas exist for InfoSource & |
019 | InfoSource & not assigned to planning area |
020 | No values exist |
021 | Error reading master data |
022 | Enter values for all characteristics |
023 | Transfer to R/3 using mixed periodicities is not allowed |
024 | Periodicities of forecast profile and planning book are incompatible |
025 | Mixed periodicities in a forecast are not allowed |
026 | Planning book horizon is smaller than forecast horizon |
027 | R**2 = &1 ; adjusted R**2 = &2 ; Durbin-Watson = &3 ; MAPE = &4 |
028 | Choose an aggregation level |
029 | Select characteristic value combinations for generation |
030 | Invalid unit of measure & |
031 | No LC dimension found for unit of measure & |
032 | Basic key figure & contains no data |
033 | Info object & not included in InfoCube |
034 | Characteristic of selection not part of aggregation level |
035 | The manual forecast is not processed in the background |
036 | In the forcast profile "No Forecast" has been set |
037 | Choose at least one characteristic that is not a CBF characteristic |
038 | No export data source exists |
039 | Error reading planning objects (No SNP master data table found) |
040 | Specify planning versions |
041 | InfoCube not read. No characteristic or navigation attribute exists |
042 | Planning object has not been created |
043 | No further values available |
044 | Planning objects created partially in & |
045 | All characteristic combinations already exist |
046 | No characteristic combinations found |
047 | No data can be displayed |
048 | No checks selected |
049 | There are no plannable characteristic combinations: &1 - &2 |
050 | No further InfoCubes for this planning area |
051 | Extraction structure '&1' deleted and regenerated in target system |
052 | Extraction structure '&1' need not be changed |
053 | Time period invalid |
054 | Characteristic &1 is not defined in planning object structure &2 |
055 | Execution of "applications after import" method for DataSource '&1' |
056 | Planning area for DataSource '&1' does not exist in target system |
057 | Time stream '&1' does not exist |
058 | Extraction structure '&1' does not yet exist in the target system |
059 | Extraction structure '&1' already exists in target system |
060 | The Proact - SDP inbound is not intended for orders in the LC |
061 | Planning object structure must contain characteristic '&1' |
062 | Planning object structure must contain a product characteristic |
063 | Invalid product assignment |
064 | Internal error adopting a characteristic |
065 | Planning object structure must contain a product characteristic |
066 | Characteristic '&1' cannot be used as product characteristic |
067 | Disallowed use of navigation attributes |
068 | Planning object structure being referenced => No changes allowed |
069 | Invalid time buckets profile in data view & |
070 | Info objects not activated => report /SAPAPO/TS_D_OBJECTS_COPY |
071 | Planning object structures must be manually activated |
072 | Planning object structure '&1' cannot be maintained (type: '&2') |
073 | Characteristic '&1' not assigned to planning object structure '&2' |
074 | InfoCube & does not have the required structure |
075 | The contents of planning object structure & were deleted |
076 | Time series still exist for planning area & |
077 | Specify a planning object structure |
078 | Specify an InfoCube |
079 | Planning object structure & does not have the required structure |
080 | Only use time characteristics to restrict time |
081 | Only use 'Including' conditions to restrict time |
082 | Only use 'EQ' or 'BT' conditions to restrict time |
083 | Block creation is only possible for period ind. &, not for & |
084 | Planning area incorrectly named; do not enter special characters or space |
085 | Data partly outside of horizon &1 to &2 |
086 | Data partly before horizon &1 to &2 |
087 | Data partly after horizon &1 to &2 |
088 | Planning area & is not an SNP planning area |
089 | Choose a characteristic |
090 | You must restrict the superordinate characteristic & of characteristic & |
091 | Invalid selection condition for characteristic '&1' in data extraction |
092 | Select a time characteristic |
093 | No logs found |
094 | No aggregates exist |
095 | Delivered InfoObject &1 has been modified |
096 | Aggregate &1 is not defined in planning object structure &2 |
097 | No duplicate characteristic combinations found |
098 | Duplicate characteristic combinations were found |
099 | Internal error [&] |
100 | Error in control setup |
101 | Error while calling method |
102 | Error calling COM routine &1 (return code &2) |
103 | An error occurred, please correct it |
104 | No characteristic assigned to planning object structure & |
105 | Tree node could not be deleted |
106 | Key figure &1 is read only. Data cannot be modified. |
107 | Error reading characteristics |
108 | Error while reading characteristics for basis planning object structure |
109 | Error while creating planning object structure |
110 | Name unknown |
111 | Planning object structure successfully saved |
112 | Planning object structure &1 does not exist |
113 | Interface not complete |
114 | Planning object structure successfully activated |
115 | Invalid planning object ID |
116 | Activation error |
117 | Planning object structure successfully deleted |
118 | MAPE: &1 MSE: &2 RMSE: &3 MPE: &4 |
119 | MAD: &1 Error total: &2 |
120 | ALPHA: &1 BETA: &2 GAMMA: &3 |
121 | Forecast key figure does not correspond with a planning row |
122 | The data is not saved |
123 | Planning horizon is smaller than past horizon of the forecast |
124 | Data saved successfully |
125 | Following forecast profile selected: &1 |
126 | No incorrect characteristic combinations found in aggregate & |
127 | Incorrect characteristic combinations were found in aggregate & |
128 | & P index does not exist on database |
129 | & P index is a non-unique index |
130 | Error converting a product characteristic |
131 | No selection was made |
132 | & P index not found |
133 | & P index checked successfully |
134 | & P index repaired |
135 | DataSource '&2' exists for planning area '&1' |
136 | There is no planning book for planning area '&1' |
137 | Error repairing P index: & |
138 | No planning objects created |
139 | &2 planning objects created for planning object structure &1 |
140 | Error during unicode check for program '&1' |
141 | Error when generating program |
142 | Key figure & not locked, data not saved |
143 | &2 planning objects not created for planning object structure &1 |
144 | No planning objects deleted |
145 | Invalid selection ID chosen ('&1') |
146 | &2 planning objects not deleted for planning object structure &1 |
147 | Planning objects for &2 selections deleted from &1 |
148 | Specify a planning object structure |
149 | Specify a planning area |
150 | Planning object structure successfully created |
151 | Planning object structure successfully activated |
152 | Planning area successfully created |
153 | Planning object structure successfully changed |
154 | Error occured during activation (see log) |
155 | Batch job for filling the aggregate successfully scheduled |
156 | No errors found when checking planning object structure |
157 | Planning area successfully changed |
158 | Planning area locked by user '&' |
159 | Planning object structure locked by user '&' |
160 | There are different key figures with the same key figure ID |
161 | There are the same key figures with a different key figure ID |
162 | No errors found when checking the planning area |
163 | Choose a data source |
164 | &1 must not be activated |
165 | Internal Error |
166 | Planning area & is invalid |
167 | Characteristic value & of characteristic & converted incorrectly |
168 | Characteristic value & not allowed |
169 | No new characteristics combinations were loaded |
170 | Planning obj. structure does not contain all SNP-relevant characteristics |
171 | Planning object structure does not contain all of the CBF characteristics |
172 | No planning area selected |
173 | Planning object structure &1 not saved |
174 | At least one active aggregate exists for master plng object structure & |
175 | Aggregate is aleady active |
176 | "&1" is not a planning object structure relevant to CBF |
177 | No characteristics combination was found in aggregate & |
178 | Data record &1 of realignment table &2 is not completely maintained |
179 | No planning object ID was read or buffered from aggregate &1 |
180 | Lock could not be acquired for creating a register |
181 | No relationship found between &1 and &2 |
182 | Status of planning area &1 contains errors |
183 | Status of planning area &1 corrected |
184 | Status has been updated |
185 | No notes were downloaded |
186 | &1 notes downloaded |
187 | Errors in initialization status for pl.area &1 and planning version &2 |
188 | Can only be repaired manually |
189 | Characteristics combination was read from &2, not &1 |
190 | Dimension successfully created |
191 | Function only possible for DP planning object structures |
192 | Check aggregate &: |
193 | No incorrect characteristics combinations found in planning object str. & |
194 | Incorrect characteristics combinations found in planning object struct. & |
195 | All the standard characteristics are already active |
196 | Incorrect characteristics combination(s) |
197 | An error occurred during initialization |
198 | Name of InforProvider cannot be blank |
199 | Invalid import parameter |
200 | Planning area & does not exist |
201 | No short text specified for planning area |
202 | No &2 specified for planning area &1 |
203 | Planning area & already exists |
204 | Planning version & already exists |
205 | Version &1 does not exist for planning area &2 |
206 | There are no planning versions for planning area &1 |
207 | No liveCache anchor found |
208 | Timestream & does not exist |
209 | Incorrect definition of planning area & |
210 | Error in definition of hierarchical characteristic & |
211 | Inconsistent definition of planning area &1: Key figure &3 |
212 | Invalid method |
213 | Planning area does not contain key figure & |
214 | No disaggregation key figure has been defined for key figure & |
215 | Key figure &: Invalid aggregation/disaggregation rule |
216 | Invalid propagation mode for key figure & |
217 | Invalid selection |
218 | Invalid key figure index & |
219 | Invalid data status |
220 | Time series deletion failed |
221 | No parameter time series available for current selection |
222 | Key figure &: Invalid time-based aggregation/disaggregation rule |
223 | No entries deleted |
224 | No planning version selected |
225 | Error occurred when reading orders |
226 | An invalid version was selected |
227 | No key figure was found for selection |
228 | Time buckets profile & does not exist |
229 | Time buckets profile & is invalid |
230 | There are no plannable characteristic combinations |
231 | Insufficient information about read period transferred |
232 | Periodicities of InfoCube and plng book/plng area are incompatible |
233 | Data of a frozen version may not be changed |
234 | No plannable objects exist for this selection |
235 | No valid storage buckets profile exists |
236 | No valid request ID exists |
237 | Update termination &1 - &2 |
238 | Data changes of several versions not allowed |
239 | InfoCube description already exists |
240 | Key figure &1: Restriction mode change from &2 to &3 is invalid |
241 | Inconsistent state: No. of charctstc combinations <-> no. of LC anchors |
242 | Inconsistent state: Parameter time series <-> LC anchors - incompatible |
243 | Inconsistent state: & |
244 | Not authorized to change planning area & |
245 | Activate PPM or remove it from model. Source of supply: & |
246 | Characteristic & not contained in planning area |
247 | Value of key figure &1 had to be corrected because of key figure &2 |
248 | Not all InfoCube data can be used for the planning area |
249 | Date is after end date of buckets profile & |
250 | No forecast profile exists for this planning area |
251 | Enter a planning area |
252 | InfoObject & does not exist |
253 | Attributes of key figure & must not be changed |
254 | You must not add key figure & |
255 | You cannot delete key figure & |
256 | Combination of time characteristic values inconsistent: &1 &2 &3 &4 |
257 | Invalid rule for DP BOMS key figure & |
258 | Table row is too wide |
259 | Planning area & falls within the SAP name range |
260 | Invalid selection. No hierarchic characteristic was added |
261 | Info object does not exist |
262 | Invalid combination of node type and hierarchy ID |
263 | Invalid combination of hierarchy ID and level ID |
264 | A link to this info object already exists |
265 | No planning area exists for version & |
266 | InfoCube & does not have the required structure |
267 | Warning: This selection will block the complete version '&1' |
268 | No detailed lock could be set for characteristic '&1' |
269 | No detailed lock could be set for &1 characteristics (&2) |
270 | No characteristic value combination created for product &1 and PPM/PDS &2 |
271 | Value of key figure &1 in period &2 - &3 too large |
272 | Planning area and InfoCube must have common characteristic |
273 | Invalid use of DP BOM auxiliary characteristics |
274 | InfoCube not allowed as data source for key figure '&' |
275 | Key figure function &1 already used in planning object structure |
276 | Error creating key figure description |
277 | Error deleting key figure description |
278 | No key figure ID found for DP BOM parameter time series |
279 | Parallel processing is not allowed |
280 | Save terminated due to customer action in BAdI |
281 | No data for version &2 exists in InfoCube &1 |
282 | Error during activation of table &1 |
283 | No (further) object found |
284 | Start / end date adjusted to the storage buckets profile |
285 | Key figure '&1' not assigned to the master planning object structure |
286 | Internal error occurred when deleting a key figure from an aggregate |
287 | Loading of proportional factors is not allowed |
288 | Loading of fixed data is not allowed |
289 | liveCache objects could not be checked |
290 | System error during parallel processing: &1&2 |
291 | Proportional factors are loaded to an aggregated level |
292 | Fixed data is loaded to an aggregated level |
293 | Non-repairable key figure inconsistency for key figure &1 |
294 | Inconsistent initialization time period for key figure &1 |
295 | Planning object structure not used in any planning area |
296 | The number of characteristics combinations per block is very small |
297 | No characteristics combinations found in & |
298 | Key figure description for key figure &1 does not exist in liveCache |
299 | Key figure description must be updated in liveCache |
300 | Planning area successfully deleted |
301 | Terminated without saving |
302 | Planning area &1, planning version &2 could not be initialized |
303 | Planning area '&1' could not be deleted |
304 | Planning object structure '&1' could not be deleted |
305 | Scheduling agreement locked by other user |
306 | Planning version &1 in planning area &2 not yet initialized |
307 | Planning object structure &1 copied successfully |
308 | Copying not permitted |
309 | Plannning version &1 is not initialized to planning area &2 |
310 | No characteristic combinations exist for planning object structure &1 |
311 | Wrong characteristics combination: & |
312 | Key figure &1 does not exist for aggregate &2 |
313 | No planning object structure found |
314 | Version '&1' locked by user '&2', initialization terminated |
315 | Version '&1' is locked, initialization was not carried out |
316 | Select characteristic combinations for substitution |
317 | &1 is a planning object structure |
318 | Plan version for planning object structure &1 not found |
319 | *****************DataSource check and RemoteCube check******************* |
320 | Planning object structure and planning area successfully determined |
321 | Data from planning area successfully read |
322 | A data record has been inserted in planning area |
323 | Data from RemoteCube successfully read |
324 | Values for a char. combination and a period successfully compared |
325 | Key figure values are identical (User configuration correct) |
326 | Key figure values differ (User configuration incorrect) |
327 | No inconsistencies found |
328 | Planning area contains all characteristics from RemoteCube |
329 | Planning area contains all key figures from RemoteCube |
330 | Inserted data record removed from planning area |
331 | End of processing for InfoCube &1 |
332 | Export DataSource successfully repaired |
333 | Export DataSource successfully deleted |
334 | Checking not carried out completely (No data record found) |
335 | Select a version |
336 | DataSource deletion cancelled |
337 | Characteristic '&1' must be in the planning book |
338 | Characteristics of planning areas '&1' and '&2' are not compatible |
339 | liveCache lock handler not available |
340 | Reading from planning area not completely carried out |
341 | Reading from Infocube or Remotecube not completely carried out |
342 | Field catalog created is empty |
343 | RemoteCube is empty (Configuration probably incorrect) |
344 | No line whose key figure values are not all 0 found in InfoCube |
345 | Program terminated due to runtime errors |
346 | A characteristic from the RemoteCube was not found in the planning area |
347 | A key figure from the RemoteCube was not found in the planning area |
348 | Consistency check faulty (Carry out a consistency check) |
349 | Characteristic is a navigation attribute |
350 | A key figure from the RemoteCube was not found in the planning area |
351 | Different values for a key figure |
352 | InfoSource &1 does not exist or there is no DataSource for it |
353 | Invalid data state in &1 |
354 | Internal error in &1 &2 |
355 | Key figure from planning area not found in RemoteCube |
356 | Characteristic from planning area not found in RemoteCube |
357 | Error deleting DataSource &1 |
358 | Error reading DataSource &1 |
359 | Compiled extraction structure for planning area &1 empty |
360 | Error generating or adjusting DataSource &1 |
361 | Error processing DataSources for planning area &1 |
362 | Wrong call parameter |
363 | DataSource does not exist or is not assigned to planning area |
364 | Inconsistency between DataSource &2 and planning area &1 |
365 | Error deleting a note text |
366 | Error updating the note anchor table for planning area &1 |
367 | Aggregate contains all characteristics of master planning obj. struct. &1 |
368 | Planning area &1 and DataSource &2 do not have same extraction structure |
369 | Neither DataSource nor planning area specified |
370 | DataSource &1 not found |
371 | DataSource not unique |
372 | Name of DataSource &1 does not start with standard prefix '&2' |
373 | Key figure description for key figure &1 is inconsistent |
374 | Key figure description for key figure &1 is inconsistent |
375 | '&' is not a valid name for a data source |
376 | No descriptions exist |
377 | No DataSource Selected |
378 | DataSource &1 replicated successfully in logical system &2 |
379 | DataSource &1 does not exist |
380 | An identical aggregate to '&1' already exists |
381 | Extraction structure &1 is used in multiple planning areas |
382 | Error when creating LC anchors |
383 | Option of zero fixing reset for key figure &1 |
384 | Zero fixing not allowed for key figure &1 |
385 | No time buckets profile selected |
386 | Characteristic value for characteristic &1 not filled |
387 | Error when changing the LC change indicator |
388 | Error when deleting an LC change indicator |
389 | Standard characteristics have been inserted |
390 | Internal Error: Invalid data structure for InfoCube &1 |
391 | Key Figure &1: Invalid property 'History Not Changeable' |
392 | No planning object selected |
393 | Functionality not useable for SNP planning object structures |
394 | Key Fig. &1: Inconsistency btwn master plan.obj.struct.and agg. |
395 | Planning object structure does not contain location characteristic |
396 | Planning object structure does not contain product characteristic |
397 | Planning version specified does not exist for planning area &1 |
398 | Values were ignored during saving |
399 | Not allowed to fix InfoCube key figure &1 |
400 | The name & has already been used |
401 | Name & already used |
402 | Planning area successfully copied |
403 | Enter From and To dates |
404 | To date must be greater than From date |
405 | "To" date must be earlier than or same as &1 |
406 | "From" date must be later than or same as &1 |
407 | "To" date must be earlier than or same as &1 |
408 | "From" date must be later than or same as &1 |
409 | No key figures selected |
410 | Your previous key figure-specific changes will be discarded |
411 | 'To date' has to be later than or equal to &1 |
412 | 'From date' has to be before or equal to &1 |
413 | Check the initialization time periods of the key figures |
414 | Key figure time frames are not within global time frame |
415 | From-date is outside the time period &1 to &2 of key figure &3 |
416 | To-date is outside the time period &1 to &2 of key figure &3 |
417 | From-date is outside the intialization time period &1 to &2 |
418 | To-date is outside the initialization time period &1 to &2 |
419 | From/To date adjusted to initialization period |
420 | *****************Messages for /SAPAPO/LCM_CONS_CHECK********************* |
421 | Storage buckets profile check |
422 | Storage buckets profile check |
423 | No time series used |
424 | Key figure initialization horizon check |
425 | liveCache anchor check and time series check |
426 | &1 Characteristic combinations without liveCache anchor &2 |
427 | &1 Characteristic combinations with liveCache anchor but w/o time series |
428 | Superfluous relationships |
429 | Characteristic combination without liveCache anchor |
430 | Check of time series relationships between &1 and &2 |
431 | Superfluous time series relationships between &1 and &2 |
432 | Missing relationships between &1 and &2 |
433 | Multiple relationships between &1 and &2 |
434 | Missing time series relationships between &1 and &2 |
435 | Time series initialization horizon check |
436 | Inconsistent time series initialization horizons |
437 | Missing characteristic combination(s) |
438 | Missing DP BOM relationship between &1 and &2 in liveCache |
439 | There are inconsistencies in pull rules of a DP BOM relationship |
440 | There are inconsistencies in parameter values of a DP BOM relationship |
441 | Error while locking data |
442 | Error while unlocking data |
443 | DP BOM relationships could not be repaired |
444 | DP BOM relationships repaired successfully |
445 | Error while reading the time buckets profile for the DP BOM relationships |
446 | Error while creating the time buckets profile for DP BOM relationships |
447 | Error while reading DP BOM relationships from liveCache |
448 | DP BOM relationship check |
449 | No liveCache anchor found |
450 | Execution of After Import method for planning area '&1' |
451 | Execution of before-export method for planning area '&1' |
452 | Planning area '&1', transport table '&2': Error copying |
453 | Planning area '&1', transport table '&3': &2 entries copied |
454 | Planning area '&1', transport table '&2': No entries |
455 | Planning area '&1': Errors copying to transport tables |
456 | Transport table '&1' generated |
457 | Transport object '&1' adjusted |
458 | All required transport tables exist |
459 | Transport object '&1' already adjusted |
460 | Execution of before-export method for planning object structure '&1' |
461 | Planning object structure '&1': Errors copying to transport tables |
462 | Planning object structure '&1', transport table '&3': &2 entries copied |
463 | Planning object structure '&1', transport table '&2': Errors copying |
464 | Planning object structure '&1' (client '&2' deleted in target system |
465 | Planning object structure '&1', transport table '&2': No entries |
466 | Execution of after-import method for planning object structure '&1' |
467 | Activation of standard InfoObjects |
468 | Error activating planning object structure '&1' |
469 | Planning object structure '&1' has to be activated manually |
470 | Planning object structure '&1' activated successfully |
471 | Activate the master planning object structure & first |
472 | After-import cannot be executed due to syntax errors in function group &1 |
473 | Transport table '&1' already exists |
474 | Table '&1' has been included in order '&2' |
475 | Table '&1' has not been included in any order |
476 | Namespace for table '&1' has been included in order '&2' |
477 | Namespace for table '&1' has not been included in any order |
478 | Execution of before-export method for storage buckets profile '&1' |
479 | Storage buckets prfl.'&1': Error occurred copying to transport table '&2' |
480 | Storage buckets profile '&1' successfully copied to transport table '&2' |
481 | Storage buckets profile '&1' (client '&2') deleted in target system |
482 | Execution of after-import method for storage buckets profile '&1' |
483 | Storage buckets profile '&1' successfully copied into active table |
484 | Storage buckets profile '&1': Error occurred when copying to active table |
485 | Planning area '&1' does not exist (to be deleted in target system) |
486 | After-import function '&1' was not executed |
487 | Order '&1' not flagged for subsequent activation |
488 | Planning object structure '&1' cannot be changed due to transport |
489 | Aggregate '&1' cannot be changed due to transport |
490 | Storage buckets profile '&1' cannot be changed due to transport |
491 | System check: For permission to import objects into target system |
492 | Objects are permitted to be imported into target system |
493 | Planning area '&1' cannot be changed due to transport |
494 | InfoCube &1 does not exist |
495 | Key figure &1 is not contained in InfoCube &2 |
496 | InfoObject &1 was copied from Content and activated |
497 | Planning object structure &1 not changed => Activation not necessary |
498 | BW aggregate '&1' deleted for planning object structure '&2' |
499 | BW aggregate '&1' could not be deleted for planning object structure '&2' |
500 | Storage buckets profile '&1' already exists |
501 | Planning area '&1' already exists |
502 | Currency '&1' is invalid |
503 | No logging |
504 | Displaying log |
505 | No log exists |
506 | Logs deleted successfully |
507 | key figure '&1' is double: In InfoCube and time series |
508 | Info object '&1' for parameter '&2' is not a key figure |
509 | &1 redundant key figure description(s) in LiveCache |
510 | Planning version &2 successfully initialized |
511 | Planning version could not be locked |
512 | Plan version &2 not initialized for planning area &1 |
513 | Storage buckets profile in liveCache contains unnecessary periods |
514 | Key fig. specific initialization only poss. for individual plng versions |
515 | Extended check of liveCache anchor |
516 | liveCache anchor without characteristics combinations |
517 | Characteristics combinations inconsistent |
518 | Planning object structure &1 does not belong to application DP/SNP |
519 | Planning object structure & is invalid |
520 | Planning area and DS have diff. extraction structures in target system |
521 | Extraction structure '&1' will be deleted in target system |
522 | DataSource '&1' has extraction structure '&2' in target system |
523 | Planning area '&1' has extraction structure '&2' in target system |
524 | DataSource '&1' does not exist in target system |
525 | DataSource '&1' inconsistent in target system |
526 | An internal error has occurred |
527 | Import paramter of AI method: '&1' = '&2' |
528 | DataSource '&1': No valid entry in table /SAPAPO/TSAREAEX |
529 | DataSource for planning area '&1' and planning object structure '&2': &3 |
530 | No DataSource found for planning area '&1' and PlObjStr '&2' |
531 | Check DataSources for planning area '&1' |
532 | DataSource '&1' is inconsistent and cannot be transported |
533 | No inconsistencies found for DataSource &1 |
534 | After import method &1 deactivated using /SAPAPO/SDP_TRANSP |
535 | No implementation &1 of BAdI &2 found |
536 | Implementation &1 of BAdI &2 is not active |
537 | Start of after-import method '&1' |
538 | Content of transportation table '&1' |
539 | DataSource '&1': Valid entry in table /SAPAPO/TTAREAEX |
540 | Inconsistency involving extraction structure '&1' detected |
541 | Extract structure generation: &1 entries selected from table ROOSFIELD |
542 | "Zero Allowed" setting is inconsistent for key figures &1, &2, &3 |
543 | "Negative Values Not Allowed" setting inconsist. for key fig. &1, &2, &3 |
544 | DataSource &1 has invalid setting '&2' for direct access |
545 | Administration lock failed for planning area &1 and planning version &2 |
546 | Administration unlock failed for planning area &1 and planning version &2 |
547 | Fixed values cannot be overwritten; saving is not possible |
548 | No lock monitor (SNP and DP) is active |
549 | No database entries found |
550 | &1 database entries deleted |
551 | Planning area & already exists |
552 | Master planning object structure & does not exist |
553 | Master planning object structure & is inactive |
554 | Data base connection & is invalid |
555 | All active aggregates were assigned |
556 | Background job to fill aggregate &1 is not yet complete |
557 | Planning version &1 for planning area &2 de-initialized successfully |
558 | Data of planning version & deleted successfully |
559 | A job to generate the combinations of &1 is not yet complete |
560 | A job for changing planning area &1 is not yet complete |
561 | Report is obolete. Use report &1 |
562 | Do you want to create fixing key figure '&1' for '&2' in the plan.area? |
563 | '&2' could not be determined for fixable key figure '&1' |
564 | &2 was able to be determined for fixable key figure '&1' |
565 | Active aggregates are missing in the planning area |
566 | Unavailable active aggregates were assigned to the planning area |
567 | Monitoring activated for planning area &1 and planning version &2 |
568 | Monitoring deactivated for planning area &1 and planning version &2 |
569 | CCMS Monitoring: Wrong Segment |
570 | Note anchors for planning area '&1' not yet converted (table '&2') |
571 | Note anchors for planning area '&1' already converted (table '&2') |
572 | Note anchors can be converted for planning area '&1' |
573 | Use report '/SAPAPO/TS_GEN_DOCTAB_CHECK' to correct the inconsistency |
574 | Note anchors for planning area '&1' cannot be converted |
575 | New note anchor table ('&1') generated for planning area '&2' |
576 | Note anchors for planning area '&1' converted successfully |
577 | Old note anchor table cannot be deleted |
578 | Old note anchor table not created or deleted already |
579 | Note anchors for planning area '&1' not yet converted (=> report '&2') |
580 | '&2' notes were successfully converted for planning area '&1' |
581 | Errors occurred during note conversion for planning area '&1' |
582 | Locks set |
583 | Planning version &1 is locked for planning area &2 by user &3 |
584 | Planning version &1 could not be locked for planning area &2 |
585 | No inconsistencies were found in table &1 |
586 | Selection &1&1 was renamed in &3&4 |
587 | Promotion &1 was renamed in &' |
588 | Start of program execution &1 (&2, &3) |
589 | End of program execution &1 (&2, &3) |
590 | No notes exist for planning area '&1' |
591 | Object &1 not in transport table; no import of object |
592 | Error while unlocking data |
593 | A new application log will be created, if you switch off the monitoring |
594 | &1 Logs deleted successfully |
595 | Key figure &1 is being used and cannot be removed |
596 | Locking conflicts happened |
597 | Planning object structure &1 must not be transported with TLOGO &2 |
598 | Number of key figures exceeds CBF limit (=20); see SAP Note 484144 |
599 | Characteristic "product" or "location" is not assigned |
600 | You are not authorized to use the selected function |
601 | Before-export method for planning book '&1' is being processed |
602 | Planning book '&1': errors copying to transport table |
603 | Planning book '&1', table /SAPAPO/CHRTCHTT: &2 entries copied |
604 | Error copying: planning book '&1' not found |
605 | Characteristics combinations will be loaded from a planning obj. struct. |
606 | Characteristics combinations will be loaded from an InfoProvider |
607 | Characteristics combinations will be loaded from a file |
608 | Characteristics combinations will be loaded from a BAdI |
609 | Aggregate '&1': Value ignored for '&2' '&3' '&4' |
610 | Aggregate '&1' deleted successfully |
611 | Aggregate '&1' was not deleted |
612 | Create Manually |
613 | Load to Worklist |
614 | Generate immediately |
615 | Generate in background |
616 | DP BOM: Invalid BOM Relation found for PPM/PDS in LC |
617 | DP BOM: Several Versions are active for &1 |
618 | DP BOM: Check for invalid BOM-relations of PPM/PDS executed |
619 | Extended DP BOM check will be carried out |
620 | Table &1: Field &2 = '&3' |
622 | Planning Object Structure &1 Check |
623 | Storage Buckets Profile &1 Check |
624 | Planning Area &1 Check |
625 | Standard SNP planning level &1 is inactive |
630 | Internal error during dynamic generation of data structure |
631 | Illegal call during dynamic generation of data structure |
640 | In key figure &1 &2 combination(s) with fixed values was/were found |
641 | In key figure &1 &2 combination(s) with negative values was/were found |
642 | In key figure &1 &2 comb. with values greater than &3 was/were found |
643 | Enter a larger value |
644 | There are no fixed values in the selected key figures |
645 | There are no negative values in the selected key figures |
646 | There are no values > &1 in the selected key figures |
650 | Changes to info object '&1' not allowed |
651 | Illegal use of conversion routine 'PRODU' |
652 | Not possible to use lowercase letters in DP |
653 | Characteristic &1: Data type '&2' not valid |
670 | InfoCube '&1' for planning object structure '&2' deleted successfully |
671 | InfoCube '&1' could not be deleted for planning object structure '&2' |
672 | Planning area '&1' (client '&2') deleted in target system |
673 | DataSource '&1' for planning area '&2' should be checked |
680 | No extraction structure found |
681 | Object catalog entry for extraction structure '&1' is correct |
682 | Object catalog entry for extraction structure '&1' was corrected |
683 | Object catalog entry for extraction structure '&1' was created |
690 | The key figure semantic is already used by key figure '&1'. |
700 | Key figure '&1' already assigned to aggregate '&2' |
701 | Characteristic values are not allowed to have this apostrophe: & |
712 | Maintain disaggregation key figure for calculation types P or I |
713 | Maintain time-based disaggregation key figure for calculation type K |
714 | Maintain time-based disaggreg. key figure for time-based disaggreg. 'K' |
717 | Standard SNP planning level created successfully |
718 | Standard SNP planning level &1 was activated for &2 |
719 | Standard SNP planning level &1 was deactivated for &2 |
720 | No aggregate chosen |
723 | Select a hierarchy structure with object type: location product |
724 | Select a hierarchy structure with object type: PPM or PDS |
725 | Select a hierarchy structure with object type: Resource |
726 | Select a hierarchy structure with object type: Time Dependent Loc. Prod. |
773 | Realignment table cannot be created |
776 | It is not allowed to delete the key figure |
779 | Exception created successfully |
780 | Exception successfully deleted |
788 | &1 uses 7.0 Datasources. |
789 | Export data source generated successfully |
790 | The export data source is old. Regenerate the source (planning area: &) |
791 | Data source & is not assigned to a planning area |
792 | Planning object structure deactivation failed |
793 | Planning object structure successfully deactivated |
794 | Table & does not exist |
795 | Error when writing new settings |
796 | Action terminated by user |
797 | No BW master table exists for &1. Corr. char values are not checked. |
798 | Log is corrupted, can not be displayed. Please delete it. |
800 | ---------------PERFORMANCE MESSAGES---------------------- |
801 | Problems in performance due to the large number of key figures |
802 | Performance problems due to large number of time periods |
878 | Planning object structure does not contain the InfoObject & |
890 | Planning object structure '&1' cannot be deleted (see long text) |
891 | Mast.plng.obj.struct. is used in plng area. Dependent objects are deleted |
892 | "&1" is an SNP-relevant planning object structure |
893 | Planning object structure '&1' cannot be deleted (see long text) |
897 | Assignment successfully saved |
899 | Save planning area before maintaining origin selection |
987 | Assignment successfully saved |