/SAPAPO/ATP - Availability check: ATP > 000, ALL > 200, PLN > 400
 The following messages are stored in message class /SAPAPO/ATP: Availability check: ATP > 000, ALL > 200, PLN > 400.
It is part of development package /SAPAPO/ATP in software component SCM-APO-ATP-EST. This development package consists of objects that can be grouped under "Availability Check".
 It is part of development package /SAPAPO/ATP in software component SCM-APO-ATP-EST. This development package consists of objects that can be grouped under "Availability Check".
| Message Nr ▲ | Message Text | 
|---|---|
| 000 | Dump for test purposes | 
| 001 | Error in ATP COM routine: &1 | 
| 002 | Deregistration of task handler for transaction &1 was unsuccessful | 
| 003 | Index exceeded: Requirement groups cannot be created | 
| 004 | Index exceeded: Requirements cannot be created | 
| 005 | Index exceeded: Requirement schedule lines cannot be created | 
| 006 | A requirement group with index &1 already exists | 
| 007 | A requirement with index &1 already exists | 
| 008 | A requirement schedule line with index &1 already exists | 
| 009 | The links to the preceding requirement group &1 are inconsistent | 
| 010 | Confirmation is only possible for the amount of ATP qty & | 
| 011 | The total confirmed quantity is greater than the order quantity | 
| 012 | Order date lies after the confirmation date | 
| 013 | Select a modifiable row | 
| 014 | &3: Internal table &1 contains no rows with index &2. | 
| 015 | No correlation calculation has been defined for requirement group type &1 | 
| 016 | Requirement index &1 does not exist in the reference table | 
| 017 | Requirement group index &1 does not exist in the reference table | 
| 018 | Requirements scheduling index &1 does not exist in the reference table | 
| 019 | Check instructions &3 / &4 does not exist for location product &1 / &2 | 
| 020 | Task handler for transaction &1 has not been registered | 
| 021 | Choose one record only | 
| 022 | Choose one record | 
| 023 | Quantity unit &1 could not be found | 
| 024 | The ATP time series were deleted successfully | 
| 025 | The ATP time series were generated successfully | 
| 026 | Error in determining logical system in business system group &1 | 
| 027 | Error in establishing RFC destination to logical system &1 | 
| 028 | Unidentified error during data reading in logical system &1 | 
| 029 | System error during data reading in logical system &1: &2&3 | 
| 030 | User-defined selection of substitutions is not possible | 
| 031 | Unidentified function &1 when calling up &2; programming error | 
| 032 | ATP group &1 not defined | 
| 033 | ATP group &1 and business event &2 not defined | 
| 034 | Category &1 not defined | 
| 035 | Check mode &1 and business event &2 not defined | 
| 036 | Table &1 locked by user &2; update not possible | 
| 037 | ATP check control not consistent | 
| 038 | Error while reading data to system &1 | 
| 039 | Communication error while reading data to system &1: &2&3 | 
| 040 | Product &1 does not exist | 
| 041 | Location &1 does not exist | 
| 042 | Check control for ATP group '&1' and business event '&2' is not defined | 
| 043 | ATP group '&1' has not been defined | 
| 044 | Check using requirments quantities for ATP group &1 is not supported | 
| 045 | Link &1 to liveCache produces errors | 
| 046 | Pegging area was not found for &1, &2, &3, &4 | 
| 047 | Master data for product &1 is incomplete | 
| 048 | No master data could be found for product ID &1 | 
| 049 | No master data could be found for location ID &1 | 
| 050 | Please select only one simulated requirement | 
| 051 | Please select a simulated requirement | 
| 052 | Error when entering the check sequence | 
| 053 | All persistent ATP objects have been deleted | 
| 054 | MATID &1 and LOCID &2 correspond to different business logical systems | 
| 055 | Check mode &2, business event &3 not supported in business system grp &1 | 
| 056 | All persistent DELTA anchors deleted | 
| 057 | No DELTA anchor object - GUID was found for &1, &2, &3, &4 | 
| 058 | DELTA anchor deleted successfully | 
| 059 | No business system could be determined for logical system &1 | 
| 060 | Anchor DELTA items deleted successfully | 
| 061 | All anchor DELTA items deleted successfully | 
| 062 | DELTA records with TrGuid &1 deleted successfully | 
| 063 | No order GUID could be determined for &1, &2, &3 &4 | 
| 064 | All ATP log files deleted | 
| 065 | Enter a valid activation parameters record | 
| 066 | No calendar could be found for time stream &1 | 
| 067 | Enter a check mode or maintain the product master | 
| 068 | Choose a valid function | 
| 069 | No valid rule strategy or rule was found | 
| 070 | Error occurred when reading APS order | 
| 071 | Invalid type &1 for liveCache connection | 
| 072 | Error occurred while reading planning object from liveCache | 
| 073 | Error occurred while reading delta records for a delta anchor | 
| 074 | Error occurred while reading planning delta for a document | 
| 075 | No product/location found for specified PegID | 
| 076 | No ATP group has been maintained for product &1 in location &2 | 
| 077 | No check mode has been maintained for product &1 in location &2 | 
| 078 | No master data exists for the product/location combination &1/&2 | 
| 079 | Total confirmed quantities exceed total receipts | 
| 080 | Total requirement quantities exceed the total receipts | 
| 081 | Receipts in the past were included | 
| 082 | Receipts in the past were not included | 
| 083 | Index exceeded: Requirements subgroup cannot be created | 
| 084 | Requirements subgroup with index &1 already exists | 
| 085 | Check mode &1 has not been defined | 
| 086 | Check mode &3 does not exist for product/location &1/&2 | 
| 087 | Entry does not exist for &1 in the global settings for the ATP check | 
| 088 | Requirements profile &1 has not been defined | 
| 089 | Importing Customizing data for the availability check is not allowed | 
| 090 | Product availability check is not supported or not relevant | 
| 091 | ATP groups could not be read for product &1 at location &2 | 
| 092 | Master data could not be read for product &1 at location &2 | 
| 093 | User-defined substitution selection results in more than one substitution | 
| 094 | No substitution for item &1/&2 with "rules immediately" | 
| 095 | No check instructions found for requirement &1 | 
| 096 | Results mode &1 not supported | 
| 097 | &4: No row with &2 = &3 in internal table &1 | 
| 098 | Scheduling call incorrect | 
| 099 | Error in an ATP Function | 
| 100 | Return: &1 &2 &3 &4 | 
| 101 | System error occurred when locking planning object &1 and basic method &1 | 
| 102 | Plng object &1 and basic method &2 have been locked (check not possible) | 
| 103 | Planning object &1 and basic method &2 could not be unlocked | 
| 104 | System error occurred when locking (&2) | 
| 105 | System error occurred when unlocking (&2) | 
| 106 | Error when reading ATP delta records | 
| 107 | Products &3 and &4 do not match for order/item &1/&2 | 
| 108 | Locations &3 and &4 do not match for order/item &1/&2 | 
| 109 | Account assignments &3 and &4 do not match for order/item &1/&2 | 
| 110 | &2 characteristics combinations adopted from planning area &1 | 
| 111 | Connection to liveCache does not exist. (&1) | 
| 112 | Error occurred while calling COM routine (connection to liveCache is OK) | 
| 113 | COM routine: Internal error (connection to liveCache is OK) | 
| 114 | Problem when calling liveCache | 
| 115 | Warning: Corrupt GUIDS exist - Display: Incorrupt GUIDS | 
| 116 | Choose a row | 
| 117 | Select a valid row | 
| 118 | Functionality available in next release | 
| 119 | Error occurred when initializing the variant | 
| 120 | Error when determining GUID for a characteristics combination | 
| 121 | Error when reading ATP Customizing | 
| 122 | Error when determining checking horizon for product &1 in location &2 | 
| 123 | Error when determining the order number for the order ID | 
| 124 | Error when determining the internal delta records | 
| 125 | Error when updating the internal delta records | 
| 126 | Error when writing the internal/external delta records | 
| 127 | No PegID could be determined for PosGuid | 
| 128 | No temporary quantity assignments can currently be displayed. | 
| 129 | No production with availability check; time is reset | 
| 130 | Filter display currently not possible | 
| 131 | Number of I/O nodes: &1 | 
| 132 | Background processing not yet implemented | 
| 133 | Comparision canceled during data record selection | 
| 134 | ATP check in system &1 not possible, since liveCache is not active | 
| 135 | Selection not found in liveCache | 
| 136 | One or more PEGIDs do not exist in liveCache | 
| 137 | Start immediately is only effective if rules-based ATP is active | 
| 138 | Error when determining the item ID | 
| 139 | Index overrun: scheduling cannot be created | 
| 140 | Unknown error | 
| 141 | ATP characteristics matrix could not be created during initialization | 
| 142 | The singles/totals records in liveCache are consistent (see long text) | 
| 143 | Not all delta anchor GUIDs (prod. allocs) could be decoded. | 
| 144 | The delta anchor GUID &1 cannot be decoded. | 
| 145 | Scheduling with index &1 already exists | 
| 146 | The scheduling index &1 does not exist in the reference table | 
| 147 | The ATP rules are not called up for item &1 | 
| 148 | An immediate rule evaluation is required for subitems | 
| 149 | "Use calculation profile" only makes sense in combination with RBA | 
| 150 | "Create remaining requirement" only accord. to prod. interch. master data | 
| 151 | No authorization for ATP area &1 and activity &2 | 
| 152 | ATP authorization area not found | 
| 153 | User &3 has no authorization for ATP area &1 and activity &2 | 
| 154 | "Create remain. req. according to InC" not poss.; InC MD not activated | 
| 155 | Check instruct. &1/&2 can only be maintained using transac. /SAPAPO/RSP01 | 
| 156 | You cannot activate third-party and RBA or production together | 
| 157 | Data inconsistency: The system could not create a (TPVS) context | 
| 158 | Shift of receipt buckets must be smaller than bucket size &1 | 
| 159 | Bucket data could not be determined for all pegging areas | 
| 160 | Change is not activated until reorganization of time series | 
| 161 | Categories &1 and &2 cannot both be included in one scope of check | 
| 162 | Error when reading categories | 
| 163 | Category &1 is neither stock, access or requirement | 
| 164 | A safety stock requirement is not permitted for category &1 | 
| 165 | Category &1 may not be used for ATP checks | 
| 166 | Confirmatzion of quantity &1 takes place via reassignment (ROC) | 
| 167 | Choose at least one basic method | 
| 168 | The data for product &1 and supplier &2 is not maintained completely | 
| 169 | Preselection of suitable substitutions activates immed. rule evaluation | 
| 170 | No connection to SAP liveCache &1 | 
| 171 | The aggregated temporary quantity assignments are consistent | 
| 172 | The aggregated temporary quantity assignments are inconsistent | 
| 173 | Reassignment of confirmations produces no confirmation | 
| 174 | Scope of check for ATP group &1 regarding event &2 initial | 
| 175 | Choose output format "ALV list" | 
| 176 | Without a remaining requirement, subitems cannot always be forced | 
| 177 | Internal error: negative index in RBA item &1 | 
| 178 | Confirmation assignment incompatible with storage loc., version, charact. | 
| 179 | Direct production necessary for subcontracting (but TPOP is not active) | 
| 180 | No MRP element found (are single records expanded?) | 
| 181 | No other MRP element with this number exists | 
| 182 | Enter the number of the MRP element first | 
| 183 | Call up search function first | 
| 184 | Error in BAdI /SAPAPO/ATP_CONSTRAINTS_OLTP | 
| 187 | "Merge Subitems" is only effective if "Create Subitem" is not marked | 
| 188 | EnhConfirmLogic is not supported with 'End of check without confirmation' | 
| 189 | Check control for business event &1 is not defined | 
| 190 | Substitutions created based on requested consolidation location in order | 
| 191 | Enter a check mode | 
| 192 | Periods for fiscal year variant &2 cannot be generated | 
| 193 | Enter a business event | 
| 194 | Maximum number of confirmations was set to 2 | 
| 195 | Rules for item &1 did not return a valid substitution | 
| 196 | Check whether ATP segments should be copied from main item to subitems | 
| 197 | System has set "Copy ATP Segment Data" field to value X | 
| 198 | No condition structure was found for order &1 and item &2 | 
| 199 | No characteristic values were found for order &1 and item &2 | 
| 200 | One of the necessary characteristics combinations was not found | 
| 201 | Characteristics combination for item &2/&3 was not found | 
| 202 | Unit conversion from '&1' '&2' into '&3' '&4' is not possible | 
| 203 | Characteristics combination unknown | 
| 204 | Consumption information could not be determined | 
| 205 | Unit &1 is unknown | 
| 206 | Conversion factor from &1 to &2 could not be determined | 
| 207 | Output unit &1 is unknown | 
| 208 | The target unit &1 is unknown | 
| 209 | Conversion of units without dimensions is not possible | 
| 210 | Product allocation group &1 does not exist | 
| 211 | The characteristics combination specified does not exist in this group | 
| 212 | &1 combinations with these values still exist | 
| 213 | The specified product allocation sequence entry does not exist | 
| 214 | No allocations are defined for the current characteristics combination | 
| 215 | The product allocation procedure &1 is not used | 
| 216 | The characteristics combination could not be determined | 
| 217 | No valid rows chosen in the table | 
| 218 | Error during scheduling in product allocation | 
| 219 | Start date lies after end date | 
| 220 | Product of item &2 not allocated | 
| 221 | Product not allocated | 
| 222 | No Help exists for the data element of the field &1-&2 | 
| 223 | Error when displaying Help for field &1-&2 | 
| 224 | Help cannot be displayed for field &1-&2 | 
| 225 | There is no product allocation assignment in the selected period | 
| 226 | Product allocation procedure or product allocation step missing | 
| 227 | Error creating characteristics combinations for collect. prod. allocs | 
| 228 | The displayed characteristics combination is deactivated | 
| 229 | Product allocation situations cannot be displayed (parameter missing?) | 
| 230 | The validity end is initial in step &1 with object &2 | 
| 231 | Enter special stock indicator | 
| 232 | Enter account assignment object | 
| 233 | End date specified already being used | 
| 234 | Product allocation group &1 has been locked by user &2 | 
| 235 | No general collective product allocations exist | 
| 236 | &2 char. combinations were created and &3 changed in prod. alloc. grp &1 | 
| 237 | Masking indicator for product allocation group &1 is empty | 
| 238 | Wildcard character &2 is not allowed for product allocation group &1 | 
| 239 | &2 characteristics combinations were copied to InfoCube &1 | 
| 240 | Error during scheduling in product allocation | 
| 241 | Product &1 unknown | 
| 242 | Source code for product allocations cannot be generated | 
| 243 | A new screen number could not be generated | 
| 244 | Processing terminated | 
| 245 | You do not have authorization to change objects | 
| 246 | Object &1 could not be locked | 
| 247 | Screen &2 in &1 already exists | 
| 248 | Screen &2 in &1 could not be saved | 
| 249 | Screen description is not correct | 
| 250 | Error while generating, but screen is saved | 
| 251 | Characteristic &2 from reference structure &1 cannot be converted | 
| 252 | No characteristics combinations are contained in prod. allocation grp &1 | 
| 253 | The transferred charact. catalog is empty - product alloc. not possible | 
| 254 | All product allocation characteristics have already been assigned | 
| 255 | All product allocation key figures have already been assigned | 
| 256 | No product/location transferred for one of the items to be checked | 
| 257 | Connection to InfoCube &1, version &2 (period &3, &4) defined | 
| 258 | Connection to planning area &1, version &2 (period &3, &4) defined | 
| 259 | Transferred time contains more than 999 periods | 
| 260 | Temporary quantity assignment could not be determined in liveCache &1 | 
| 261 | Temporary quantity assignment could not be saved in liveCache &1 | 
| 262 | Temporary quantity assignment could not be deleted | 
| 263 | Parameter missing when deleting temporary quantity assignment | 
| 264 | Temporary quantity assignment can only be determined from SAP liveCache | 
| 265 | Unknown deletion mode &1 for external temporary quantity assignments | 
| 266 | Error (&1) occurred when transferring product allocations | 
| 267 | Product allocations were copied to InfoCube &1, version &2 | 
| 268 | Product allocations of InfoCube &1, version &2 were copied | 
| 269 | Finish date lies before start date - the system will switch the dates | 
| 270 | Logical system &1 cannot be assigned to a system group | 
| 271 | Characteristics combinations could not be transferred | 
| 272 | Period &1 of product allocation group is not supported in the InfoCube | 
| 273 | Error occurred when reading InfoCube &1 | 
| 274 | Key figure categories are not the same | 
| 275 | RFC error occurred while accessing InfoCube in the Business Warehouse | 
| 276 | No master data has been defined for InfoCube &1 | 
| 277 | The parameters called contain errors | 
| 278 | Error occurred while writing data to the product allocation group | 
| 279 | Version &2 of InfoCube &1 could not be locked | 
| 280 | No connection exists between InfoCube &1 and a product allocation group | 
| 281 | Version &2 has not been defined for InfoCube &1 | 
| 282 | No connection has been defined in system group &1 | 
| 283 | There is no connection from product allocation group &1 to an InfoCube | 
| 284 | There is no connection from InfoCube &1 to product allocation group &2 | 
| 285 | Period &2 (FY variant &3) is not allowed for the InfoCube &1 | 
| 286 | You must enter a product allocation procedure | 
| 287 | You must enter an item number | 
| 288 | A product allocation procedure with item &2 already exists | 
| 289 | Product alloc. time series are stored directly in the planning area | 
| 290 | An error occurred when transferring characteristics combinations | 
| 291 | Copying confirmations from temporary qty assignments is not permitted | 
| 292 | Period &1 of product allocation group is not defined in the planning area | 
| 293 | A connection has not been defined for the product allocation group | 
| 294 | Fiscal year variant &1 has not been defined | 
| 295 | A fiscal year variant must be specified for period category &1 | 
| 296 | The fiscal year variant may not be specified | 
| 297 | There is no connection from plng area &1 to product allocation group &2 | 
| 298 | Version &2 is not defined for planning area &1 | 
| 299 | Make an entry in all required fields | 
| 300 | Conversion factor must be greater than 0 | 
| 301 | Product allocation step cannot be checked | 
| 302 | Date set to &1 | 
| 303 | Date set to &1 (last day of period &2). | 
| 304 | Check object validities when changing period type | 
| 305 | The product allocation group specified has not been defined | 
| 306 | You must specify a product allocation group | 
| 307 | More than one masking indicator (&2,&3) defined for &1 | 
| 308 | No wildcard character has been entered for collective product allocations | 
| 309 | Wildcard character '&1' is used for collective product allocations | 
| 310 | The product allocation group is already being used for another method | 
| 311 | Periodicity &2(&3) configured for product allocation group &1 | 
| 312 | Check date &2 (from &1) is not supported | 
| 313 | Characteristic of product allocation obj. missing from prod. alloc. group | 
| 314 | The characteristic product allocation object must be first in field list | 
| 315 | Product allocation group &1 can be used for product allocation | 
| 316 | Product allocation group &1 has no characteristics | 
| 317 | Some characteristics of product allocation group &1 are not allowed | 
| 318 | Some characteristics are not in the standard system | 
| 319 | No consumption interval has been maintained | 
| 320 | Consumption interval is being used | 
| 321 | Product allocations from past periods are used | 
| 322 | Product allocations from past periods are not used | 
| 323 | Consumption interval is ignored for discrete product allocation | 
| 324 | Generation error of the translation table | 
| 325 | Translation table &2 for product allocation group &1 was generated (&3) | 
| 326 | Generation error of access source code | 
| 327 | Access source code of product allocation group &1 was generated (&3) | 
| 328 | Generation error of display screens | 
| 329 | Display screen of product allocation group &1 generated (&3) | 
| 330 | &2 hierarchy entries exist for product allocation group &1 | 
| 331 | The hierarchy of product allocation group &1 could not be transferred | 
| 332 | &2 hierarchy entries of product allocation group &1 were transferred | 
| 333 | No control entries exist for product allocations procedure &1, &2 | 
| 334 | No active times have been defined for procedure &1, step &2 | 
| 335 | Validity end of product allocation is always the end of a period (&1, &2) | 
| 336 | Product allocation objects are entered in the hierarchy | 
| 337 | A counter of 0 is not allowed | 
| 338 | More than one step is not possible for discrete product allocations | 
| 339 | In step &1, the validity end of object &2 is &3 instead of &4 | 
| 340 | Product allocation object &1 is not contained in the hierarchy | 
| 341 | No allocation quantities defined for product allocation object &1 | 
| 342 | No steps defined in product allocation procedure &1 | 
| 343 | You must enter a description for the product allocation group | 
| 344 | Prod. alloc. group &1 is already being used in this prod. alloc. proced. | 
| 345 | You must enter a field name | 
| 346 | Field &1 is not used for the collective allocation search | 
| 347 | A field with item &2 already exists | 
| 348 | No period category is specified for product allocation group &1 | 
| 349 | No check date specified for product allocation group &1 | 
| 350 | Characteristic &1 is not contained in the field catalog | 
| 351 | Some characteristics of product alloc. grp &1 missing from field catalog | 
| 352 | Product allocation group &1 is still being used | 
| 353 | Type of charact. &1 of product allocation group &2 cannot be determined | 
| 354 | &2 characteristics combinations were copied to the planning area &1 | 
| 355 | InfoCube &1 does not exist | 
| 356 | No planning parameters have been maintained for InfoCube &1 | 
| 357 | Version &2 of InfoCube &1 has not been defined | 
| 358 | Characteristic &2 does not exist in the InfoCube &1 | 
| 359 | Key figure &2 does not exist in the InfoCube &1 | 
| 360 | Characteristic &2 does not exist in product allocation group &1 | 
| 361 | Key figure &2 cannot be used for a product allocation group | 
| 362 | Characteristic &2 does not exist in planning area &1 | 
| 363 | Key figure &2 does not exist in planning area &1 | 
| 364 | No results can be displayed for the procedure selected | 
| 365 | No row with a product allocations procedure was selected | 
| 366 | Product allocation procedure &1 does not exist | 
| 367 | Customizing settings in product allocations control are missing | 
| 368 | Planning area &1 does not exist | 
| 369 | Version &2 of planning area &1 has not been defined | 
| 370 | Access source code must be generated for the translation table | 
| 371 | Characteristics combinations must be loaded into the table again | 
| 372 | Search help for translation table must be regenerated | 
| 373 | Display screen for translation table must be generated again | 
| 374 | Generation status of product allocation groups is up-to-date | 
| 375 | Product allocations must be deleted with the characteristic values | 
| 376 | No planning parameters defined for planning area &1 | 
| 377 | Planning area &1 has not been defined for period &2/FY variant &3 | 
| 378 | Product allocations were transferred to planning area &1, version &2 | 
| 379 | Product allocations for planning area &1, version &2 were transferred | 
| 380 | At least one object to be reset must be selected | 
| 381 | Characteristics combinations to be changed could not be locked | 
| 382 | You must choose at least one action | 
| 383 | Aggregation/disaggregation not possible | 
| 384 | There is no connection from planning area &1 to a product alloc. group | 
| 385 | Error reading planning area &1 | 
| 386 | RFC error accessing the planning area in SAP BW | 
| 387 | No master data defined for planning area &1 | 
| 388 | It is not possible to delete characteristics combination &3 | 
| 389 | &1 of &2 selected characteristics combinations were deleted | 
| 390 | Error generating internal objects | 
| 391 | No entries were chosen for processing | 
| 392 | &1 of &2 selected characteristics combinations were changed | 
| 393 | This function cannot be called for list items | 
| 394 | &1 of &2 selected product allocation assignments were deleted | 
| 395 | Product allocation procedure and step are unknown | 
| 396 | Product alloc. group cannot be determined for characteristics combination | 
| 397 | Function cannot be executed in the chosen row | 
| 398 | This function can only be called for list items | 
| 399 | Function code &1 is not supported | 
| 400 | Error occurred when importing from the shared buffer: &1, &2 | 
| 401 | Characteristics in characteristics view &1 no longer valid - update | 
| 402 | Characteristic view cannot be deactiv./activated - transaction data exist | 
| 403 | Intersection of the characteristics for the products is empty | 
| 404 | Product &1 has already been assigned to a characteristics view | 
| 405 | Characteristics view &1 cannot be deleted - product(s) is (are) active | 
| 406 | Active product &1 cannot be deleted - transaction data exists | 
| 407 | Status of characteristic &1 cannot be changed - product is active | 
| 408 | Product &1 cannot be deactivated/activated; data exists | 
| 409 | Characteristic &1 was removed | 
| 410 | Characteristic &1 was added | 
| 411 | A characteristics view with the name &1 already exists | 
| 412 | You must enter a name for the characteristics view | 
| 413 | You must enter a material number | 
| 414 | Product &1 does not exist | 
| 415 | No characteristics assigned to product &1 | 
| 416 | No entry exists for product selection | 
| 417 | No entry exists for location selection | 
| 418 | By adding product &1, the intersection of the characteristics is empty | 
| 419 | Product &1 does not have all characteristics of the active charact. view | 
| 420 | Characteristic does not exist | 
| 421 | No connection defined from product alloc. group &1 to the planning area | 
| 422 | Not all characteristics/key figures are connected to the planning area | 
| 423 | Connection of characteristics/key figures is incomplete | 
| 424 | The connection is defined completely | 
| 425 | Version &2 of the planning area could not be locked | 
| 426 | The planning area &1 could not be locked | 
| 427 | Product allocation group &1 can be used for transportation planning | 
| 428 | No requirement was transferred for the product allocation step | 
| 429 | Characteristic is not contained in the intersection | 
| 430 | There is no connection from product alloc. group &1 to a planning area | 
| 431 | Characteristics and info objects are consistent (length of the values) | 
| 432 | The info object &2 used in the connection no longer exists | 
| 433 | The lengths of characteristic &1 and info object &3 differ | 
| 434 | Characteristic &1 is an IBASE char. and is not allowed in the connection | 
| 435 | Config. char. (IBase) for collective prod. alloc. search cannot be used | 
| 436 | A product allocation assignment does not exist | 
| 437 | Update not possible | 
| 438 | Product &1 has to be deactivated before it can be deleted | 
| 439 | No product/location combinations could be found | 
| 440 | Correlation profile &1 is not defined | 
| 441 | The BOM explosion for &1 (&2) could not determine any components | 
| 442 | Select the column incoming orders quantity in a valid row | 
| 443 | No data import for direct connection from &1 to several units | 
| 444 | Different units of measure when changing planning object &1 | 
| 445 | No time series found for this selection | 
| 446 | Direct connection of product allocation group &1 to planning area defined | 
| 447 | Planning area &1 is currently locked by user &2 | 
| 448 | Period type of PAL does not correspond to period type of InfoCube | 
| 449 | Period start is after the period end | 
| 450 | Lock for changing persistent data from reqmts group &1 not received | 
| 451 | No schedule line found for item &1, reqmts date &2 and reqmts qty &3 | 
| 452 | System error when attempting to lock requirements group &1 | 
| 453 | Data from several transactions is processed during one transaction | 
| 454 | No order item data for transaction &1 found in DB | 
| 455 | Persistent data for order item &1 not found in DB | 
| 456 | Invalid parameter values when calling function module &1 | 
| 457 | Order items read belong to different requirements groups | 
| 458 | No order item data found in the ATP tree structures | 
| 459 | Commit work completed: Restart update function &1 | 
| 460 | No requirements group found in database for this selection | 
| 461 | Initial key fields are not allowed | 
| 462 | It is not possible to write passive ATP tree structures | 
| 463 | No subsequent business transaction defined for key &1/&2/&3 / &4 | 
| 464 | Requirement group information for ATP tree structure is missing | 
| 465 | Internal error in function module &1 | 
| 466 | Error in correlation: Complete delvry grp (&1, &2) lost its confirmation | 
| 467 | Internal error: Item &1/&2 | 
| 468 | Status of characteristic &1 has not been changed due to existing rule | 
| 469 | Product cannot be deactivated/activated because data exists | 
| 470 | Product cannot be added because data exists | 
| 471 | Product cannot be added because rules exist | 
| 472 | Product has been added; characteristics (with rules) have been deleted | 
| 473 | According to SAP R/3, an entry is not required for characteristic &1 | 
| 474 | 'Time Series' Status Cannot be Combined with 'Only Used for Rules' Status | 
| 475 | Invalid time stamp for the product allocation assignment | 
| 476 | System cannot determine a period for product allocation group &1 | 
| 477 | Only one period allowed - date set to period limit | 
| 478 | Rounding not active in packaging specification of rounding procedure &1 | 
| 479 | Invalid quantity to be rounded &1 | 
| 480 | Invalid rounding result &1 | 
| 481 | Invalid rounding call for rounding procedure &1 | 
| 482 | Invalid rounding object for product &1 location &2 | 
| 483 | GUID conversion during rounding not possible for &1 &2 | 
| 484 | Error when building field catalog during rounding of order &1 item &2 | 
| 485 | Rounding executed for product &1 location &2 value &3 | 
| 486 | Rounding result &1 | 
| 487 | No min. packaging size defined for packaging spec. of rounding proced. &1 | 
| 488 | Invalid quantity conversion of &1 to &2 during rounding with material &3 | 
| 489 | A rounding procedure does not exist for material &1 location &2 | 
| 490 | No valid source found for &3/&1/&2 | 
| 491 | TPOP: No supplier determined for product &1 in location &2 | 
| 492 | Product &1 is not sales-relevant in location &2 | 
| 493 | Rounding display not possible | 
| 494 | Select at least one rounding procedure or rounding profile | 
| 495 | Select either a rounding procedure or a rounding profile | 
| 496 | A field catalog does not exist for rounding profile & | 
| 497 | Packaging specification cannot be determined for rounding procedure &1 | 
| 498 | Rounding to sales unit of measure &1 failed | 
| 499 | No unit of measure specified for rounding display | 
| 500 | Item &1: No result for check of product &2 in location &3 | 
| 501 | Shortage for neutral results &1 (product &2 in location &3) | 
| 502 | Enter a valid Alert Monitor profile | 
| 503 | Maintain an ATP profile in profile maintenance of the Alert Monitor | 
| 504 | Correlation profile and BAPI interface settings contradict each other | 
| 505 | No TPOP for product &1 in location &2 due to consolidation | 
| 506 | Invalid POSGUID: '&1'. | 
| 507 | Invalid POSGUIDs: '&1' and '&2'. | 
| 508 | The starting POSGUID '&1' is bigger than the ending POSGUID '&2'. | 
| 511 | Choose single record display first before changing entries | 
| 512 | The new settings are active when you call the results overview again | 
| 520 | Continue w/o characteristic value assignment - no check at char. level | 
| 521 | Error reading product substitution orders of order &1 | 
| 530 | Maximum number of possible substitutions: &1 - select again | 
| 531 | Maximum number of selected pegareas: &1 - restrict your selection | 
| 550 | Try to activate update buffer for temp. qty assignments several times | 
| 556 | Use the transaction /SAPAPO/BOPIN to change the ATP situation | 
| 557 | The ATP situation can not be changed here | 
| 559 | ***** PARB messages ***** | 
| 560 | Object with ID &1 &2 already exists | 
| 561 | Object with ID &1 &2 does not exist | 
| 562 | Item &1 already included in ProductAvailabilityRequirement &2 | 
| 563 | Missing anchor &1 (DELPS &2) or wrong item order in Table REQUIREMENTS | 
| 570 | ***** Customizing messages ***** | 
| 571 | Only existing SAP standard ATP categories may be referenced | 
| 572 | Bucket logic &1 is only compatible with Bucket TS SPACE or &2, not &3 | 
| 573 | Shifting receipt elements is only meaningful for conservative buckets | 
| 574 | More than one bucket per day only meaningful when "Accept time" active | 
| 575 | Reference category &1 does not exist | 
| 576 | Data is being copied from reference category &1 | 
| 577 | Specify a value either for the field '&1' or for '&2' | 
| 578 | Bucket ID &1 not defined in global settings for availability check | 
| 580 | RBA fields changed to display mode | 
| 581 | After activating special PO categories, consider dependent Customizing | 
| 600 | ***** XPRA messages ***** | 
| 601 | No logical system for business system group &1 | 
| 602 | &1 of &2 mapping entries were copied for order items | 
| 603 | XPRA is terminated as no upgrade is active | 
| 604 | XPRA is not planned for source release &1 | 
| 605 | R/3 object type of category &1 changed from &2 to &3 | 
| 606 | R/3 object type of category &1 could not be changed | 
| 607 | R/3 object type '&1' does not correspond to type '&2' of category '&3' | 
| 650 | Requirement not found for exclusion & & & | 
| 660 | Requirements grouping & contains items with different business processes | 
| 661 | Item &/& may only exist in one requirements grouping | 
| 662 | Override location from item & & deleted due to multi-item sing. del. loc. | 
| 663 | Consolidation loc. from item & deleted due to multi-item sing. del. loc. | 
| 664 | Only main items can be checked in the case of reqmnts grouping (item &/&) | 
| 665 | MISL: No common loc. can be detrmind; check complte req. group for &1 &2 | 
| 666 | MISL: No common loc. can be determined; check complete requirements group | 
| 667 | MISL: No check of item &1 &2 - MISL activated but MISL-Rule is missing | 
| 668 | |
| 670 | Logic Error in BAdI &1, output inconsistent - no processing possible | 
| 680 | Unable to get data without a transaction GUID | 
| 681 | Error while reading data with transaction GUID &1 | 
| 682 | Value of modific. counter for doc. &1 in SCM is: &2, but should be: &3 | 
| 686 | Document &1 from system &2 is currently in process &3 &4 | 
| 687 | Object &1 &2 from system &3 has not been replicated to SCM | 
| 701 | Objects for selection not found | 
| 702 | From-date later than to-date | 
| 703 | Missing characteristics combination in planning area & | 
| 750 | 'Consume Oldest Period First' strategy used during backward consumption | 
| 751 | 'Consume Newest Period First' strategy used during backward consumption | 
| 799 | Maintain a business event for location &1 | 
| 800 | Incorrect setup of table & | 
| 801 | The confirmed quantity - & & - can only be reduced | 
| 802 | On & & only & & available | 
| 803 | Enter date or delete quantity | 
| 804 | Please note that the customer wants complete delivery | 
| 805 | Delivery is only possible on & or later | 
| 806 | No goods accepted on &1. The next possible date is: &2 | 
| 807 | The delivery date &1 &2 cannot be kept | 
| 808 | The specifications are valid for the entire item | 
| 809 | Maintain the unit of measure displayed for product &1 and location &2 | 
| 810 | Conversion of &1 to &2 is not possible for product &3 in location &4 | 
| 811 | At least one basic method has caused a date shift | 
| 812 | Only & & are available altogether, & & are already assigned | 
| 815 | ATP check for sublocation and/or version not activated | 
| 850 | An error occurred when calling a method of the tree model | 
| 851 | Program error in reqmt origin screen: Node and subnode cannot be the same | 
| 888 | Planning area is connected to more than one production allocation group | 
| 899 | ATP-Huber.: Do not give specific user, SY-UNAME is used |