/SCMTMS/PLN_VSR_OL
341 mesaj (bu uygulama alanında)
Her satırda SAP mesaj numarası ve kaynak çıktısındaki İngilizce metin yer alır. Derin bağlantı için örn. #msg-123 kullanın.
| Mesaj | Mesaj metni |
|---|---|
| 1 | &1 &2 is locked by user &3 |
| 2 | &1 was changed in a parallel session; save your data and refresh |
| 3 | Stop at &1 was changed in a parallel session; save your data and refresh |
| 4 | &1 &2 was changed in a parallel session; save your data and refresh |
| 5 | You can only create TPs for one req doc. or req docs from one pred. doc. |
| 10 | Authority check failed for &1 &2 |
| 11 | Context: No authorization for &1 &2 |
| 12 | No &1 authorization for &2 &3 |
| 13 | Alert could not be created for category &1 |
| 14 | You have to select at least one freight unit for optimization |
| 15 | No transportation lanes found for your selection |
| 16 | Select at least one vehicle or schedule for optimization |
| 17 | Condition calculation for (un)loading duration failed, default is used |
| 18 | No planning-relevant freight unit was selected |
| 19 | Strategy &1 is not a VSR strategy |
| 20 | Strategy &1 is not a VSS strategy |
| 21 | Strategy &1 cannot be used to select schedules or routes |
| 22 | Strategy &1 can only be used for schedule selection |
| 30 | Compartment &1 is overloaded (total &2 exceeds available &3 &4) |
| 31 | Resource/equip. type &1 is overloaded (total &2 exceeds available &3 &4) |
| 32 | MTr combination &1 is overloaded (total &2 exceeds available &3 &4) |
| 33 | Booking &1 is overloaded (total &2 exceeds available &3 &4) |
| 34 | No direct load allowed for MTr &1 |
| 35 | One order condition violated for compartment type &1 seq &2 on MTr &3 |
| 36 | No. of parallel freight ord.(&1) exceeds max. limit (&2) for multires. &3 |
| 37 | Alert for multiresource violation could not be created for &1 &2 |
| 38 | Package &1 is overloaded (total &2 exceeds available &3 &4) |
| 39 | Document has an overload situation; check utilization |
| 40 | All checks executed successfully |
| 41 | Document &1 is inconsistent |
| 42 | Consistency check failed |
| 43 | &1 is overloaded; utilization is &2% |
| 44 | Combined capacity of the document has a utilization of &1 |
| 50 | &1 alternative transportation proposals found |
| 61 | &1 excluded because not relevant for automatic planning |
| 62 | &1 excluded because document is planned on an excluded capacity document |
| 63 | Stage &2 of document &1 excluded because it is blocked for planning |
| 64 | &1 excluded because the document has status &2 |
| 65 | &1 excluded because assigned resource/equip. type is blocked for planning |
| 66 | Resource &1 excluded because it is blocked for planning |
| 67 | &1 excluded because optimizer can't consider the stage sequence type |
| 68 | &1 excluded because doc. has at least one stop with an undefined location |
| 69 | &1 excluded because schedule data status is "Data is Not Up-to-Date" |
| 70 | &1 excluded because capacity document is before planning horizon |
| 71 | &1 excluded; there is at least one item with fixed req. doc. assignment |
| 72 | Equip. type &1 (group &2) excluded because it is blocked for planning |
| 73 | &1 excluded because items are locally distributed into compartments |
| 74 | &1 filtered because trailer unit is created via freight unit building |
| 75 | Enter a maximum number of transportation proposals greater than 0. |
| 100 | ==> Shortcut related messages |
| 101 | No freight units have been built |
| 200 | ==> Interactive planning related messages |
| 201 | Planning not possible, &1 is already planned |
| 202 | No consolidation allowed for &1 |
| 203 | &1 cannot be assigned to res. &2; it does not have capacity |
| 204 | &1 can only be coupled to veh. res/veh. type; &2 is passive veh. res/type |
| 205 | &1 is already coupled to a vehicle resource or vehicle type |
| 206 | &1 can only be coupled to passive veh. res.; &2 is not a pass. veh. res. |
| 207 | Assignment of &1 to &2 not possible |
| 208 | For &1 with MTr &2 no appropriate transporation lane exists |
| 209 | Planning not possible; &1 is blocked |
| 210 | &1 may not be loaded directly |
| 211 | &1 is fixed |
| 212 | &1 cannot be coupled to passive vehicle resource or vehicle type &2 |
| 213 | &1 cannot be coupled to &2 |
| 214 | For schedule &1 no departure times exist |
| 215 | Planning for &1 not possible |
| 216 | Missing pick-up or delivery window for &1 |
| 217 | Missing pick-up/delivery window for &1; use planning horizon as default |
| 218 | Depot location of vehicle &1 is not considered within freight order &2 |
| 219 | Pick-up window of &1 violates appointment window of &2 |
| 220 | Delivery window of &1 violates appointment window of &2 |
| 221 | &1 assigned to &2 |
| 222 | Location &1 is not yet part of &2 |
| 223 | No transshipment location of &1 is part of &2 |
| 224 | &1 extended for location &2 |
| 225 | Means of transport of &1 changed |
| 226 | Container &1 added to &2 |
| 227 | Vehicle &1 added to &2 |
| 228 | &1 created for vehicle &2 |
| 229 | &1 created |
| 230 | &1 removed from &2 |
| 231 | Vehicle resource &1 has MTr with 'Schedule' checkbox selected |
| 232 | &1 is not planned and cannot be unplanned |
| 233 | Stop &1 of &2 cannot be assigned to stop &3 of &4 |
| 234 | No common transshipment location for source locations found |
| 235 | No common transshipment location for destination locations found |
| 236 | &1 is already assigned to container &2 |
| 237 | &1 cannot be used for manual planning |
| 238 | No usable departure time found |
| 239 | Planning not possible; check selected objects |
| 240 | Planning not possible; multiple FOs with active vehicle passed |
| 241 | &1 removed from planning |
| 242 | &1 coupled to &2 at location &3 |
| 243 | Planning not possible; &1 is canceled |
| 244 | &1 cannot be coupled to &2 |
| 245 | &1 uncoupled from &2 at location &3 |
| 246 | Planning not possible; stops are coupled |
| 247 | Stop cannot be removed because of coupling to other freight orders |
| 248 | &1 uncoupled from &2 |
| 249 | Proposed transportation mode of FU &1 does not match &2 |
| 250 | Vessel &3 of FU &1 does not match vessel of &2 |
| 251 | Voyage &3 of FU &1 does not match voyage of &2 |
| 252 | Flight code &3 of FU &1 does not match flight code of &2 |
| 253 | Proposed carrier &3 of FU &1 does not match carrier &4 of &2 |
| 254 | Proposed transp. mode of FU &1 doesn't match resource/equipment type &2 |
| 255 | Proposed vessel &3 from FU &1 copied to &2 |
| 256 | Proposed flight code &3 from FU &1 copied to &2 |
| 257 | Proposed voyage &3 from FU &1 copied to &2 |
| 258 | Proposed means of transport of FU &1 does not match &2 |
| 259 | Proposed means of transport of FU &1 doesn't match res./equip. type &2 |
| 260 | Transportation mode category of FU &1 does not match &2 |
| 261 | Cannot create freight order for &1 due to missing proposals |
| 262 | Cannot assign requirements of &1 to elements of category &2 |
| 263 | Assign requirements of &1 to elements of category &2 |
| 264 | Means of transport changed from &1 to &2 |
| 265 | Multiple stages of &1 assigned to same resource or equipment type &2 |
| 266 | Multiple stages of &1 assigned to same &2 |
| 267 | &1 has shipping type &2 and must not be planned separately |
| 268 | Enter a valid combination of shipping types |
| 269 | FU stages within container have different consignees |
| 270 | Consolidated on-carriage for &1 has different destination locations |
| 271 | Cannot create freight booking for &1 due to missing proposals |
| 272 | Container usage for consolidated on-carriage is possible only for FOs |
| 273 | No freight units consolidated within container |
| 274 | Cannot add container &1 to &2 |
| 275 | Different freight agreement ID in forwarding order and freight booking |
| 276 | Cannot plan multiple stages of freight document &1 |
| 277 | Cannot plan uncontrolled freight units with controlled freight units |
| 278 | Default freight document type is not available; cannot plan stages |
| 279 | Cannot change first and last location within location sequence |
| 280 | Different carriers maintained for the selected freight unit stages |
| 281 | Only one pickup location is permitted when you create a freight booking |
| 282 | Only one delivery location is permitted when you create a freight booking |
| 283 | Service level at POL of type &1 does not match the given stages |
| 284 | Service level at POD of type &1 does not match the given stages |
| 285 | Only subsequent stages of &1 can be planned together |
| 286 | Assignment is not possible; location &1 is not part of freight booking &2 |
| 287 | You cannot assign stages to booking &1; pick-up locations do not match |
| 288 | You cannot assign stages to booking &1; ports of loading do not match |
| 289 | You cannot assign stages to booking &1; ports of discharge do not match |
| 290 | You cannot assign stages to booking &1; delivery locations do not match |
| 291 | You can only use schedules that have gateways |
| 292 | Select a freight order with a passive vehicle |
| 293 | Select a freight order with a vehicle |
| 294 | Multiple locations found for UN/LOCODE &1 within order &2 |
| 295 | Location for UN/LOCODE &1 not found in order &2 |
| 296 | Complete the location data for freight unit stage &1 |
| 297 | Planning failed; no data changed |
| 298 | Freight order &1 created |
| 299 | Freight order &1 created for vehicle &2 |
| 300 | Freight booking &1 created |
| 301 | Location &1 is not part of schedule &2 |
| 302 | Stage &1 cannot be planned with schedule &2; locations are different |
| 303 | Assignment not possible |
| 304 | Error while creating freight booking for schedule &1 |
| 305 | Error while creating freight order for schedule &1 |
| 306 | &1 schedule departures selected |
| 307 | &1 freight documents created |
| 308 | Cannot use location &1 of booking &2; service level is &3 |
| 309 | Freight order &1 is already assigned to an active vehicle |
| 310 | Trailer &1 is already assigned to a passive vehicle |
| 311 | Planning not possible; stages already planned |
| 312 | Error while creating freight order |
| 313 | Coupling not possible; trailer already coupled for these stages |
| 314 | Transportation unit &1 created for vehicle &2 |
| 315 | Error while creating transportation unit |
| 316 | Vehicle change not possible; remove original vehicle first |
| 317 | Transportation unit &1 created |
| 318 | Error while creating transportation unit |
| 319 | Transportation unit &1 is already assigned to freigth order &2 |
| 320 | Error while converting penalty costs from condition &1; default is used |
| 321 | Only uncoupling intermediate stages is not possible |
| 322 | Document type &1 can not be used for planning operations |
| 323 | Freight order for pick-up cannot be used because of service level |
| 324 | Freight order for delivery cannot be used because of service level |
| 325 | Freight order cannot be created; enter a location |
| 326 | Planning not possible; status &1 is active for &2 |
| 327 | Res./equip. type can't be assigned; freight order is linked to a schedule |
| 328 | Location &1 cannot be deleted; coupling activities at location &1 |
| 329 | Location &1 cannot be deleted; uncoupling activities at location &1 |
| 330 | Sequence cannot be changed; loading location after unloading location |
| 331 | Contract basis &1 not found |
| 332 | Driver &1 added to freight order &2 |
| 333 | Coupling of trailer unit &1 at location &2 is not allowed |
| 334 | Coupling of trailer unit &1 at location &2 not allowed; no loading act. |
| 335 | Re-coupling of trailer unit &1 not allowed at location &2; not swapped |
| 336 | Transportation mode categories of vehicle &1 and document &2 do not match |
| 337 | Transp. mode categories of requirement and capacity document don't match |
| 338 | Trailer unit &1 cannot be assigned; freight order is linked to a schedule |
| 339 | Railcar unit &1 cannot be assigned; freight order is linked to a schedule |
| 340 | Trailer unit &1 cannot be assigned; it is linked to a schedule |
| 341 | Railcar unit &1 cannot be assigned; it is linked to a schedule |
| 342 | Assignment not possible; freight order &1 is linked to a schedule |
| 343 | Assignment not possible; trailer unit &1 is linked to a schedule |
| 344 | Assignment not possible; railcar unit &1 is linked to a schedule |
| 345 | Enter a valid means-of-transport combination for freight order &1 |
| 346 | Freight booking cannot be created; stage type for stage &1 missing |
| 347 | Assignment not possible; cannot add further pick-up/delivery locations |
| 348 | Assignment of &1 to &2 not possible; no common pick-up/delivery locations |
| 350 | &1 loaded into &2 at location &3 |
| 351 | &1 unloaded from &2 at location &3 |
| 352 | &1 cannot be assgined to &2 |
| 353 | Proposed carrier &3 of container unit &1 does not match carrier &4 of &2 |
| 354 | Proposed means of transport of container unit &1 does not match &2 |
| 355 | Vessel &3 of container unit &1 does not match vessel of &2 |
| 356 | Voyage &3 of container unit &1 does not match voyage of &2 |
| 357 | Flight code &3 of container unit &1 does not match flight code of &2 |
| 358 | Container unit &1 cannot be assgigned to trailer unit &2 |
| 359 | Container unit &1 cannot be assgigned to railcar unit &2 |
| 360 | Cannot plan uncontrolled container units with controlled container units |
| 361 | &1 unassigned from &2 |
| 362 | Stage cannot be unassigned; pre-/succeeding stages are still assigned |
| 363 | Stage cannot be split because of existing assignments |
| 364 | Transportation mode categories of schedule &1 and doc. &2 inconsistent |
| 365 | Extension of freight order &1 not possible; it is linked to a schedule |
| 366 | Cannot insert new locations; railcar unit &1 already assigned to FO |
| 367 | Container unit &1 created |
| 368 | Error while creating container unit |
| 369 | Enter freight agreement ID in forwarding order &1 of freight unit &2 |
| 370 | Enter freight agreement ID in forwarding order &1 of container unit &2 |
| 371 | Cannot assign container to container unit; equipment type inconsistent |
| 372 | Means of transport combination in FO &1 not defined in Customizing |
| 373 | FO not planned; choose an FO with an FO type that is linear and direct |
| 374 | Assignment not possible; cannot add further requirements to document &1 |
| 375 | Location cannot be added to &1 because location sequence is fixed |
| 376 | Locaction cannot be deleted from document &1; location sequence fixed |
| 377 | Cannot remove location &1 from doc. &2; FU or TU still assigned |
| 378 | Freight doc. cannot be created; departure of schedule &1 is not valid |
| 379 | Planning not possible; documents cannot be assigned to each other |
| 380 | Stop cannot be moved because further documents are assigned |
| 381 | Planning not possible; invalid data passed to planning operation |
| 382 | Location seq. synchronization of doc. &1 not possible; stops are assigned |
| 383 | Location cannot be deleted because further documents are assigned |
| 384 | Cannot assign requirement to document &1; document is fixed |
| 385 | Locaction cannot be moved within document &1; location sequence is fixed |
| 386 | Driver assignment per stage not possible for road freight order &1 |
| 387 | Assignment not possible; no default truck defined for driver &1 |
| 388 | Cannot create doc.; document type &1 is not relevant for driver planning |
| 389 | Assignment not possible; cannot change dest. location of preceding stage |
| 390 | Assignment not possible; cannot change src. location of succeeding stage |
| 391 | Assignment not possible; cannot change source location of first stage |
| 392 | Assignment not possible; cannot change dest. location of last stage |
| 393 | Assignment not possible; other req. documents already assigned to doc. &1 |
| 394 | Not all objects could be planned; check planning result |
| 395 | Planning not possible; stages of doc. &1 have different carriers |
| 396 | Resource &1 cannot be used; it is blocked |
| 397 | Default truck &1 cannot be used; it is blocked |
| 398 | Freight order &1 created for means of transport &2 |
| 399 | Trailer unit &1 created |
| 400 | Railcar unit &1 created |
| 401 | Planning not possible; &1 is not ready for planning |
| 402 | Cannot change assignments of document &1; document assignments are fixed |
| 403 | Fixed assignment of document &1 overruled by manual planning settings |
| 404 | Fixing of document &1 overruled by manual planning settings |
| 405 | Assignment not possible; document &1 is already assigned to a schedule |
| 406 | Document &1 cannot be planned with schedule &2; locations are different |
| 407 | Cannot assign schedule &1 to doc. &2; document is already in use |
| 408 | Cannot assign schedule &1 to doc. &2; resource &3 is already assigned |
| 409 | Planning not possible; resource &1 does not have capacity |
| 410 | Planning not possible; document &1 is schedule-based |
| 411 | Cannot assign schedule &1 to doc. &2; different transportation modes |
| 412 | Cannot assign resource &1 to document &2; document category mismatch |
| 413 | Assignment not possible; driver &1 is blocked |
| 414 | Number of freight orders created: &1 |
| 415 | Number of freight bookings created:&1 |
| 416 | Number of trailer units created: &1 |
| 417 | Number of railcar units created: &1 |
| 418 | Number of container units created: &1 |
| 419 | Can't create document for resource/equip. type; doc. category mismatch |
| 420 | Cannot change document &1. Location sequence is fixed |
| 421 | Number of requirement documents assigned: &1 |
| 422 | Number of requirement documents unassigned: &1 |
| 423 | Number of requirement documents assigned to new capacity item: &1 |
| 424 | Requirement doc. &1 assigned to new capacity item &2 |
| 425 | On-carriage of &1 must not be planned separately; buyer's consolidation |
| 426 | Cannot assign &1 to &2; consolidation parameter mismatch |
| 427 | Cannot assign driver; document &1 is not relevant for driver planning |
| 428 | Cannot assign driver team to document &1; only single driver possible |
| 429 | Keep the service level at src loc. and dest loc. identical |
| 430 | Number of driver assignments: &1 |
| 431 | Number of driver unassignments: &1 |
| 432 | Driver &1 assigned to document &2 |
| 433 | Driver &1 unassigned from document &2 |
| 434 | You can only plan all stages of document &1 together |
| 435 | Cannot assign stage &1; doc. &2 can't be used for cust. self-delivery |
| 436 | Cannot assign stage &1; document &2 can't be used for customer pick-up |
| 437 | Delivery location added for new delivery attempt of requirement doc. &1 |
| 438 | Requirement &1 returned to loading loc.; new delivery attempt prepared |
| 439 | New delivery attempt prepared for req. &1 to be planned using other doc. |
| 440 | Requirement document assigned to item & instead |
| 441 | Planning not possible; stage &1 is not planning-relevant |
| 442 | Package unit &1 created |
| 443 | Number of package units created: &1 |
| 444 | Cannot remove location &1 from doc. &2; sub-stops still assigned |
| 445 | Planning not possible; VSR optimizer can't consider container unit &1 |
| 446 | Planning not possible; VSR optimizer can't consider package unit &1 |
| 447 | Planning not possible; selected stages of CU &1 are unconnected |
| 448 | Planning not possible; selected stages of PU &1 are unconnected |
| 449 | Cannot remove stop from document &1; stop is used by cargo items |
| 450 | Requirement document &1 assigned to capacity item &2 |
| 451 | Freight document &1 consolidated into freight document &2 |
| 452 | TU &1 consolidated into TU &2 |
| 453 | &1 freight documents consolidated into freight document &2 |
| 454 | &1 TUs consolidated into TU &2 |
| 455 | Cannot move stop &1; stop is a distribution stop |
| 456 | Cannot move stop &1; stop is a collection stop |
| 457 | Cannot move stop &1; conversion into a distribution stop is not possible |
| 458 | Cannot move stop &1; conversion into a collection stop is not possible |
| 459 | Cannot change assignments of capacity item &1; assignments are fixed |
| 460 | Fixed assignment of cap. item &1 overruled by manual planning settings |
| 461 | Cannot change assignments of document &1; load plan is finalized |
| 462 | Cannot change assignments of document &1; execution already started |
| 463 | Package unit &1 cannot be assigned; doc. &2 has different default PU type |
| 464 | Assignment not possible; invalid partial assignment for document &1 |
| 465 | Unassignment not possible; invalid partial assignment for document &1 |
| 466 | Unassignment of req. doc. &1 from cap. doc. &2 not possible |
| 467 | Delivery location changed for new delivery attempt of requirement doc. &1 |
| 468 | Cannot change dest. location of stage &1; succeeding stage is planned |
| 469 | Planning not possible; no cross-company assignments allowed for doc. &1 |
| 470 | Planning not possible; no cross-company assignments for doc. type &1 |
| 471 | Cannot assign requirement &1 to doc. &2; no cross-company assign. allowed |
| 472 | Action not possible; only linear stage sequences are supported |
| 473 | Consignment order &1 created |
| 474 | Number of consignment orders created: &1 |
| 475 | Assignment not possible; carrier doesn't match |
| 476 | Assignment not possible; no common location sequence found |
| 477 | Cannot remove requirement doc. &1; warehouse processing already started |
| 478 | Planning not possible; warehouse processing already started for doc. &1 |
| 479 | Assignment not possible; deviating goods supplier within documents |
| 480 | Can't assign requirement doc. to capacity doc. No location in req. doc. |
| 481 | Equipment group &1 and equipment type &2 can't be used; they are blocked |
| 482 | Can't assign schedule &1 to doc. &2; equip. type &3 is already assigned |
| 483 | Planning not possible; equip. group &1/equip. type &2 has no capacity |
| 484 | Can't assign equip. type &1 to document &2; document category mismatch |
| 485 | Action not possible in FO &1 for customer self-delivery/pick-up. |
| 486 | Cannot change assignments of doc. &1; load plan of item &2 is finalized |
| 490 | Can't assign stages of req. doc &1 to cust. self-delivery/pick-up FO &2 |
| 502 | Failed delivery for Requirement &1 reverted |
| 504 | Cannot revert failed delivery for req. &1; execution already started |
| 505 | Cannot revert failed delivery for req. &1; succ. stage is already planned |
Mesaj metinleri danışmanlık ve eğitim amaçlı teknik referans olarak gösterilir. SAP, SAP TM, SAP EWM, SAP GTS, SAP S/4HANA ve diğer SAP ürün/hizmet adları SAP SE'nin veya bağlı şirketlerinin ticari markalarıdır.