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