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