| /DSD/VC_MESSAGE524 |
Enter a valid unloading point |
| /DSD/VC_MESSAGE525 |
Enter a valid contact person |
| /DSD/VC_MESSAGE526 |
Enter a valid sales area. Sales area process active |
| /DSD/VC_MESSAGE527 |
Sales area not permitted. Sales area processes not active |
| /DSD/VC_MESSAGE528 |
Number range &1 is not an external number range |
| /DSD/VC_MESSAGE529 |
Number range &1 is not an internal number range |
| /DSD/VC_MESSAGE530 |
Flag the shipment or visit list as relevant |
| /DSD/VC_MESSAGE550 |
Enter a valid time frame (date from > date to) |
| /DSD/VC_MESSAGE551 |
Only saved visit plans will be checked; (Change not saved) |
| /DSD/VC_MESSAGE552 |
Only saved visit lists will be checked; (Change not saved) |
| /DSD/VC_MESSAGE600 |
A customer can only be contained once in each visit plan |
| /DSD/VC_MESSAGE601 |
Not possible to move visit plans |
| /DSD/VC_MESSAGE602 |
You are not authorized to display customer master data |
| /DSD/VC_MESSAGE603 |
Document &1 for document category &2 |
| /DSD/VC_MESSAGE604 |
Save cancelled due to existing visit lists |
| /DSD/VC_MESSAGE605 |
Type &1 is not permitted |
| /DSD/VC_MESSAGE606 |
A customer cannot be driver and co-driver at the same time |
| /DSD/VC_MESSAGE607 |
Visit plan is no longer valid and therefore cannot be changed |
| /DSD/VC_MESSAGE608 |
Visit list &1 cannot be changed (execution date is before today's date) |
| /DSD/VC_MESSAGE609 |
Visit list &1 cannot be changed (locked due to transport link) |
| /DSD/VC_MESSAGE610 |
Save terminated - error in number range object &1 - interval &2 |
| /DSD/VC_MESSAGE611 |
Calendar &2 could not be synchronized for customer &1 |
| /DSD/VC_MESSAGE612 |
Driver &1 is not defined as the customer in sales area &2 &3 &4 |
| /DSD/VC_MESSAGE613 |
Customer &1 is not defined in the sales area for the visit plan |
| /DSD/VC_MESSAGE614 |
Customer &1 is not defined in the sales area for the visit list |
| /DSD/VC_MESSAGE615 |
&1 customers were not transferred (do not exist in sales area) |
| /DSD/VC_MESSAGE616 |
Customer sequence incorrect. A sequence number must be unique |
| /DSD/VC_MESSAGE617 |
Not all visit plan texts were copied |
| /DSD/VC_MESSAGE618 |
Only special text objects are allowed |
| /DSD/VC_MESSAGE620 |
The ship-to party of the delivery entered here must be a driver |
| /DSD/VC_MESSAGE621 |
Customer for delivery &1 is not the same as driver for visit list |
| /DSD/VC_MESSAGE622 |
Customer (&1) for this delivery should be a driver from the tour master |
| /DSD/VC_MESSAGE623 |
A speculative load should not be assigned for visit plan type &1 |
| /DSD/VC_MESSAGE624 |
Customer &1 is not relevant for this document &2 |
| /DSD/VC_MESSAGE625 |
Customer &1 is not a ship-to party in document &2 |
| /DSD/VC_MESSAGE626 |
A shipment document should not be assigned to one individual customer |
| /DSD/VC_MESSAGE627 |
Driver must be same as ship-to party (&1) of speculative load |
| /DSD/VC_MESSAGE628 |
The ship-to party of the delivery (&1) is a customer from the visit list |
| /DSD/VC_MESSAGE629 |
Customer &1 is not a sold-to party in document &2 |
| /DSD/VC_MESSAGE630 |
Text &1 for object &2, ID &3, language &4 does not exist |
| /DSD/VC_MESSAGE631 |
Unable to delete text &1 for object &2, ID &3, language &4 |
| /DSD/VC_MESSAGE632 |
Unable to create text &1 for object &2, ID &3, language &4 |
| /DSD/VC_MESSAGE633 |
Customizing: DSD tour status - visit plan type &1 is not relevant for DSD |
| /DSD/VC_MESSAGE635 |
Maximum number of customers for this visit plan has been reached |
| /DSD/VC_MESSAGE636 |
Maximum number of customers for this visit plan has been reached |
| /DSD/VC_MESSAGE637 |
Error when reading a row |
| /DSD/VC_MESSAGE638 |
Error when inserting a row |
| /DSD/VC_MESSAGE639 |
Error when changing a row |
| /DSD/VC_MESSAGE640 |
Error when deleting a row |
| /DSD/VC_MESSAGE641 |
Error when calling a BAdI |
| /DSD/VC_MESSAGE650 |
Authorizations are missing for & visit list(s) |
| /DSD/VC_MESSAGE700 |
There is no print output for shipment status &1 (at least &2) |
| /DSD/VC_MESSAGE701 |
There is no print output for shipment type &1/ trans. planing point &2 |
| /DSD/VC_MESSAGE702 |
Application &1 object &2 message &3 selected |
| /DSD/VC_MESSAGE703 |
Message &1 was successfully processed |
| /DSD/VC_MESSAGE704 |
Errors occurred when processing message &1 &2 |
| /DSD/VC_MESSAGE705 |
Visit list is inactive; message will not be processed |
| /DSD/VC_MESSAGE706 |
No print output for visit plan type &1 |
| /DSD/VC_MESSAGE707 |
No messages were selected for processing |
| /DSD/VC_MESSAGE708 |
The message type must be entered in table /DSD/VC_MSGTYP |
| /DSD/VC_MESSAGE711 |
No authorization for message processing |
| /DSD/VC_MESSAGE712 |
The visit list is not assigned a shipment document |
| /DSD/VC_MESSAGE713 |
Transport document &1 does not exist |
| /DSD/VC_MESSAGE714 |
Changes to visit lists must be saved first |
| /DSD/VC_MESSAGE715 |
Message can only be displayed (shipment &1 is being processed by &2) |
| /DSD/VC_MESSAGE716 |
Messages can only be displayed (save changes to visit lists first) |
| /DSD/VC_MESSAGE717 |
Messages for shipment &1 have been processed and saved |
| /DSD/VC_MESSAGE718 |
Changes to messages were not saved for shipment &1 |
| /DSD/VC_MESSAGE719 |
Changes to messages were not saved for visit list &1 |
| /DSD/VC_MESSAGE720 |
Messages for visit list &1 have been processed and saved |
| /DSD/VC_MESSAGE750 |
Header data is missing for shipment or visit list |
| /DSD/VC_MESSAGE751 |
Component ID is missing |
| /DSD/VC_MESSAGE752 |
Incorrect combination of parameters when calling function module |
| /DSD/VC_MESSAGE753 |
Flags for driver scenario are set incorrectly in table /DSD/VC_VPTYPE |
| /DSD/VC_MESSAGE754 |
More than one shipment is linked with list when processing using VL |
| /DSD/VC_MESSAGE755 |
Shipment number of visit list number is missing |
| /DSD/VC_MESSAGE756 |
Visit list &1 does not exist |
| /DSD/VC_MESSAGE757 |
No items for visit list &1 |
| /DSD/VC_MESSAGE758 |
No reference documents for visit list &1 |
| /DSD/VC_MESSAGE759 |
Visit list &1 is not active |
| /DSD/VC_MESSAGE760 |
Error &1 while reading table /DSD/VC_VLTRADAT |
| /DSD/VC_MESSAGE761 |
/DSD/VC_VLTRADAT does not contain data for type &1 -> no further IDocs |
| /DSD/VC_MESSAGE762 |
Type of visit list &1 has TRHH indicator set |
| /DSD/VC_MESSAGE763 |
Visit list for shipment &1 not found |
| /DSD/VC_MESSAGE764 |
Message type &1 not defined in /DSD/VC_MSGTYP as relevant for output |
| /DSD/VC_MESSAGE800 |
Visit list not archived; checking residence time |
| /DSD/VC_MESSAGE801 |
Visit list not archived as settlement not successful |
| /DSD/VC_MESSAGE802 |
Visit list is being archived |
| /DSD/VC_MESSAGE803 |
Visit list not archived as settlement has not been carried out |
| /DSD/VC_MESSAGE804 |
You cannot change documents "&1" |
| /DSD/VC_MESSAGE805 |
Visit plan type &1 does not exist |
| /DSD/VC_MESSAGE806 |
Residence time &1 for visit plan type &2 is less than &3 days |
| /EACA/BTA_GL000 |
A system error has occurred |
| /EACA/BTA_GL001 |
No accounting system could be found |
| /EACA/BTA_GL002 |
The Accounting Engine has not yet been activated |
| /EACA/BTA_GL003 |
No configuration that can be activated |
| /EACA/BTA_GL004 |
No active configuration available |
| /EACA/BTA_GL005 |
No journal found |
| /EACA/BTA_GL006 |
No configuration information available |
| /EACA/BTA_GL007 |
GL Business Transaction successfully activated |