| VW167 |
... Partner & was removed from leg (Key: & &) |
| VW168 |
... Partner & was copied to leg (Key: & &) |
| VW169 |
Changes to shipment header & (partially) incorrect |
| VW170 |
Start with automatic route determination for shipment & |
| VW171 |
Status 'Shipment completion' set in shipment & |
| VW172 |
Status 'Loading end' set in shipment & |
| VW173 |
Status 'Loading start' set in shipment & |
| VW174 |
Status 'Planned' set in shipment & |
| VW175 |
Status 'Checked in' set in shipment & |
| VW176 |
Status 'Shipment end' set in shipment & |
| VW177 |
Status 'Shipment start' set in shipment & |
| VW178 |
Shipment header & was changed |
| VW179 |
Start with changes to the shipment header data for shipment & |
| VW180 |
Date & is not valid |
| VW181 |
Time & is not valid |
| VW182 |
& Transportation point & does not exist |
| VW183 |
& Shipping point & does not exist |
| VW184 |
& The shipping point & / loading point & combination does not exist |
| VW185 |
Plant & does not exist |
| VW186 |
& Plant &/storage location & combination does not exist |
| VW187 |
& Customer/ship-to party & does not exist |
| VW188 |
& vendor & does not exist |
| VW189 |
Address & does not exist |
| VW190 |
Incoterm & does not exist |
| VW191 |
SD document catgegory must be & (not &) |
| VW192 |
Value &2 is not supported in domain &1 |
| VW193 |
Work area & contains & incorrect entries. See log |
| VW194 |
The total status should be & and not & |
| VW195 |
The point of departure of stage & (key & &) is empty |
| VW196 |
The target destination of stage & (key & &) is empty |
| VW197 |
Too many data are maintained for the leg category in stage & (key & &) |
| VW198 |
Stage & (Key & &), &: Definition is not unique |
| VW199 |
Stage & (key & &), &: Invalid location definition |
| VW200 |
Different shipment document types cannot be processed simultaneously |
| VW201 |
Shipments contain the same deliveries, therefore cannot be processed |
| VW202 |
'Change' function can only be used for column 'Shipment'. Display only |
| VW203 |
Place the cursor on a line within the list |
| VW204 |
Place the cursor on a column within the list |
| VW205 |
Select several shipments or place cursor on a line |
| VW206 |
Selection variant & missing for the list. Maintain in Customizing |
| VW207 |
Selection variant could not be created/changed successfully |
| VW208 |
The variant has been created anew |
| VW209 |
Selection variant is displayed only |
| VW210 |
& shipment(s) could not be refreshed |
| VW211 |
No display authorization for & shipment(s) |
| VW212 |
Enter name & for variant |
| VW213 |
The variant should be called &, not & |
| VW214 |
The transaction was started with user-specific variant & |
| VW215 |
Variant & does not exist |
| VW216 |
Printing/output authorizations missing for & shipment(s) |
| VW217 |
Enter a partner role |
| VW218 |
Begin with check of: & (Key: & & &). |
| VW219 |
Deliveries were assigned to shipment & |
| VW220 |
Shipment &: Begin with leg generation based on a location list |
| VW221 |
Leg generation carried out successfully |
| VW222 |
Leg generation could not be carried out successfully |
| VW223 |
Enter a sequence for the locations |
| VW224 |
Leg generation not possible - shipping type missing |
| VW225 |
Not everything could be delivered via the location itinerary |
| VW226 |
All deliveries in shipment & are already posted for GI (or not relevant) |
| VW227 |
Delivery & in shipment & is already posted for GI |
| VW228 |
All deliveries in shipment & were successfully posted for GI |
| VW229 |
Delivery & in shipment & could not be posted for GI |
| VW230 |
There are deliveries in shipment & that were not posted for GI |
| VW231 |
All dlvs in shipment & posted for GI, but some were already posted for GI |
| VW232 |
All deliveries in shipment & have already been billed (or not relevant) |
| VW233 |
Delivery & in shipment & has already been billed |
| VW234 |
All deliveries in shipment & were successfully billed |
| VW235 |
Delivery & in shipment & could not be billed |
| VW236 |
There are deliveries in shipment & that were not billed |
| VW237 |
All deliveries in shipment & billed, some had already been billed |
| VW238 |
Shipment &1: Status '&2' already set |
| VW239 |
Shipment &1: Set status '&2' |
| VW240 |
Shipment &1: Status '&2' set |
| VW241 |
Shipment &1: Status '&2' could not be set |
| VW242 |
Errors occurred during shipment completion (seelog) |
| VW243 |
Warnings were issued during shipment completion (see log) |
| VW244 |
Status '&1' set for &2 shipments |
| VW245 |
No log exists |
| VW246 |
Start by posting the deliveries in shipment & for goods issue |
| VW247 |
Start by billing the deliveries in shipment & |
| VW248 |
Specify the name of the variant |
| VW249 |
Variant valid for inbound shipments (but shipment type is outbound) |
| VW250 |
Variant valid for outbound shipments (but shipment type is inbound) |
| VW251 |
Delivery & in shipment & is not relevant for GI |
| VW252 |
Delivery & in shipment & is not relevant for billing |
| VW253 |
The billing messages are stored under collective run number & |
| VW254 |
Transportation processing activities after saving (printing?) incorrect |
| VW255 |
Shipment completion activities failed before saving |
| VW256 |
Shipment &1: Status '&2' reset |
| VW257 |
Action canceled by user |
| VW258 |
Delivery & in shipment & posted for GI |
| VW259 |
Delivery & in shipment & billed |
| VW260 |
Start deleting shipment & |
| VW261 |
Maint. partner type, part.no., ext.no.range and shipment changes together |
| VW262 |
No deliveries were found |
| VW263 |
No partner exists for the deliveries |
| VW264 |
Output type & is already assigned to another planning system |
| VW265 |
Logical system & is already assigned to another planning system |
| VW266 |
Shipments have different transp. planning points. Processing not possible |