| VL525 |
Route schedule locked by user &1 |
| VL526 |
First delete all allocations of route schedule determination |
| VL527 |
Route schedule &1 still being used in other shipping points |
| VL528 |
Route schedule &1 deleted |
| VL529 |
No texts exist for route schedules in language &1 |
| VL530 |
No itinerary maintained for route schedule &1 |
| VL531 |
Specify an itinerary |
| VL532 |
Itinerary &1 is already assigned |
| VL533 |
Route schedule &1 has an itinerary, but it is not defined |
| VL534 |
No calendar week could be determined for date &1 |
| VL535 |
Itinerary for &1 &2 &3 &4 does not exist, but is expected |
| VL536 |
Calendar week &1: date of the Monday could not be calculated |
| VL537 |
Itinerary maintenance not allowed without route schedule determination |
| VL538 |
Route schedule &1 cannot be used |
| VL539 |
Error when adding/subtracting SPZ |
| VL540 |
Error while checking route schedule against determination |
| VL541 |
Customer &1 flagged for deletion |
| VL542 |
Central delivery block &2 set for customer &1 |
| VL543 |
Add a new ship-to party to the itinerary |
| VL544 |
Adapt/update itinerary |
| VL545 |
Note that the ship-to party in the itinerary has changed |
| VL546 |
Specify shipping point and route schedule of reference |
| VL547 |
Create a generally valid assignment first |
| VL548 |
Ship-to party &1 has no unloading points |
| VL549 |
Route schedule not found |
| VL550 |
********** Collective processing |
| VL551 |
Order header & does not exist |
| VL552 |
Header status & does not exist |
| VL553 |
Item does not fit into this delivery |
| VL554 |
Text for error message & & not maintained |
| VL555 |
A WM transfer order already exists |
| VL556 |
The desired dates contradict each other |
| VL557 |
The delivery date cannot be before the material staging date |
| VL558 |
Delivery &1 read from the archive |
| VL559 |
Delivery &1 does not exist in the database or in the archive |
| VL560 |
************** General delivery interface |
| VL561 |
Essential transfer parameters are missing in record: & & |
| VL562 |
Enter either delivery date or goods issue date |
| VL563 |
Higher-level item & does not exist |
| VL564 |
Delivery type was not transmitted |
| VL565 |
Data of preceding document was not transmitted |
| VL566 |
Ship-to party and sales organization have different languages |
| VL567 |
Document data for delivery in central system was not transmitted |
| VL568 |
Originating system is not known |
| VL569 |
Mandatory partner was not transmitted |
| VL570 |
************************************************ Route Schedules II ***** |
| VL571 |
Shipping deadlines may change |
| VL572 |
Unexpected exception |
| VL573 |
Do not delete general rt. sched. determin. if individual determ. exists |
| VL574 |
Are itinerary and route compatible? |
| VL575 |
Check Customizing for del. type &1; Indicator for del. split incorrect |
| VL576 |
Delivery is archived; Display of document flow not possible |
| VL577 |
Change document for delivery &1 read from archive |
| VL578 |
Change management could not be activated |
| VL579 |
Decentralized warehouse cannot be reached, therefore display only |
| VL580 |
Shipping point &1 is not maintained correctly in decentralized system |
| VL581 |
Assign a goods receiving point to the inbound delivery |
| VL582 |
Delivery contains items with incomplete batch split |
| VL583 |
This process is currently not supported |
| VL584 |
Error in the incompletion-log control (see long text) |
| VL585 |
Change management for decentralized WMS is not currently supported |
| VL586 |
Transaction VL31 is not supported with active change management |
| VL587 |
Shipping in shipping point &1 from plant &2 stor. loc. &3 is not possible |
| VL588 |
Shipping point &1 cannot be used in the sales area entered |
| VL589 |
&1 &2 could not be distributed |
| VL590 |
The availability check is not active for this material |
| VL591 |
Delivery split could not be reconstructed. Transaction canceled |
| VL592 |
Log on &1 by &2 at &3 by user &4 |
| VL593 |
& & saved and transferred to storage |
| VL594 |
Delivery is in storage, therefore display only |
| VL595 |
Duplicate item numbers; item number transfer deactivated |
| VL596 |
Item &1 from central system cannot be deleted decentrally |
| VL597 |
Role of ship-to party must be defined in partner schema &1 as mandatory |
| VL598 |
Verification from WMS has already occurred. |
| VL599 |
Stock transport order belongs to third-party delivery &1 |
| VL600 |
********** Goods issue postings |
| VL601 |
Delivery is not defined for goods issue |
| VL602 |
Goods issue has already been posted for delivery |
| VL603 |
Plant is not defined for delivery item & |
| VL604 |
The storage location is not defined for delivery item & |
| VL605 |
The batches are not defined for delivery item & |
| VL606 |
Valuation type is not defined for delivery item & |
| VL607 |
For plant &, material type & is not defined in Table T134W |
| VL608 |
Delivery has not yet been completely processed by WM |
| VL609 |
Delivery has not yet been put away / picked (completely) |
| VL610 |
Document does not contain any items |
| VL611 |
Goods receipt posted to & & |
| VL612 |
Goods issue not yet carried out |
| VL613 |
Create delivery for purchase order using delivery list |
| VL614 |
Item does not affect purchase order. Display not possible. |
| VL615 |
Delivery item is not or only partially packed |
| VL616 |
& & have already been packed. Quantity cannot be changed. |
| VL617 |
Item has already been packed and therefore cannot be deleted |
| VL618 |
Picking request not yet confirmed |
| VL619 |
Problems in inventory management (goods issue not possible) |
| VL620 |
There are still open shipment order items |
| VL621 |
Risk of posting several mat.documents for one delivery->long text |
| VL622 |
No material document could be found for cancellation |
| VL623 |
GI for delivery & has not yet taken place or is already canceled |
| VL624 |
Goods movemt for delivery & cannot be canceled for the following reasons: |