VW - Shipment Processing Output
The following messages are stored in message class VW: Shipment Processing Output.
It is part of development package VTR in software component LE-TRA. This development package consists of objects that can be grouped under "SD R/3 transport processing".
It is part of development package VTR in software component LE-TRA. This development package consists of objects that can be grouped under "SD R/3 transport processing".
Message Nr ▲ | Message Text |
|---|---|
| 000 | *** Messages for transportation processing *** |
| 001 | & |
| 002 | Error at & &, Key: & & |
| 003 | Shipment type & does not exist |
| 004 | Transportation planning point & does not exist |
| 005 | Transaction & is not in table T180 |
| 006 | Shipment & has been saved |
| 007 | Forwarding agent & does not exist |
| 008 | & shipments have been saved (numbers: & - &) |
| 009 | Saving not necessary: no changes were made |
| 010 | Shipment & does not exist |
| 011 | Shipment & is currently being processed by user & |
| 012 | Delivery & is currently being processed |
| 013 | Shipment & was deleted |
| 014 | & shipments were deleted (numbers: & - &) |
| 015 | No authorization for maintaining shipments in transport.planning point & |
| 016 | No authorization for displaying shipments in transport.planning point & |
| 017 | No authorization for deleting shipments in transport.planning point & |
| 018 | No authorization for maintaining shipment type & |
| 019 | No authorization for displaying shipment type & |
| 020 | No authorization for deleting shipment type & |
| 021 | New shipment created with provisional number & |
| 022 | Select shipment header |
| 023 | Route & has no valid legs |
| 024 | The shipment hierarchy could not be set up (RC &) |
| 025 | The address could not be found in the address administrator |
| 026 | The service agent was copied in & out of & legs |
| 027 | Central posting block for the service agent &: & |
| 028 | Central purchasing block for the service agent &: & |
| 029 | Purchase block for reasons of quality: & for service agent &: & |
| 030 | Quality check: & for service agent &: & |
| 031 | Deliveries were not assigned to shipment & |
| 032 | Deletion is not possible. Shipment &1 contains handling units |
| 033 | Output cannot be maintained: no output determ.proced.for shipment type & |
| 034 | Copied from the delivery: & |
| 035 | Variant & in report & does not exist |
| 036 | Number range & is not an internal number range in RV_TRANSPO |
| 037 | Number range & is not an external number range in RV_TRANSPO |
| 038 | The changes have been saved |
| 039 | The object you have chosen cannot be changed |
| 040 | No shipments were found for the selection criteria |
| 041 | The object you have chose cannot be displayed |
| 042 | & is not a weight unit |
| 043 | & is not a unit of volume |
| 044 | Error in word processing (return code: &) |
| 045 | Deadlines cannot be maintained: no network profile in shiment type & |
| 046 | No deadlines have been entered for this shipment |
| 047 | Route & is not available |
| 048 | Error in & &, Index: & |
| 049 | Select a delivery first |
| 050 | Delivery & cannot be assigned to itself |
| 051 | No detail information exists for this field |
| 052 | Does it make sense to copy the route for a preliminary or subsequent leg? |
| 053 | Planning for shipment & has already been completed |
| 054 | Planning is not possible as planning is complete for the shipment |
| 055 | No shipments were found for the selection criteria |
| 056 | Shipments with provisional numbers & to & created |
| 057 | Position the cursor on a delivery (inbound) |
| 058 | You cannot move anything to this cursor position |
| 059 | Texts cannot be maintained: no TextDetrmProcdr available for TranspType & |
| 060 | Selection view could not be found |
| 061 | It is not possible to remove Shipment &1 |
| 062 | This action no longer possible: Transport &1 has already been scheduled |
| 063 | This action could not be completely carried out |
| 064 | End date precedes start date |
| 065 | End time precedes start date |
| 066 | Not possible: Delivery &1 has already been loaded |
| 067 | It is only possible to display this object |
| 068 | A document flow cannot be displayed for a new shipment |
| 069 | The transportation connection point & does not exist |
| 070 | Transportation connection point & is not a load tranfer point |
| 071 | Transportation connection point & is not a border crossing point |
| 072 | Shipping type preliminary leg/subsequent leg unnecessary |
| 073 | Shipping type preliminary/subsequent leg must be maintained. |
| 074 | Maintain shipping type |
| 075 | Delivery & of the shipment does not exist |
| 076 | Sorting cannot be carried out for the selected field |
| 077 | Shipments sorted by '&1' |
| 078 | Deliveries or inbound deliveries sorted by '&1' |
| 079 | Select a shipment |
| 080 | Shipment & contains no legs relevant for printing |
| 081 | Leg & not relevant for printing since leg indicator incorrect |
| 082 | Leg & not relevant for printing, carrier not same as output partner |
| 083 | Itinerary for shipment &1 adopted |
| 084 | Output was successfully issued |
| 085 | No output has been selected for printing |
| 086 | Output could not be issued |
| 087 | Transportation planning point: No address - country cannot be determined |
| 088 | Shipment &1 contains no deliveries |
| 089 | Externally specified shipment & is invalid |
| 090 | Shipment & already exists |
| 091 | No transportation connection points maintained |
| 092 | Shipping type & does not exist |
| 093 | Transportation condition & does not exist |
| 094 | & shipments without & ;; |
| 095 | Function not allowed: Transport.planning point & only for planning system |
| 096 | Deletion flag for service agents &: & |
| 097 | Deliveries in shipment & no longer exist |
| 098 | Transportation planning point can not be changed |
| 099 | Shipment type can not be changed |
| 100 | You can only have one ID for a point |
| 101 | Enter a customer or vendor |
| 102 | Select a stage of shipment or choose one using the cursor |
| 103 | Select at least one stage |
| 104 | Enter a date between & and & |
| 105 | Only one stage can be selected using the cursor |
| 106 | No further stages selected |
| 107 | Enter a point of departure |
| 108 | Enter a destination |
| 109 | Enter a sequence for each point of departure |
| 110 | Enter a different sequence for each point of departure |
| 111 | Departure sequence is missing: no leg could be determined |
| 112 | Leg determination is not defined for this shipment type |
| 113 | The header data have not been read for delivery &. |
| 114 | Leg determination has not been carried out (no destination) |
| 115 | Leg determination has not been carried out (no point of departure) |
| 116 | Leg determination is not defined for shipment document type & |
| 117 | Leg determination not possible as no deliveries exist |
| 118 | Overflow in a quantity field caused by delivery &1 |
| 119 | Overflow summing quantities in the deliveries |
| 120 | No leg determination possible since shipping type not maintained |
| 121 | No leg determination possible since shipping types VL and NL are missing |
| 122 | When calling function module &, tables/parameters & & & are missing |
| 123 | Value & is not allowed for the shipment completion type |
| 124 | Value & is not allowed for this service level |
| 125 | Value & is not allowed for processing control |
| 126 | Value & is not allowed for the leg indicator |
| 127 | Value & is not allowed for the route determination indicator |
| 128 | Checking the shipment header data: Return code & |
| 129 | Change the route in the shipment header from & to &: Return code & |
| 130 | Changing the service agent in the shipment from & to &: Return code & |
| 131 | Start functions by setting status 'planned' in shipment & |
| 132 | Start functions by setting status 'Check in' in shipment & |
| 133 | Start functions by setting status 'Loading start' in shipment & |
| 134 | Start functions by setting status 'Loading end' in shipment & |
| 135 | Start functions by setting status 'Shipment completion' in shipment & |
| 136 | Start functions by setting status 'start shipment' in shipment &. |
| 137 | Start functions by setting status 'Shipment end' in shipment & |
| 138 | Route & refers to points that do not exist |
| 139 | ... Create/change/delete section incorrect (key & &, category &, no. &) |
| 140 | No stages were selected |
| 141 | Error when adding a partner (key &) |
| 142 | Route determination terminated by user |
| 143 | Route already specified, not copied from the delivery |
| 144 | Copying the route from the delivery deactivated in Customizing |
| 145 | Route not copied from the deliveries - not the same |
| 146 | Route not copied from the deliveries - none exist |
| 147 | Route not copied from the deliveries (only poss. for outgoing shipments). |
| 148 | Route not copied successfully from the delivery |
| 149 | Route copied from delivery |
| 150 | Service agent already specified (not copied from delivery) |
| 151 | Copying service agents from the delivery deactivated in Customizing |
| 152 | Service agent not copied from the deliveries - not the same |
| 153 | Service agent not copied from deliveries - none exist |
| 154 | Service agent not copied from dlv. (only poss. for outgoing shipments) |
| 155 | Service agent not copied successfully from the delivery |
| 156 | Service agent copied successfully from the delivery |
| 157 | Leg determination executed |
| 158 | Leg determination was not executed |
| 159 | ... Create section successful (key & &, category &, no. &) |
| 160 | ... Delete section successful (Key & &, category &, no. &) |
| 161 | ... Change section successful (Key & &, category &, No. &) |
| 162 | Route & was successfully removed from the legs |
| 163 | Route & was successfully added to the legs |
| 164 | Route & was not successfully added to the legs |
| 165 | Partner & was successfully removed from the header and & legs |
| 166 | Partner & was successfully copied to shipment header and to & legs |
| 167 | ... Partner & was removed from leg (Key: & &) |
| 168 | ... Partner & was copied to leg (Key: & &) |
| 169 | Changes to shipment header & (partially) incorrect |
| 170 | Start with automatic route determination for shipment & |
| 171 | Status 'Shipment completion' set in shipment & |
| 172 | Status 'Loading end' set in shipment & |
| 173 | Status 'Loading start' set in shipment & |
| 174 | Status 'Planned' set in shipment & |
| 175 | Status 'Checked in' set in shipment & |
| 176 | Status 'Shipment end' set in shipment & |
| 177 | Status 'Shipment start' set in shipment & |
| 178 | Shipment header & was changed |
| 179 | Start with changes to the shipment header data for shipment & |
| 180 | Date & is not valid |
| 181 | Time & is not valid |
| 182 | & Transportation point & does not exist |
| 183 | & Shipping point & does not exist |
| 184 | & The shipping point & / loading point & combination does not exist |
| 185 | Plant & does not exist |
| 186 | & Plant &/storage location & combination does not exist |
| 187 | & Customer/ship-to party & does not exist |
| 188 | & vendor & does not exist |
| 189 | Address & does not exist |
| 190 | Incoterm & does not exist |
| 191 | SD document catgegory must be & (not &) |
| 192 | Value &2 is not supported in domain &1 |
| 193 | Work area & contains & incorrect entries. See log |
| 194 | The total status should be & and not & |
| 195 | The point of departure of stage & (key & &) is empty |
| 196 | The target destination of stage & (key & &) is empty |
| 197 | Too many data are maintained for the leg category in stage & (key & &) |
| 198 | Stage & (Key & &), &: Definition is not unique |
| 199 | Stage & (key & &), &: Invalid location definition |
| 200 | Different shipment document types cannot be processed simultaneously |
| 201 | Shipments contain the same deliveries, therefore cannot be processed |
| 202 | 'Change' function can only be used for column 'Shipment'. Display only |
| 203 | Place the cursor on a line within the list |
| 204 | Place the cursor on a column within the list |
| 205 | Select several shipments or place cursor on a line |
| 206 | Selection variant & missing for the list. Maintain in Customizing |
| 207 | Selection variant could not be created/changed successfully |
| 208 | The variant has been created anew |
| 209 | Selection variant is displayed only |
| 210 | & shipment(s) could not be refreshed |
| 211 | No display authorization for & shipment(s) |
| 212 | Enter name & for variant |
| 213 | The variant should be called &, not & |
| 214 | The transaction was started with user-specific variant & |
| 215 | Variant & does not exist |
| 216 | Printing/output authorizations missing for & shipment(s) |
| 217 | Enter a partner role |
| 218 | Begin with check of: & (Key: & & &). |
| 219 | Deliveries were assigned to shipment & |
| 220 | Shipment &: Begin with leg generation based on a location list |
| 221 | Leg generation carried out successfully |
| 222 | Leg generation could not be carried out successfully |
| 223 | Enter a sequence for the locations |
| 224 | Leg generation not possible - shipping type missing |
| 225 | Not everything could be delivered via the location itinerary |
| 226 | All deliveries in shipment & are already posted for GI (or not relevant) |
| 227 | Delivery & in shipment & is already posted for GI |
| 228 | All deliveries in shipment & were successfully posted for GI |
| 229 | Delivery & in shipment & could not be posted for GI |
| 230 | There are deliveries in shipment & that were not posted for GI |
| 231 | All dlvs in shipment & posted for GI, but some were already posted for GI |
| 232 | All deliveries in shipment & have already been billed (or not relevant) |
| 233 | Delivery & in shipment & has already been billed |
| 234 | All deliveries in shipment & were successfully billed |
| 235 | Delivery & in shipment & could not be billed |
| 236 | There are deliveries in shipment & that were not billed |
| 237 | All deliveries in shipment & billed, some had already been billed |
| 238 | Shipment &1: Status '&2' already set |
| 239 | Shipment &1: Set status '&2' |
| 240 | Shipment &1: Status '&2' set |
| 241 | Shipment &1: Status '&2' could not be set |
| 242 | Errors occurred during shipment completion (seelog) |
| 243 | Warnings were issued during shipment completion (see log) |
| 244 | Status '&1' set for &2 shipments |
| 245 | No log exists |
| 246 | Start by posting the deliveries in shipment & for goods issue |
| 247 | Start by billing the deliveries in shipment & |
| 248 | Specify the name of the variant |
| 249 | Variant valid for inbound shipments (but shipment type is outbound) |
| 250 | Variant valid for outbound shipments (but shipment type is inbound) |
| 251 | Delivery & in shipment & is not relevant for GI |
| 252 | Delivery & in shipment & is not relevant for billing |
| 253 | The billing messages are stored under collective run number & |
| 254 | Transportation processing activities after saving (printing?) incorrect |
| 255 | Shipment completion activities failed before saving |
| 256 | Shipment &1: Status '&2' reset |
| 257 | Action canceled by user |
| 258 | Delivery & in shipment & posted for GI |
| 259 | Delivery & in shipment & billed |
| 260 | Start deleting shipment & |
| 261 | Maint. partner type, part.no., ext.no.range and shipment changes together |
| 262 | No deliveries were found |
| 263 | No partner exists for the deliveries |
| 264 | Output type & is already assigned to another planning system |
| 265 | Logical system & is already assigned to another planning system |
| 266 | Shipments have different transp. planning points. Processing not possible |
| 267 | Condition stage & is already defined for procedure & |
| 268 | Condition & already exists in procedure & |
| 269 | Transit time of & days, & hours and & minutes is too long |
| 270 | Travelling time total exceeds transit time of route |
| 271 | No. of hours (&) not within allowed range (0-23) |
| 272 | No. of mins (&) not within allowed range (0-59) |
| 273 | No partner agreement for partner no./partner type &/& |
| 274 | Text ID & not created as an SD text (object ID 'VBBK') |
| 275 | Specified location & is not a border point |
| 276 | Partner type & not allowed - can only implement logical system ('LS') |
| 277 | Unexpected error during creation of billing documents for shipment &. |
| 278 | Shipment costs calculation for &. stage has already started |
| 279 | Shipment costs calculation for shipment & has already started |
| 280 | Shipment & checked in |
| 281 | Shipment & could not be checked in |
| 282 | Errors occurred during check-in. Read log carefully |
| 283 | Warnings were issued during check-in. Read log carefully |
| 284 | Check-in of shipments was executed |
| 285 | Shipment & will be checked-in again after query |
| 286 | Check-in of shipment & was interrupted after query |
| 287 | In shipment &, check-in status already set |
| 288 | Shipment & could not be checked in |
| 289 | Start with check-in of shipment & |
| 290 | Unit '&' is not defined as length unit |
| 291 | Single-column view not possible (see long text). |
| 292 | Change restricted shipment costs for shipment &1 are settled |
| 293 | Change restricted shipment costs for shipment &1 are calculated |
| 294 | Change restricted shipment &1 is processed for transportation |
| 295 | Distance and distance units must always be maintained together |
| 296 | Proposal values for duration of transportation conn. point not found |
| 297 | Customer & is a one-time customer (cannot be used as reference) |
| 298 | Handling units not changeable as they are used in shipment cost calc. |
| 299 | Shipment & cannot be deleted as shipment costing has already started |
| 300 | Maintain transp. connection points before this activity (see long text) |
| 301 | Enter a percentage greater than 0 |
| 302 | Enter a unit of measurement |
| 303 | Enter volume or weight |
| 304 | Enter a percentage between 0 and 100 |
| 305 | & Location specification insufficient |
| 306 | & The location is not identified uniquely |
| 307 | Error when carrying out internal log |
| 308 | & The location is different to the spec.in transp. connection point & |
| 309 | & location specification & contains & error(s) |
| 310 | & for customer & unloading point & does not exist |
| 311 | & address with number & does not exist |
| 312 | & warehouse number & does not exist |
| 313 | for warehouse number & goods issue door & does not exist |
| 314 | For warehouse number & goods receipt door & does not exist |
| 315 | Marker not replaced at level & in the log |
| 316 | & the location indicates non-existing address & & |
| 317 | & loading point is not allowed if the shipping point is maintained |
| 318 | & loading point is not allowed if the customer is maintained |
| 319 | & storage location is only allowed if the plant is maintained |
| 320 | & door only allowed if warehouse no. (and plant or ship.pnt) maintained |
| 321 | & warehoulse no.is only allowed if shipping point or plant maintained |
| 322 | Location with key & has no (valid) address |
| 323 | Maintaining/displaying the location address is not possible |
| 324 | Address could not be changed/inserted |
| 325 | Duration & has an invalid format |
| 326 | Duration & contradicts duration between start and end |
| 327 | Date specifications contain & error(s) |
| 328 | Special processing indicator & does not exist |
| 329 | Pricing procedure & does not exist |
| 330 | Leg & for shipment & does not exist |
| 331 | Location specifications were copied from point & |
| 332 | Enter corresponding warehouse number |
| 333 | Route itinerary is only unique with the goods issue date |
| 334 | Unit & does not exist |
| 335 | The specified unit & is not a length unit |
| 336 | The unit is missing for the distance |
| 337 | No inconsistencies determined for distance or duration |
| 338 | Inconsistent routes are selected |
| 339 | Processing not possible: Data blocked by user & |
| 340 | Filter type &1 is not defined |
| 341 | Filter routine &1 not found in program &2 |
| 342 | Filter routine &1 not suitable for item &2(&3) (category &4) |
| 343 | Sub-items for item &1(&2) not found |
| 344 | Item &1(&2) (category &3) cannot be processed |
| 345 | Error when processing item &1(&2) (filter routine &3) |
| 346 | No changed route stages exist |
| 347 | Function module READ_TABLE_BUFFERED: Parameter 'I_BUFFER_TYPE' incorrect |
| 348 | Service agent & can not be copied without address |
| 349 | Error during log processing (&) |
| 350 | Termination: Field catalog: Field & in DB table & does not exist |
| 351 | Error during log formatting (&) |
| 352 | Specifiy variant for delivery selection |
| 353 | Specify variant for "data and options" |
| 354 | For transportation chain, also specify "Data and Options" for process 2 |
| 355 | Also specify "Data and Options" for process & |
| 356 | Shipment type & in process & is inbound, not outbound |
| 357 | Shipment type & in process & is outbound, not inboun |
| 358 | Company code of transportation planning point in process & is different |
| 359 | Create shipment documents in process & |
| 360 | Processing combination, capacity, and sort criteria: & |
| 361 | Processing combination criteria |
| 362 | No combination criteria available; all deliveries assigned to a shipment |
| 363 | Processing sort criteria |
| 364 | No sort criteria available |
| 365 | Sort criteria "Weight, descending" will be created (see long text) |
| 366 | Sort criteria "Volume, descending" will be created (see description text) |
| 367 | No capacity criteria available |
| 368 | Processing capacity criteria |
| 369 | CAUTION: Delivery & exceeds maximum weight of & & |
| 370 | CAUTION: Delivery & exceeds maximum volume of & & |
| 371 | Creation of shipment & |
| 372 | Selecting deliveries |
| 373 | Creating shipments |
| 374 | Shipment: Log for collective processing & |
| 375 | Selection variant & for "Data and Options" not found or empty |
| 376 | Altogether, & documents were created, & of them saved to the database |
| 377 | Leg determination: Destination for preliminary leg taken from shipment & |
| 378 | Leg determination: Point of depart.for subseq.leg taken from shipment & |
| 379 | Collective run carried out as simulation. No data saved |
| 380 | Check-in log |
| 381 | Log '&' |
| 382 | Shipment & |
| 383 | Loading shipment &1 already completed |
| 384 | Loading shipment &1 already commenced |
| 385 | No external number assignment defined for shipment type & |
| 386 | Variant & for 'combination criteria' not found |
| 387 | Log can not be saved. Activity terminated |
| 388 | No shipments could be created |
| 389 | Select at least one leg |
| 390 | Copying of route from the delivery terminated by user |
| 391 | The customs office is not valid for the transportation point country |
| 392 | CPD service agents are not allowed here |
| 393 | Check the validity of the customs office |
| 394 | Planning profile & is only valid for incoming shipments |
| 395 | Planning profile & is only valid for outgoing shipments |
| 396 | Specify a name for the planning profile |
| 397 | Planning profile &: & shipments created |
| 398 | Select the deliveries to be processed from the planning proposal |
| 399 | See log for planning proposal |
| 400 | ******* Archiving messages ************* |
| 401 | Archiving terminated. There are no shipping types |
| 402 | Archiving terminated. There are no transportation planning points |
| 403 | Program cannot be run at present |
| 404 | Archiving terminated. No archiving authorization |
| 405 | Archiving terminated. Archive could not be opened |
| 406 | Shipment &1 can be archived |
| 407 | The following shipment is not linked to any other shipments |
| 408 | The following shipments are linked within a transportation chain |
| 409 | Shipment_&1:_Message_&4_not_documented_(info-parameter:_&2,_&3) |
| 410 | Shipment &1 cannot be archived |
| 411 | Shipment &1 cannot be archived because it is linked to shipment &2 |
| 412 | Shipment &1 lies outside the specified shipment number range |
| 413 | Shipment &1 has overall status &2 (required status = &3). |
| 414 | Shipment &1 was created on &2 (required = before &3). |
| 415 | Shipment &1 was changed on &2 (required before &3) |
| 416 | Dlv. &2 in shpmnt &1 has transprt. planning status &3 (required:' '/C). |
| 417 | Dlv. &2 in shpmnt &1 has goods movement status &3 (required:' '/C) |
| 418 | Checking logic is not maintained (Tran.VORT). Standard values are taken |
| 419 | WARNING: Delivery &3 in shipment &2 does not exist. Already archived? |
| 420 | WARNING: Shipment &2 for delivery &3 does not exist. Already archived? |
| 421 | WARNING: Database error: Shipment &2 has no header data |
| 422 | INTERNAL ERROR: Transportation network incorr. numbered (VTTP &1: &2#&3) |
| 423 | INTERNAL ERROR: Transportation network incorr. numbered (VBFA &1: &2#&3) |
| 424 | Could not find any shipments that can be archived |
| 425 | Deletion terminated. Archive could not be opened |
| 426 | Deletion terminated. Customizing: COMMIT counter not defined |
| 427 | Deletion of table &2 not possible or only partly successful |
| 428 | Shipment &1 has total shipment calculation status &2 (needed: ' '/'C') |
| 429 | Could not find any shipments that can be deleted |
| 430 | Shipment &1 can be deleted |
| 431 | Shipment &1 deleted |
| 432 | Reload was terminated. Archive could not be opened |
| 433 | The archive contains no shipments |
| 434 | Shipment &1 cannot be reloaded. It already (partly) exists (Tab. &2) |
| 435 | Shipment &1 was found in the archive and can be reloaded |
| 436 | Shipment &1 was reloaded successfully |
| 437 | Shipment &1 could not be reloaded |
| 438 | For shipment &1, shipment cost document &2 not yet activated |
| 439 | Overview for general messages |
| 440 | Overview for shipments that can be archived |
| 441 | Overview for shipments that cannot be archived |
| 442 | There is no data on shipments that cannot be archived |
| 443 | There are no general messages |
| 444 | Overview statistical data |
| 445 | Overview for shipments that can be deleted |
| 446 | Overview for deletion problems |
| 447 | Deletion carried out |
| 448 | Overview for reloaded shipments |
| 449 | No reloadable shipments found |
| 450 | Overview of reloading problems |
| 451 | Reloading successful |
| 452 | Enter documents that can be archived without check |
| 453 | Read checking logic ... OK |
| 454 | Read shipment types ... OK |
| 455 | Read transportation planning points ... OK |
| 456 | Open archive file ... OK |
| 457 | Program &2: Read shipmemt headers |
| 458 | Program run &2: Read shipment items |
| 459 | Program run &2: Check consistency of the database entries read. |
| 460 | Program run &2: Read data for shipments that can be archived |
| 461 | Program run &2: Check suitability for archiving of shipments read |
| 462 | Program run &2: Move archivable shipments to archive |
| 463 | Close archive, log will be issued |
| 464 | Program run &2: Read shipments from the archive |
| 465 | Program run &2: Delete shipments |
| 466 | WARNING: Shipments archiving could be duplicated (program error) |
| 467 | Shipment &1 will be archived without being checked |
| 468 | Enter shipment numbers in the 'archive without check' area |
| 469 | For archiving without check, enter shipment numbers below |
| 470 | Only use 'archiving w/o check' if absolutely necessary |
| 471 | Maintain shipment number below only if 'archiving w/o check' |
| 472 | Shipment &1 is not in the area specified. Not reloaded |
| 473 | Shipment &1 is being written to a new archive |
| 474 | Enter the name of the profile |
| 475 | Enter a unit of weight |
| 476 | Enter a volume unit |
| 477 | Processing of capacity criteria; no shipments created |
| 478 | Shipment weight & fails to meet minimum weight of & |
| 479 | Shipment volume & fails to meet minimum volume of & |
| 480 | No.of deliveries & in shipment fails to meet minimum of & deliveries |
| 481 | Delivery & is not assigned to a shipment |
| 482 | Delivery & was assigned to shipment & |
| 483 | Delivery & does not fit into any group and is therefore not considered |
| 484 | Only enter one activity (create, change or delete) |
| 485 | Processing step |
| 486 | Read shipment & |
| 487 | Processing shipment &: Start |
| 488 | Save shipment & |
| 489 | Posting goods issue for delivery & |
| 490 | & & & & |
| 491 | Shipment &: Actions for '&' |
| 492 | Shipment &: Output processing for '&' |
| 493 | Read activities profile & |
| 494 | Posting goods issue for deliveries in shipment & |
| 495 | Billing the deliveries in shipment & |
| 496 | Trigger output print for shipment & (and dependent documents) |
| 497 | Actions not successful, status reset |
| 498 | Subsequent statuses also reset |
| 499 | Delivery & does not exist |
| 500 | Problems with ALV: List could not be displayed |
| 501 | There is no log for processing the planning proposal |
| 502 | Billing for delivery & |
| 503 | Shipment &1: Output &2 &3 &4 |
| 504 | Shipping unit &1: Output &2 &3 &4 |
| 505 | Billing doc &1: Output &2 &3 &3 |
| 506 | Delivery &1: Output &2 &3 &4 |
| 507 | Object &1: Output &2 &3 &4 |
| 508 | Shipment &1: Set to status '&2' with errors / warnings |
| 509 | Shipment &1: Status '&2' could not be reset |
| 510 | Save shipments |
| 511 | Processing shipment &: Header data |
| 512 | Processing shipment &: Set status (if available) |
| 513 | Processing shipment &: Items |
| 514 | Delete shipment & |
| 515 | Processing shipment &: End |
| 516 | Field '&1'(&2-&3) cannot be maintained in general |
| 517 | Field '&1' (&2-&3) cannot be changed |
| 518 | Processing shipment &: Stages |
| 519 | Field '&' does not exist in table & |
| 520 | Old value: '&1' New value: '&2' |
| 521 | Leg &1: Delivery &2 cannot be assigned because it is not in the shipment |
| 522 | Stage category & is not available |
| 523 | Error occured during 'EXPORT TO MEMORY' for shipment data |
| 524 | Error occured in 'EXPORT TO MEMORY' for address data |
| 525 | Error occured in 'IMPORT FROM MEMORY' for shipment data |
| 526 | Error occured in 'IMPORT FROM MEMORY' for shipment data |
| 527 | Transaction &1, program &2, screen &3 |
| 528 | Field & |
| 529 | Log for batch input processing |
| 530 | Errors in batch input processing |
| 531 | Stack processing goods issue for deliveries in shipment & |
| 532 | Error in Customizing of shipping deadlines for shipment type & |
| 533 | Enter an event |
| 534 | Enter an operation mode |
| 535 | Batch job & planned |
| 536 | Batch job execution terminated. Return code: & |
| 537 | No tender possible for shipment & (forwarding agent missing) |
| 538 | Tender not possible for shipment & (stages missing) |
| 539 | Transaction & is old! |
| 540 | Format error on entering data. Use format hhhhhhh:mm |
| 541 | Shipment & selected |
| 542 | Shipment & not selected (already displayed) |
| 543 | Shipment & not selected (different transportation planning point) |
| 544 | Shipment & not selected (different shipment type) |
| 545 | Shipment & not selected (deliveries already displayed) |
| 546 | Shipment & not selected (shipment blocked) |
| 547 | Shipping material not copied as means of transport not unique |
| 548 | Means of transport not copied from deliveries as not unique |
| 549 | Means of transport not copied from deliveries as none exists |
| 550 | Mass maintenance of shipment: & |
| 551 | You are not authorized to maintain shipment & |
| 552 | No maintenance authorizations for & shipment(s) |
| 553 | Field & is not ready for input. Reference value has not been copied |
| 554 | Select at least one shipment |
| 555 | A warning message was issued when the reference was copied (see log) |
| 556 | Select at least one column |
| 557 | Check selection log |
| 558 | Means of transport could not be copied from delivery |
| 559 | Means of transport could not be copied from delivery |
| 560 | The shipment status was canceled due to erroneous dangerous goods check |
| 561 | Status cannot be set because of dangerous goods block indicator |
| 562 | Status cannot be set because status "planned" has not been set |
| 563 | Shipment does not contain any dangerous goods |
| 564 | Shipment &1 contains no materials |
| 565 | Status cannot be undone because subsequent statuses have already been set |
| 566 | No deliveries exist in shipment & |
| 567 | No inbound deliveries in shipment & |
| 568 | Shipment & does not exist (check your entry) |
| 569 | Shipment & is not an inbound shipment |
| 570 | Selection of deliveries for empty shipment not allowed |
| 571 | Pick deliveries & completely |
| 572 | Saving not possible because external shipment numbers missing |
| 573 | Tender status deleted because forwarding agent & was deleted |
| 574 | Tender status deleted because stages deleted |
| 575 | Shipping type already filled out (not copied from delivery) |
| 576 | Shipping type not copied from deliveries because not unique |
| 577 | Shipping type not copied from deliveries because none exist |
| 578 | Shipping type could not be copied from delivery |
| 579 | Shipping type could not be copied from delivery |
| 580 | No variants to be converted |
| 581 | &1 of &2 selection variants were converted |
| 582 | New selection variant & already exists |
| 583 | Old selection variant & cannot be deleted |
| 584 | New selection variant & cannot be generated |
| 585 | Old selection variant & contains inbound and outbound parameters |
| 586 | Old selection variant &1 was converted to &1_IN and &1_OUT |
| 587 | Special processing already filled out (was not copied from delivery) |
| 588 | Special processing not copied from deliveries because not unique |
| 589 | Special processing not copied from deliveries because none exist |
| 590 | Special processing could not be copied from delivery |
| 591 | Special processing could not be copied from delivery |
| 592 | Shipment category already filled out (not copied from delivery9 |
| 593 | Shipment category not copied from deliveries because not unique |
| 594 | Shipment category not copied from deliveries because none exist |
| 595 | Shipment category could not be copied from delivery |
| 596 | Shipment category could not be copied from delivery |
| 597 | Problem in delivery split: & & & |
| 598 | Incorrect starting release for XPRA (only possible as of 4.5B) |
| 599 | Incorrect target release for XPRA (only possible as of 4.6A) |
| 600 | Reporting to the Graphical Transportation Information System |
| 601 | No deliveries found for specified order & |
| 602 | No deliveries specified for the selection variant |
| 603 | No shipments specified for selection variant |
| 604 | No corresponding shipments could be determined |
| 605 | Selection variant & is not allowed |
| 606 | Select an issuing type |
| 607 | No delivery selected |
| 608 | Select exactly one stage of shipment |
| 609 | Select exactly one point |
| 610 | Select exactly one shipment stage OR one point |
| 611 | No stages and no points could be be determined for the shipment |
| 612 | There are deliveries that are not allocated to a shipment |
| 613 | There are shipments without stages and points |
| 614 | There are legs without deliveries |
| 615 | No shipment stages selected |
| 616 | Position the cursor on a sort field |
| 617 | The number of days entered must be in the range of 0-99 |
| 618 | The number of hours entered must be in the range 0-23 |
| 619 | The number of minutes entered must be within the range of 0-59 |
| 620 | Function not yet supported |
| 621 | Maintain graphic profile & & & in Customizing for this client |
| 622 | Use the graphics window last opened |
| 623 | The cursor is not on a field with a document number |
| 624 | No address available |
| 625 | Position cursor on a shipment number for selection |
| 626 | Planning profile & does not exist |
| 627 | Position cursor on a delivery for selection |
| 628 | There are no deadlines for the selected deliveries/shipments |
| 629 | Several shipments were determined. Enter the shipment number |
| 630 | No corresponding shipments could be determined |
| 631 | Enter at least one selection criterion |
| 632 | No detailed information available for the selected field |
| 633 | You cannot sort using this field |
| 634 | Display of variants not possible because shipment & does not exist |
| 635 | Display of variants not possible for empty shipments |
| 636 | Enter a shipment number (required) |
| 637 | Partner maint.not possible; Customizing shpmnt type &1 does not have &2 |
| 638 | Text maint.not possible; Customizing shipment type &1 does not have &2 |
| 639 | Processing shipment &: Handling units |
| 640 | You cannot place the cursor here because entry missing - see long text |
| 641 | System has placed cursor on closest table entry |
| 642 | The combination entered for & is not permitted |
| 643 | &1 has to be entered as well as &2 |
| 644 | Enter a location combination for which the specification & is valid |
| 645 | & entries could not be added due to previous deleted entries |
| 646 | Maintain generic entry (&1 &2 weight group) that is allowed |
| 647 | Enter a weight group (required entry) |
| 648 | Transportation planning point & can only be used for external plng system |
| 649 | Message type & is not defined |
| 650 | Double-click on the object to display object information |
| 651 | Select deliveries to be processed by the delivery split |
| 652 | Select shipments with the same delivery split profiles |
| 653 | Maintain the delivery split profile for shipment type & |
| 654 | Shipm.& contains changed means of transp.and packing materials (s.descr.) |
| 655 | Reset the status to delete execution deadlines |
| 656 | Select exactly one shipment |
| 657 | Select at least one shipment |
| 658 | Delivery split not possible since shipment & already completed |
| 659 | Maint. of MTr for shipment &1 blocked because delivery split was performd |
| 660 | Split not possible for shipment &1, deliveries &2 |
| 661 | Split not possible for shipment &1, deliveries &2 |
| 662 | Split not possible for shipment &1, deliveries &2 |
| 663 | Split not possible for shipment &1, deliveries &2 |
| 664 | Split not possible for shipment &1, deliveries &2 |
| 665 | Shipment &: Generation of delivery items for HU not defined |
| 666 | Shipment &: Generation of delivery items for HU flagged |
| 667 | Set tender status for shipment only, not possible for delivery |
| 668 | Tender status for shipment can only be set using "change" mode |
| 669 | Total weight &1 &2 is more than allowed total weight for shipment &3 &4 |
| 670 | Save your changes before leaving change mode |
| 671 | Select shipments and associated deliveries |
| 672 | Shipment has been changed, cannot be removed |
| 673 | Shipment has been changed, cannot be removed |
| 674 | Select a single shipment |
| 675 | Select only one shipment or delivery for detail view |
| 676 | Assignment not possible. Shipment has been marked for deletion |
| 677 | Shipment type or planning point of forwarding agent & incomplete |
| 678 | Save changes made to worklist before exiting |
| 679 | User & has not been assigned to a forwarding agent |
| 680 | -- Messages for the matchcode for routes---- |
| 681 | No data determined for the selection specified |
| 682 | Ext. vendor ID has no value. Delete the selection line or enter a value |
| 683 | Delivery &2 in shipmnt &1 has total processing status &3 (required:' '/C) |
| 684 | Allowed total weight &1 &2 greater than defined in route &3 (there &4 &2) |
| 685 | ---- Output for Delivery Selection for Transporation Planning System----- |
| 686 | & output records created. & could not be created |
| 687 | No deliveries found for selection specified |
| 688 | Variant & for program & and screen & does not exist |
| 689 | Weight not calculated correctly because handling unit has changed |
| 690 | Save the shipment to cancel the tender quotation |
| 691 | Shipments created & (&), Shipments deleted & |
| 692 | Enter conditions for the shipment search |
| 693 | Shipment still contains open deliveries |
| 695 | Shipment costs for shipment not yet archived |
| 696 | Shipment &1 is neither in the database nor in the archive |
| 697 | Not all deliveries are in the database or in the archive |
| 698 | Shipment &1 read from the archive |
| 699 | Shipment &1 archived; display of document flow not possible |
| 700 | Messages from the update task |
| 701 | Error at & & (RC: &) |
| 702 | Maintain the "Table" field first |
| 703 | No maintenance authorization f. shipments w/ transportation svce agent & |
| 704 | No display authorization for shipments with transportation svce agent & |
| 705 | No deletion authorization for shipments with transportation svce agent & |
| 706 | Table & is not relevant for the shipment change document |
| 707 | Field & does not exist in table & |
| 708 | Unit '&' is not defined as a unit of measurement |
| 709 | The weight and weight unit must always be maintained together |
| 710 | Error displaying transport chain |
| 711 | Continuous move: There are no dependencies to other transports |
| 712 | Means of transport not created because delivery was split |
| 713 | Vendor &1 is locked; see long text |
| 714 | Plant &1 is no valid Plant |
| 715 | Supplier &1 is no valid Supplier |
| 729 | --- Output for Shipment Processing for Forwarding Agents --- |
| 730 | Selected shipments are destined for a different forwarding agent |
| 750 | Outputs for XPRAS |
| 751 | Number of shipments read: & |
| 752 | Number of shipments to be corrected: & |
| 753 | Number of shipments updated |
| 754 | Not all shipments could be updated |
| 755 | Program only necessary in Releases 30A and 30B |
| 756 | Program only required in Releases 30A through 30F and 31G through 31L |
| 757 | Number of changed routes: & |
| 758 | Number of changed stages: & |
| 759 | Program CVVTSAIN can only be started during a system upgrade |
| 760 | Program only needed in Releases 22, 30A to 31Z and 40A/40B |
| 761 | XPRA CVTVLPTR is only necessary in releases up to and including 30C |
| 762 | XPRA CVTVLPTR successfully completed |
| 763 | App.: SD Transportation XPRA CVTVLPTR |
| 764 | Table TVLP could not be blocked |
| 765 | Number of converted route determination entries: & |
| 766 | Table TVLP could not be modified |
| 767 | Table TVLP could not be unblocked |
| 768 | XPRA CVTVTRBL (Tables VTTK, VTTS, VTPA): beginning at & & |
| 769 | Table &: Altogether & records changed |
| 770 | XPRA CVTVTRBL (Tables VTTK, VTTS, VTPA): End at & & |
| 771 | XPRA CVTVTRBL not required if the old Release is 2.0, 2.1, 2.2, etc. |
| 772 | XPRA CVTVTRBL: Start with conversion in client & |
| 773 | XPRA CVTVTRBL: Client &, Table &: & entries converted |
| 774 | XPRA CVTVTRBL: Conversion in client & finished |
| 775 | Number of converted country/zone combinations: & |
| 776 | & is not a valid & |
| 777 | Program CVVTSAIN is only required for upgrades from Release 4.0A and 4.0B |
| 778 | Number of converted address references: & |
| 779 | Value & for field & is not defined |
| 780 | Number of successful processed shipments: & |
| 781 | Number of successful processed deliveries: & |
| 782 | You can only start program CVTVRSZ1 during an upgrade |
| 785 | Mode-of-transport category & is not allowed |
| 786 | Copying of deadlines from delivery terminated by user |
| 787 | Copying of shipping type from delivery terminated by user |
| 788 | Copying of special processing from delivery terminated by the user |
| 789 | Copying of shipment category of delivery terminated by the user |
| 790 | Copying of means-of-transport type from delivery terminated |
| 791 | XPRA CVTVTKTR completed successfully |
| 792 | Application: Shipment XPRA CVTVTKTR |
| 793 | Table TVTK could not be blocked |
| 794 | Table TVTK could not be modified |
| 795 | Table TVTK cound not be unlocked |
| 796 | Copying of forw.agent from delivery terminated by user |
| 797 | XPRA CVTVTKTR only required in Releases 30A through 45B |
| 798 | Re-determination of duration and distance terminated by user |
| 800 | Messages from function modules |
| 801 | Specification SELECTION_SET and SELECT_OPTIONS are alternatives |
| 802 | You are not authorized to display the change document |
| 803 | Goods types directory could not be determined |
| 804 | Goods types directory missing |
| 805 | No goods types found |
| 806 | Delivery &1 not relevant for shipment |
| 807 | The total weight cannot be calculated due to field overflow |
| 808 | No shipping material fields, because shipping materials are not clear |
| 809 | Shipping type & does not match shipping type & for route & |
| 810 | Means-of-transport type & will be replaced by & |
| 811 | Means of transport type & has invalid packaging material type & |
| 812 | Means-of-transport type not allowed for means of transport & |
| 813 | Means of transport & not specified |
| 814 | Packaging material type & not maintained for means of transport & |
| 815 | Shipping type & does not match shipping type & for route & |
| 816 | Checking means-of-transport capacity not possible. No criteria |
| 817 | Checking means-of-transport capacity not possible. No weight specified |
| 818 | Checking means-of-transport capacity not possible. No volume specified |
| 819 | Checking means-of-transp.capacity for means-of-transp.type not possible |
| 820 | Maximum weight used by means of transport exceeded |
| 821 | Maximum volume used by means of transport exceeded |
| 822 | Checking means-of-transport capacity not possible. No criteria |
| 823 | Means of transport created for shipment |
| 824 | Means of transport created for shipment. Check shipment |
| 825 | Earliest collection date must be before latest date. Check the date |
| 826 | Earliest delivery date must be before latest date. Check the date |
| 827 | Collection must take place before delivery. Check the date |
| 828 | Error during generation of delivery item with &1 for HUs |
| 829 | New block of shipments and deliveries not possible after split |
| 830 | Change not possible since called from document flow |
| 831 | Shipment number &1 of the number range object &2 is in critical area |
| 832 | Last shipment number &1 of the number range object &2 has been assigned |
| 833 | No country specified for zone selection |
| 845 | You cannot currently lock the transaction |
| 846 | Delivery & is currently being processed by user & |
| 847 | Delivery & has transportation blocking reason & |
| 848 | Number of deliveries with transportation blocking reason: & |
| 849 | Number of selected deliveries is too high (&, max. &). Improve selection |
| 850 | Log of delivery selection |
| 851 | Number of selected indices: & |
| 852 | Number of deliveries found: & |
| 853 | Number of selected delivery items: & |
| 854 | Delivery & is currently blocked by another user |
| 855 | Delivery & already in transportation planning |
| 856 | Number of blocked deliveries: & |
| 857 | Number of deliveries already processed: & |
| 858 | Number of deliveries copied: & |
| 859 | Delivery & has no items |
| 860 | Delivery & has no items relevant for packing |
| 861 | Delivery & selected |
| 862 | Delivery & included in shipment & |
| 863 | The selection log is empty |
| 864 | Number of deliveries found: & (see log) |
| 865 | Returns delivery & contains delivery items |
| 866 | Standard delivery & contains returns items |
| 867 | Delivery & was not taken into account |
| 868 | Inbound delivery & not taken into account |
| 869 | Inbound delivery & contains different plants in the items |
| 870 | Delivery & does not exist |
| 871 | Delivery & already transmitted to planning system & |
| 872 | Deliv. & contains in the items plants that are not allowed |
| 873 | No plants assigned to the company code of the planning point found |
| 874 | No (existing) document number named in this log line |
| 875 | Document &1 does not exist |
| 876 | No authorization for setting status &1 for shipment type &2 |
| 877 | No authorization for resetting status &1 for shipment category &2 |
| 878 | Internal number range is not defined for shipment type &1 |
| 879 | Delivery & is already in shipment & as a preliminary leg |
| 880 | Delivery & already exists in shipment & as a subsequent leg |
| 881 | Delivery & wihout vendor not included in shipment & |
| 882 | Copying of deadlines from delivery was activated in Customizing |
| 883 | Copying of deadlines from delivery terminated by user |
| 884 | Deadlines copied from delivery |
| 885 | &1 &2 |
| 886 | Only 1 shipment selected |
| 887 | Print profile & is invalid |
| 888 | Provisional delivery &1 could not be deleted |
| 889 | Provisional delivery &1 could not be deleted |
| 890 | No details could be displayed for provisional delivery &1 |
| 891 | Deadlines for start and end of loading were not copied from deliveries |
| 892 | Deadlines for begin and end of transportation not copied from deliveries |
| 893 | Shipment type or planning point of forwarding agent & not defined |
| 894 | Delivery & already sent to forwarding agent & |
| 895 | Position the cusor on a field with a number |
| 896 | Do not select more than seven days |
| 897 | Enter at least one date |
| 898 | Select at least one status |
| 899 | Select up to eight transportation planning times simultaneously |