Id | Title |
---|---|
VL625 | Goods movement for delivery & canceled |
VL626 | Cancellation date & is before the goods issue date & |
VL627 | Delivery still contains pre-packed (putaway) handling units |
VL628 | No purchase order item exists for this item |
VL629 | Select individual item |
VL630 | Caution: performance can be affected by unspecific GI date |
VL631 | Enter goods issue date |
VL632 | Picked quantity &1 is larger than delivery quantity &2 |
VL633 | Cancellation of goods movement from decentr. systems is not possible. |
VL634 | Delivery & - document flow missing for the respective goods issue |
VL635 | Delivery quantity of batch main item & is not allocated completely |
VL636 | Goods receipt for this inbound delivery is already posted |
VL637 | Delivery & not yet completely processed in decentralized whse system |
VL638 | Material & is already packed. Material change not possible |
VL639 | Delivery still contains handling units |
VL640 | Stock determination failed during goods issue: return code & |
VL641 | Error during Lean WM processing; delivery document inconsistent |
VL642 | Error during Lean WM processing; document flow incorrect |
VL643 | Quantity of & & remains open after stock determination |
VL644 | There is an unconfirmed transfer order for item & |
VL645 | Goods movement cannot be reversed - Delivery &1 contains handling units |
VL646 | No proof of delivery expected for delivery & |
VL647 | Proof of delivery confirmed for delivery & |
VL648 | Adapt delivery quantity &1 to pick quantity &2 |
VL649 | Delivery &1 contains items from delivery &2 (see long text) |
VL650 | Purchase order & item & does not exist. Item ignored. |
VL651 | Subsequent movement type could not be determined for & & |
VL652 | Delivery does not refer to purchase order |
VL653 | Select items for goods receipt |
VL654 | Proof of delivery for delivery & already verified |
VL655 | You cannot change the unit for POD items |
VL656 | You must save before you can post goods issue (due to forecast) |
VL657 | Delivery item &2 planned for decentralized warehouse &3 |
VL658 | Delivery planned for decentralized warehouse &2 |
VL659 | Error when creating document flow for delivery & |
VL660 | Enter a criterion for inbound delivery selection |
VL661 | Inbound delivery & does not exist |
VL662 | Database inconsistency: Plant & not found (T001W) |
VL663 | No rough goods issue defined for the purchase orders selected |
VL664 | There is no entry for confirmation category & in T163D |
VL665 | No delivery type assigned to confirmation category & (table T163D) |
VL666 | The number is not within number range &, delivery type & |
VL667 | You cannot create several dlv.headers in case of external no. assignment |
VL668 | No entry found for selection |
VL669 | Inbound delivery & not found |
VL670 | Purchase order & does not exist |
VL671 | Purchase order does not contain items for plant & |
VL672 | Enter category and identifier for means of transport |
VL673 | No inbound delivery found to match selection criteria specified |
VL674 | You cannot transfer shipping units during a delivery split |
VL675 | Shipping units cannot be transferred from an inbound delivery |
VL676 | Predefine date and time |
VL677 | Error during quantity verification of proof of delivery |
VL678 | Delivery item &1 of delivery &2 is not relevant for POD |
VL679 | Not possible to confirm/cancel proof of delivery |
VL680 | You are not authorized to cancel the goods issue for shipping point & |
VL681 | Enter a valid date |
VL682 | Actual GI date later than POD date - change POD date |
VL683 | Enter a valid time |
VL684 | Difference quantities missing in delivery item &1 for reason &2 |
VL685 | You must give a reason for the difference in item & |
VL686 | Item & contains inconsistent differences (delivery/storage quantities) |
VL687 | Item &: difference quantities in POD lead to rounding errors |
VL688 | Reason &1 was given more than once for item &2 (please change) |
VL689 | POD quantity may not be negative (please correct difference quantities) |
VL690 | Goods movement for delivery & in decentralized system contains errors |
VL691 | Proof of delivery was already confirmed |
VL692 | Proof of delivery has not been confirmed yet |
VL693 | Subsequent processing has already begun (execution not possible) |
VL694 | Processing error during update: (XLIPS and YIMSEG do not match) |
VL695 | Process. error: XVBFA already contains flow record MM doc.no. & & |
VL696 | Processing error: VLBEFU contains at least two MM doc.nos. & and & |
VL697 | Processing error: No. of VLBEFU & > No. of XLIPS & |
VL698 | Processing error: XLIPS and VLBEFU do not match |
VL699 | Processing error during update (XIMSEG and EMSEG do not match) |
VL700 | ********** Shipping output (printing, fax etc) ********* |
VL701 | No shipping papers are waiting to be processed |
VL702 | Enter a shipping point |
VL703 | Shipping point is not valid |
VL704 | No picking lists are available for this shipping point |
VL705 | Maintain print parameters: Applic. &, output &, shipping point & |
VL706 | Maintain access to print parameters: Applic.&, output & (VK01/details) |
VL707 | Maintain EDI data for partner &, application &, output & |
VL708 | Access type to print table for the delivery note is not allowed |
VL709 | & output passed on for sending |
VL710 | Maintain processing program for output &1, type &2, application &3 |
VL711 | Output & is not a picking list |
VL712 | Possible entries: X or blank |
VL713 | Select output |
VL714 | Delivery & is blocked; selection will be ignored |
VL715 | Output has been changed |
VL716 | Output for delivery & now completed; selection will be ignored |
VL717 | No output has been selected for printing |
VL718 | Output was successfully issued |
VL719 | Output could not be issued |
VL720 | Shipping point not unique |
VL721 | Ship-to party not unique |
VL722 | Plant not unique |
VL723 | Handling unit's unloading point is not unique |
VL724 | No handling units (packaging) exist |