Id | Title |
---|---|
VL425 | No serial numbers are maintained for item & or the quantity is zero |
VL426 | Serial numbers can only be maintained for quantities in whole numbers |
VL427 | Serial no. maintenance only possible if you specify a batch/val. type |
VL428 | Serial no. mainten. only possible if all batches/val.types are assigned |
VL429 | Batch/Val.type split only possible if no serial numbers are maintained |
VL430 | Activity & not assigned for the serial number profile & |
VL431 | Serial numbers cannot be assigned to item &1 |
VL432 | Item & must have & serial numbers assigned to it |
VL433 | See the long text for serial number assignment for item & |
VL434 | See the long text for serial number display for item & |
VL435 | No configuration data maintained for material &1 in plant &2 |
VL436 | Not all serial numbers for delivery item &1 can be deleted (-> long text) |
VL437 | Messages in the log refer to the distributed delivery |
VL438 | No checks necessary, since no relevant changes were made |
VL439 | Distributed document can be successfully changed |
VL440 | End time is before start time |
VL441 | Enter time together with date only |
VL442 | Enter time or date only in combination with a deadline function |
VL443 | You cannot save a delivery without items |
VL444 | Item &1: The original order item has already been invoiced |
VL445 | No partner determination procedure exists for delivery type &1 |
VL446 | Goods recipient missing in partner det. procedure &1 for del. type &2 |
VL447 | Partner determination procedure &1 was not created (delivery type &2) |
VL448 | There is an open inbound delivery &3 in the WMS for PO &1, item &2 |
VL449 | Item &1: Different billing type for intercompany billing |
VL450 | Expiration date was exceeded by & days |
VL451 | The minimum remaining shelf life was fallen short of by & days |
VL452 | The delivery cannot be distributed (see the subsequent message) |
VL453 | "From item" & is larger than "To item" & |
VL454 | You cannot carry out deliveries for the same sched.agreemt more than once |
VL455 | No delivery-relevant items in order &1, order type &2 |
VL456 | The delivery can be successfully distributed |
VL457 | Enter a valid reason |
VL458 | Batch main item &1 is already packed. HU management is not possible |
VL459 | Batch split for item &1 is already packed. Check the packing data |
VL460 | Items were deleted, even though picking has already taken place |
VL461 | Order cannot be delivered (see long text) |
VL462 | Transactions do not match according to copy condition & |
VL463 | No distribution: Delivery does not contain items relevant for distributn |
VL464 | The route could not be determined |
VL465 | This route is not a substitute for route & |
VL466 | Route & was re-determined |
VL467 | Check whether the route is to be changed to & |
VL468 | Weight group & was re-determined |
VL469 | Shipping dates were redetermined |
VL470 | Delivery quantities were increased, even though picking already occurred |
VL471 | Copying from business transaction type & to & is not defined |
VL472 | Number of copying routine for table & is missing in Table TVCPL |
VL473 | Copying is not poss.because an entry is missing in Table TVCPL: & & & & |
VL474 | Picking/putaway has already started in decentralized WMS |
VL475 | Batch split item &1 cannot be deleted due to a distributed delivery |
VL476 | Item & is not copied from the reference document |
VL477 | Delivery was split in decentralized WMS, will only display |
VL478 | Item category & is not defined, so item & will be disregarded |
VL479 | Change management is not active. You cannot save the delivery |
VL480 | The partner system is currently not available. Simulation is not possible |
VL481 | Change management switched off for this delivery, will only display |
VL482 | None of the selected items can be deleted |
VL483 | Multiple delivery is not possible for the same item in a delivery |
VL484 | Item &1 is a batch split item; batch splitting is not possible |
VL485 | No log of changes |
VL486 | Change document could not be determined |
VL487 | Position the cursor on a line in order to select |
VL488 | No more changes exist |
VL489 | Central system &1 cannot be reached, change management not possible |
VL490 | No handling units exist |
VL491 | Confirmation from WMS already performed; You cannot delete item & |
VL492 | Change management switched off for this delivery |
VL493 | Delivery split executed |
VL494 | Billing operation already exists for item &1 |
VL495 | Change management not active; deletion not possible |
VL496 | Delivery update not possible; distributed document cannot be changed |
VL497 | The delivery is currently being processed by user &1 in system &2 |
VL498 | Synchronization in partner system not yet complete |
VL499 | Delivery not current; Synchronization not yet complete |
VL500 | ********** Update |
VL501 | Error during INSERT & & & |
VL502 | Error during UPDATE & & & |
VL503 | Error during DELETE & & & |
VL504 | Delivery block is inconsistent |
VL505 | Item & is missing in Table TYLIPS |
VL506 | Error in table structure UVBAP |
VL507 | Synchronization not yet complete |
VL508 | Inbound delivery item for SC component was generated from PO &1 &2 |
VL509 | Picking/putaway has already begun |
VL510 | ****************************************** Route Schedules *********** |
VL511 | Route schedule &1 does not plan route &2 |
VL512 | No route schedules defined |
VL513 | No route schedule determination defined for shipping point &1 |
VL514 | Ship-to party &1 does not exist |
VL515 | Route schedule &1 does not exist |
VL516 | Route schedule &1: description missing in language &2 |
VL517 | No route schedule determination defined |
VL518 | Route schedule &1 saved |
VL519 | Route schedule &1 already exists |
VL520 | Enter a value between 1 and 7 for the weekday |
VL521 | Allocation already exists for shipping point &1 |
VL522 | Specify an unloading point for ship-to party &1 |
VL523 | Enter both year and period |
VL524 | Enter shipping condition and transportation group |