SAP ABAP Message Class /DSD/VC_MESSAGE (Message Class for Visit Control in DSD)
Basic Data
Hierarchy
☛
EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials
⤷ LE-DSD-VC (Application Component) Visit Control
⤷ /DSD/VC (Package) Visit Control
⤷ LE-DSD-VC (Application Component) Visit Control
⤷ /DSD/VC (Package) Visit Control
Attributes
Message class | /DSD/VC_MESSAGE | |
Short Description | Message Class for Visit Control in DSD | |
Changed On | 20130531 | |
Last Changed At | 104754 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 001 | DSD is not active - function not possible | Space: object requires documentation | |
2 | 002 | Enter a message number | The short text describes the object sufficiently | |
3 | 010 | You have to save the changes to the visit plan first | Space: object requires documentation | |
4 | 011 | You have to save the changes to the visit plans first | Space: object requires documentation | |
5 | 012 | You have to save the changes to the visit plan first | Space: object requires documentation | |
6 | 013 | You are not authorized to perform this action | Space: object requires documentation | |
7 | 014 | You can only delete visit lists that lie in the future | Space: object requires documentation | |
8 | 015 | Visit list cannot be deleted (locked due to shipment link) | Space: object requires documentation | |
9 | 016 | You cannot use exceptions in combination with "non-appointments" | Space: object requires documentation | |
10 | 017 | You should only delete future visit lists | The short text describes the object sufficiently | |
11 | 018 | You should only delete historical visit lists | The short text describes the object sufficiently | |
12 | 019 | Select one row only | The short text describes the object sufficiently | |
13 | 100 | Visit list &1 not found in /DSD/VC_VLH | Space: object requires documentation | |
14 | 101 | Could not determine the sold-to party (&2) for visit list &1 | Space: object requires documentation | |
15 | 102 | Status of customer transaction &1 does not exist in /DSD/VC_VSTATCON | Space: object requires documentation | |
16 | 103 | Could not create sales activity for customer &1 - VBELN not found | The short text describes the object sufficiently | |
17 | 104 | Customer &1 does not exist in /DSD/VC_VLP; no entry in ref. tab. | Space: object requires documentation | |
18 | 105 | No document no. exists in the settlement document items for tour &1 | Space: object requires documentation | |
19 | 106 | Visit list item ref. documents are being processed: VLID=&1, VLPOS=&2 | Space: object requires documentation | |
20 | 107 | Entry in ref. table failed for VLID=&1, VLPOS=&2 with VBELN=&3 | Space: object requires documentation | |
21 | 108 | Visit plan &1 was not found in /DSD/VC_VPH | The short text describes the object sufficiently | |
22 | 110 | Transportation planning points in vehicle and tour masters are different | Space: object requires documentation | |
23 | 111 | Delivery date of assigned delivery &1 is different to the execution date | Space: object requires documentation | |
24 | 112 | Route for delivery &1 is not the same as the route for the visit list | Space: object requires documentation | |
25 | 113 | No visit plans/lists matching the selection criteria were found | Space: object requires documentation | |
26 | 114 | No visit lists for deletion could be selected | Space: object requires documentation | |
27 | 115 | &1 - should not be deleted, as ref. documents have already been assigned | Space: object requires documentation | |
28 | 116 | Deletion of visit lists was terminated | Space: object requires documentation | |
29 | 117 | Document &1 must be entered with flag <After Tour> | The short text describes the object sufficiently | |
30 | 118 | &1 visit lists deleted | The short text describes the object sufficiently | |
31 | 200 | Order type &1 not found - check the DSD sales document types | The short text describes the object sufficiently | |
32 | 201 | Calendar changed for customer &1 and calendar type &2 | Space: object requires documentation | |
33 | 202 | Limit your selection | Space: object requires documentation | |
34 | 203 | Customer &1 has been geo-coded (latitude: &3, longitude: &2) | Space: object requires documentation | |
35 | 204 | Data saved | Space: object requires documentation | |
36 | 205 | Test run | Space: object requires documentation | |
37 | 206 | No date could be determined | Space: object requires documentation | |
38 | 207 | No sales area specified for sales area processes | The short text describes the object sufficiently | |
39 | 208 | Sales area processes inactive. No data for sales area | The short text describes the object sufficiently | |
40 | 300 | &1 - visit lists already exist for this period (&2 - &3) | Space: object requires documentation | |
41 | 301 | &1 - No visit lists have to be generated for period &2 - &3 | Space: object requires documentation | |
42 | 302 | &1 - An inactive visit list was created for day &2 | Space: object requires documentation | |
43 | 303 | &1 - Error during number assignment (number range object: &2) | Space: object requires documentation | |
44 | 304 | &1 - Error while inserting visit list &2 (tag &3) | Space: object requires documentation | |
45 | 305 | &1 - Only visit lists in the future are generated (&2 now &3) | Space: object requires documentation | |
46 | 306 | &1 - Generation start date is &2 | Space: object requires documentation | |
47 | 307 | &1 - Generation start (&2) is later than generation end (&3) | Space: object requires documentation | |
48 | 308 | No error log exists for this visit plan | Space: object requires documentation | |
49 | 309 | No visit plans were selected | Space: object requires documentation | |
50 | 310 | You are not authorized to generate visit lists | Space: object requires documentation | |
51 | 311 | Visit list &1 is being processed by &2 (not generated) | Space: object requires documentation | |
52 | 312 | No visit list was generated | Space: object requires documentation | |
53 | 313 | Only future visit lists are generated (date >= run date) | Space: object requires documentation | |
54 | 314 | From date (&1) must be earlier than To date (&2) | Space: object requires documentation | |
55 | 315 | &1 - driver &2 is not available on &3 (see block times) | Space: object requires documentation | |
56 | 316 | &1 - vehicle &2 is not available on &3 (see block times) | Space: object requires documentation | |
57 | 317 | External number &1 for visit list is not in number range &2 | The short text describes the object sufficiently | |
58 | 350 | No delivery was selected | Space: object requires documentation | |
59 | 351 | Visit list missing: visit plan &1, customer &2, delivery day &3 | Space: object requires documentation | |
60 | 352 | No DSD-relevant delivery types have been defined in Customizing | Space: object requires documentation | |
61 | 353 | No delivery for cust. &1 is planned on &2 according to visit plans | Space: object requires documentation | |
62 | 354 | No relevant visit plan types have been defined (see Customizing) | Space: object requires documentation | |
63 | 355 | Delivery document &1 cannot be assigned to a visit list | Space: object requires documentation | |
64 | 356 | Delivery document &1 is assigned to a different visit plan (&3 => &2) | Space: object requires documentation | |
65 | 357 | The delivery date must be later than the run date | Space: object requires documentation | |
66 | 360 | All deliveries have been assigned to a visit list | Space: object requires documentation | |
67 | 400 | Visit plan &1 is being processed by &2 | Space: object requires documentation | |
68 | 401 | Visit list &1 is being processed by &2 | Space: object requires documentation | |
69 | 402 | Error during number assignment for visit lists from interval &1 | Space: object requires documentation | |
70 | 403 | No number range interval for visit lists for visit plan type &1 | Space: object requires documentation | |
71 | 404 | Error during number assignment for visit plans from interval &1 | Space: object requires documentation | |
72 | 405 | No number range interval for visit plans for visit plan type &1 | Space: object requires documentation | |
73 | 406 | Error in lock administration | Space: object requires documentation | |
74 | 407 | External number &1 for visit plan is not in number range &2 | The short text describes the object sufficiently | |
75 | 408 | Create with external number: visit plan &1 already exists | The short text describes the object sufficiently | |
76 | 409 | Create with external number: visit list &1 already exists | The short text describes the object sufficiently | |
77 | 410 | &1 - Desc.: &2 (Valid &3 to &4) | Space: object requires documentation | |
78 | 411 | &1 - Desc.: &2 (Execution date: &3) | Space: object requires documentation | |
79 | 412 | No external number range interval for visit plans for visit plan type &1 | The short text describes the object sufficiently | |
80 | 413 | No external number range interval for visit lists for visit plan type &1 | The short text describes the object sufficiently | |
81 | 414 | Save canceled - error during deletion of visit plan &1 | The short text describes the object sufficiently | |
82 | 415 | Save canceled - error during change of visit plan &1 | The short text describes the object sufficiently | |
83 | 416 | Save canceled - error during deletion of visit plan &1 | The short text describes the object sufficiently | |
84 | 500 | You cannot set receiving and visit indicators at the same time | The short text describes the object sufficiently | |
85 | 501 | You have to set the visit ID and the function | Space: object requires documentation | |
86 | 502 | You can only set the manual shipment ID once in each client | The short text describes the object sufficiently | |
87 | 503 | Visit plan type & does not exist in /DSD/VC_VPTYPE | Space: object requires documentation | |
88 | 504 | Enter a route | Space: object requires documentation | |
89 | 505 | Transportation planning point differs in vehicle and tour masters | Space: object requires documentation | |
90 | 506 | End time must be later than start time | Space: object requires documentation | |
91 | 507 | "Validity(Restr.)" must not be outside of or equal to "Validity" | Space: object requires documentation | |
92 | 508 | Enter a date | Space: object requires documentation | |
93 | 509 | Vehicle & does not exist in /DSD/RPMV_V | Space: object requires documentation | |
94 | 510 | Route & does not exist in TVRO | Space: object requires documentation | |
95 | 511 | Trailer & does not exist in /DSD/RPTR_V | Space: object requires documentation | |
96 | 512 | Driver and co-driver must be different individuals | Space: object requires documentation | |
97 | 513 | Vehicle and trailer must be different objects | Space: object requires documentation | |
98 | 514 | Enter a vehicle | Space: object requires documentation | |
99 | 515 | Enter a driver | Space: object requires documentation | |
100 | 516 | Enter a visit plan type | Space: object requires documentation | |
101 | 517 | Enter a number range interval | Space: object requires documentation | |
102 | 518 | Date &1 is earlier than today (&2) | Space: object requires documentation | |
103 | 519 | Enter a visit group | Space: object requires documentation | |
104 | 520 | Visit group & does not exist in /DSD/VC_AUTH | Space: object requires documentation | |
105 | 521 | Enter a valid driver | Space: object requires documentation | |
106 | 522 | Sales area data is not valid | The short text describes the object sufficiently | |
107 | 523 | Enter a valid customer | The short text describes the object sufficiently | |
108 | 524 | Enter a valid unloading point | The short text describes the object sufficiently | |
109 | 525 | Enter a valid contact person | The short text describes the object sufficiently | |
110 | 526 | Enter a valid sales area. Sales area process active | The short text describes the object sufficiently | |
111 | 527 | Sales area not permitted. Sales area processes not active | The short text describes the object sufficiently | |
112 | 528 | Number range &1 is not an external number range | The short text describes the object sufficiently | |
113 | 529 | Number range &1 is not an internal number range | The short text describes the object sufficiently | |
114 | 530 | Flag the shipment or visit list as relevant | The short text describes the object sufficiently | |
115 | 550 | Enter a valid time frame (date from > date to) | Space: object requires documentation | |
116 | 551 | Only saved visit plans will be checked; (Change not saved) | Space: object requires documentation | |
117 | 552 | Only saved visit lists will be checked; (Change not saved) | Space: object requires documentation | |
118 | 600 | A customer can only be contained once in each visit plan | Space: object requires documentation | |
119 | 601 | Not possible to move visit plans | Space: object requires documentation | |
120 | 602 | You are not authorized to display customer master data | Space: object requires documentation | |
121 | 603 | Document &1 for document category &2 | Space: object requires documentation | |
122 | 604 | Save cancelled due to existing visit lists | Space: object requires documentation | |
123 | 605 | Type &1 is not permitted | The short text describes the object sufficiently | |
124 | 606 | A customer cannot be driver and co-driver at the same time | Space: object requires documentation | |
125 | 607 | Visit plan is no longer valid and therefore cannot be changed | Space: object requires documentation | |
126 | 608 | Visit list &1 cannot be changed (execution date is before today's date) | Space: object requires documentation | |
127 | 609 | Visit list &1 cannot be changed (locked due to transport link) | Space: object requires documentation | |
128 | 610 | Save terminated - error in number range object &1 - interval &2 | The short text describes the object sufficiently | |
129 | 611 | Calendar &2 could not be synchronized for customer &1 | The short text describes the object sufficiently | |
130 | 612 | Driver &1 is not defined as the customer in sales area &2 &3 &4 | The short text describes the object sufficiently | |
131 | 613 | Customer &1 is not defined in the sales area for the visit plan | The short text describes the object sufficiently | |
132 | 614 | Customer &1 is not defined in the sales area for the visit list | The short text describes the object sufficiently | |
133 | 615 | &1 customers were not transferred (do not exist in sales area) | The short text describes the object sufficiently | |
134 | 616 | Customer sequence incorrect. A sequence number must be unique | The short text describes the object sufficiently | |
135 | 617 | Not all visit plan texts were copied | The short text describes the object sufficiently | |
136 | 618 | Only special text objects are allowed | Space: object requires documentation | |
137 | 620 | The ship-to party of the delivery entered here must be a driver | The short text describes the object sufficiently | |
138 | 621 | Customer for delivery &1 is not the same as driver for visit list | The short text describes the object sufficiently | |
139 | 622 | Customer (&1) for this delivery should be a driver from the tour master | The short text describes the object sufficiently | |
140 | 623 | A speculative load should not be assigned for visit plan type &1 | The short text describes the object sufficiently | |
141 | 624 | Customer &1 is not relevant for this document &2 | The short text describes the object sufficiently | |
142 | 625 | Customer &1 is not a ship-to party in document &2 | The short text describes the object sufficiently | |
143 | 626 | A shipment document should not be assigned to one individual customer | The short text describes the object sufficiently | |
144 | 627 | Driver must be same as ship-to party (&1) of speculative load | The short text describes the object sufficiently | |
145 | 628 | The ship-to party of the delivery (&1) is a customer from the visit list | The short text describes the object sufficiently | |
146 | 629 | Customer &1 is not a sold-to party in document &2 | The short text describes the object sufficiently | |
147 | 630 | Text &1 for object &2, ID &3, language &4 does not exist | The short text describes the object sufficiently | |
148 | 631 | Unable to delete text &1 for object &2, ID &3, language &4 | The short text describes the object sufficiently | |
149 | 632 | Unable to create text &1 for object &2, ID &3, language &4 | The short text describes the object sufficiently | |
150 | 633 | Customizing: DSD tour status - visit plan type &1 is not relevant for DSD | Space: object requires documentation | |
151 | 635 | Maximum number of customers for this visit plan has been reached | The short text describes the object sufficiently | |
152 | 636 | Maximum number of customers for this visit plan has been reached | The short text describes the object sufficiently | |
153 | 637 | Error when reading a row | The short text describes the object sufficiently | |
154 | 638 | Error when inserting a row | The short text describes the object sufficiently | |
155 | 639 | Error when changing a row | The short text describes the object sufficiently | |
156 | 640 | Error when deleting a row | The short text describes the object sufficiently | |
157 | 641 | Error when calling a BAdI | The short text describes the object sufficiently | |
158 | 650 | Authorizations are missing for & visit list(s) | The short text describes the object sufficiently | |
159 | 700 | There is no print output for shipment status &1 (at least &2) | The short text describes the object sufficiently | |
160 | 701 | There is no print output for shipment type &1/ trans. planing point &2 | The short text describes the object sufficiently | |
161 | 702 | Application &1 object &2 message &3 selected | The short text describes the object sufficiently | |
162 | 703 | Message &1 was successfully processed | The short text describes the object sufficiently | |
163 | 704 | Errors occurred when processing message &1 &2 | The short text describes the object sufficiently | |
164 | 705 | Visit list is inactive; message will not be processed | The short text describes the object sufficiently | |
165 | 706 | No print output for visit plan type &1 | The short text describes the object sufficiently | |
166 | 707 | No messages were selected for processing | The short text describes the object sufficiently | |
167 | 708 | The message type must be entered in table /DSD/VC_MSGTYP | The short text describes the object sufficiently | |
168 | 711 | No authorization for message processing | The short text describes the object sufficiently | |
169 | 712 | The visit list is not assigned a shipment document | The short text describes the object sufficiently | |
170 | 713 | Transport document &1 does not exist | The short text describes the object sufficiently | |
171 | 714 | Changes to visit lists must be saved first | The short text describes the object sufficiently | |
172 | 715 | Message can only be displayed (shipment &1 is being processed by &2) | The short text describes the object sufficiently | |
173 | 716 | Messages can only be displayed (save changes to visit lists first) | The short text describes the object sufficiently | |
174 | 717 | Messages for shipment &1 have been processed and saved | The short text describes the object sufficiently | |
175 | 718 | Changes to messages were not saved for shipment &1 | The short text describes the object sufficiently | |
176 | 719 | Changes to messages were not saved for visit list &1 | The short text describes the object sufficiently | |
177 | 720 | Messages for visit list &1 have been processed and saved | The short text describes the object sufficiently | |
178 | 750 | Header data is missing for shipment or visit list | The short text describes the object sufficiently | |
179 | 751 | Component ID is missing | The short text describes the object sufficiently | |
180 | 752 | Incorrect combination of parameters when calling function module | The short text describes the object sufficiently | |
181 | 753 | Flags for driver scenario are set incorrectly in table /DSD/VC_VPTYPE | The short text describes the object sufficiently | |
182 | 754 | More than one shipment is linked with list when processing using VL | The short text describes the object sufficiently | |
183 | 755 | Shipment number of visit list number is missing | The short text describes the object sufficiently | |
184 | 756 | Visit list &1 does not exist | The short text describes the object sufficiently | |
185 | 757 | No items for visit list &1 | The short text describes the object sufficiently | |
186 | 758 | No reference documents for visit list &1 | The short text describes the object sufficiently | |
187 | 759 | Visit list &1 is not active | The short text describes the object sufficiently | |
188 | 760 | Error &1 while reading table /DSD/VC_VLTRADAT | The short text describes the object sufficiently | |
189 | 761 | /DSD/VC_VLTRADAT does not contain data for type &1 -> no further IDocs | The short text describes the object sufficiently | |
190 | 762 | Type of visit list &1 has TRHH indicator set | The short text describes the object sufficiently | |
191 | 763 | Visit list for shipment &1 not found | The short text describes the object sufficiently | |
192 | 764 | Message type &1 not defined in /DSD/VC_MSGTYP as relevant for output | The short text describes the object sufficiently | |
193 | 800 | Visit list not archived; checking residence time | The short text describes the object sufficiently | |
194 | 801 | Visit list not archived as settlement not successful | The short text describes the object sufficiently | |
195 | 802 | Visit list is being archived | The short text describes the object sufficiently | |
196 | 803 | Visit list not archived as settlement has not been carried out | The short text describes the object sufficiently | |
197 | 804 | You cannot change documents "&1" | The short text describes the object sufficiently | |
198 | 805 | Visit plan type &1 does not exist | The short text describes the object sufficiently | |
199 | 806 | Residence time &1 for visit plan type &2 is less than &3 days | The short text describes the object sufficiently |
History
Last changed on/by | 20130531 | SAP | |
SAP Release Created in | 200 |