SAP ABAP Message Class JR (IS-M/SD: Truck Route)
Basic Data
Hierarchy
☛
IS-M (Software Component) SAP MEDIA
⤷
IS-M (Application Component) SAP Media
⤷
JSD (Package) Appl. dev. R/3 Publishing Sales and Distribution System
IS-M (Software Component) SAP MEDIA⤷
IS-M (Application Component) SAP Media⤷
JSD (Package) Appl. dev. R/3 Publishing Sales and Distribution System 
Attributes
| Message class |  |
JR |
| Short Description |  |
IS-M/SD: Truck Route |
| Changed On |  |
20130531 |
| Last Changed At |  |
113341 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 |  000 |
The short text describes the object sufficiently | ||
| 2 | 001 |
Truck route & already exists | ||
| 3 | 002 |
Truck route & has a deletion indicator. Processing not possible | ||
| 4 | 003 |
Dimension of & is not length | ||
| 5 | 004 |
Start time + duration exceeds end time | ||
| 6 | 005 |
Time to be checked is not between start and end time | ||
| 7 | 006 |
Value is not correct: Max. 71 hours, 59 minutes. No special symbols. | ||
| 8 | 007 |
Truck route & could not be created | ||
| 9 | 008 |
Truck route & could not be changed | ||
| 10 | 009 |
Truck route & could not be deleted | ||
| 11 | 010 |
Truck route contract & could not be created | ||
| 12 | 011 |
Truck route contract & could not be deleted | ||
| 13 | 012 |
Truck route contract & could not be deleted | ||
| 14 | 013 |
Start date is later than end date | ||
| 15 | 014 |
Dimension of & is not 'time' | ||
| 16 | 015 |
Truck route contract & already exists in table & | ||
| 17 | 016 |
Truck route contract & has deletion indicator - processing not possible | ||
| 18 | 017 |
Truck route contract & has no items | ||
| 19 | 018 |
Route contract & is flagged for deletion | ||
| 20 | 019 |
Template truck route contract & has no items | ||
| 21 | 020 |
Validity period for item is outside header interval | ||
| 22 | 021 |
Start date was not entered | ||
| 23 | 022 |
End date was not entered | ||
| 24 | 023 |
Validity period overlaps with an item in this truck route contract | The short text describes the object sufficiently | |
| 25 | 024 |
Truck route & is locked | ||
| 26 | 025 |
Truck route contract & is locked | ||
| 27 | 026 |
Truck route is not assigned to a truck route contract | ||
| 28 | 027 |
Truck route contract & does not exist | ||
| 29 | 028 |
Truck route contract has no items | ||
| 30 | 029 |
Truck route & for a truck route contract item does not exist | ||
| 31 | 030 |
Forwarding agent is not assigned a truck route contract | ||
| 32 | 031 |
Truck route & is flagged for deletion | ||
| 33 | 032 |
Loaded running distance specified - please also enter load unit | ||
| 34 | 033 |
Load unit specified - please also enter loaded running distance | ||
| 35 | 034 |
Empty running distance specified - please also enter unit | ||
| 36 | 035 |
Empty unit specified - please also enter empty running distance | ||
| 37 | 036 |
Please make entries in all fields for pricing statistics | ||
| 38 | 037 |
Validity period overlaps with item in truck route contract & | ||
| 39 | 038 |
Specify either a superior or a subordinate truck route | The short text describes the object sufficiently | |
| 40 | 039 |
Truck route & does not exist | ||
| 41 | 040 |
Truck route &1 is being processed by &2 | Space: object requires documentation | |
| 42 | 041 |
Indicator 'BP Post' can only be selected if BP is required | ||
| 43 | 042 |
Indicator 'Printing works required' can only be selected if BP not req. | ||
| 44 | 043 |
Daily truck routes were saved | The short text describes the object sufficiently | |
| 45 | 044 |
Error occurred while saving daily truck routes | The short text describes the object sufficiently | |
| 46 | 045 |
Daily truck route(s) were deleted | The short text describes the object sufficiently | |
| 47 | 046 |
Error occurred while deleting daily truck route(s) | The short text describes the object sufficiently | |
| 48 | 047 |
Daily truck route & on & is locked | The short text describes the object sufficiently | |
| 49 | 048 |
Unloading point & does not exist | The short text describes the object sufficiently | |
| 50 | 049 |
Number range object missing for loading/unloading point | The short text describes the object sufficiently | |
| 51 | 050 |
Address for loading/unloading point & does not exist | ||
| 52 | 051 |
Loading/unloading point & already exists | ||
| 53 | 052 |
Loading/unloading point & has a deletion indicator - processing not poss. | The short text describes the object sufficiently | |
| 54 | 053 |
Loading/unloading point & is flagged for deletion | The short text describes the object sufficiently | |
| 55 | 054 |
General unloading points must not be assigned BPs or printing works | The short text describes the object sufficiently | |
| 56 | 055 |
Unloading point for business partner: Please specify business partner | ||
| 57 | 056 |
Loading/unloading point printing works: Please specify plant, not BP | The short text describes the object sufficiently | |
| 58 | 057 |
Business partner & has deletion indicator - usage not allowed | The short text describes the object sufficiently | |
| 59 | 058 |
Business partner & does not exist with function 'Post' | The short text describes the object sufficiently | |
| 60 | 059 |
Storage area unit & & has incorrect dimension | The short text describes the object sufficiently | |
| 61 | 060 |
Capacity unit & & has incorrect dimension | The short text describes the object sufficiently | |
| 62 | 061 |
Storage area specified - please also enter storage area unit | The short text describes the object sufficiently | |
| 63 | 062 |
Storage area unit specified - please also enter storage area | The short text describes the object sufficiently | |
| 64 | 063 |
Warehouse capacity specified - please also enter capacity unit | The short text describes the object sufficiently | |
| 65 | 064 |
Capacity unit specified - please also enter warehouse capacity | The short text describes the object sufficiently | |
| 66 | 065 |
Validity period for loading/unloading point begins in the past | The short text describes the object sufficiently | |
| 67 | 066 |
Start date of validity should not be later than end date | The short text describes the object sufficiently | |
| 68 | 067 |
Loading/unloading point type of reference object does not match entry | The short text describes the object sufficiently | |
| 69 | 068 |
No address found for business partner & with function & | The short text describes the object sufficiently | |
| 70 | 069 |
Please only specify reason for alternative actual vehicle type | The short text describes the object sufficiently | |
| 71 | 070 |
Please specify reason for alternative actual vehicle type | The short text describes the object sufficiently | |
| 72 | 071 |
Loading point &1 must be of type "Plant" | Space: object requires documentation | |
| 73 | 072 |
Only daily truck routes of type 'basic' can be created manually | The short text describes the object sufficiently | |
| 74 | 073 |
Truck route contract items can only be created for 'basic truck routes' | The short text describes the object sufficiently | |
| 75 | 074 |
Truck route must belong to truck route category 'BASIC'. Correct entry. | The short text describes the object sufficiently | |
| 76 | 075 |
Basic truck routes cannot be subordinated to another truck route | The short text describes the object sufficiently | |
| 77 | 076 |
Unloading point & is loading point for truck route & | ||
| 78 | 077 |
Please choose a list | The short text describes the object sufficiently | |
| 79 | 078 |
Select one line | The short text describes the object sufficiently | |
| 80 | 079 |
You do not have authorization to execute this function | The short text describes the object sufficiently | |
| 81 | 080 |
Enter truck route and shipping date | Space: object requires documentation | |
| 82 | 081 |
Daily truck route & already exists on & | The short text describes the object sufficiently | |
| 83 | 082 |
Daily truck route & on & has del. indicator - processing not possible | ||
| 84 | 083 |
Truck route & is not assigned to a truck route contract on & | The short text describes the object sufficiently | |
| 85 | 084 |
Period unit rule does not exist | The short text describes the object sufficiently | |
| 86 | 085 |
Daily truck route & on & does not exist | ||
| 87 | 086 |
Please enter unloading point type | The short text describes the object sufficiently | |
| 88 | 087 |
Please enter unloading point type for business partner | The short text describes the object sufficiently | |
| 89 | 088 |
Daily truck route & on & is flagged for deletion | The short text describes the object sufficiently | |
| 90 | 089 |
Drop-offs still exist for daily truck route & on & - deletion not allowed | The short text describes the object sufficiently | |
| 91 | 090 |
Split routes cannot be deleted | ||
| 92 | 091 |
The system could not delete all daily truck routes | ||
| 93 | 092 |
No data found that matches your selection criteria | The short text describes the object sufficiently | |
| 94 | 093 |
Business partner & does not exist | The short text describes the object sufficiently | |
| 95 | 094 |
Truck route & is not a basic route | ||
| 96 | 095 |
Split route & is already assigned to a basic truck route | ||
| 97 | 096 |
Basic truck route & and split route & depart from different plants | ||
| 98 | 097 |
Unloading point & is locked | The short text describes the object sufficiently | |
| 99 | 098 |
Program terminated - cannot be restarted | ||
| 100 | 099 |
Transaction for 'old' unloading rule was replaced. New JR32 and JR33 | ||
| 101 | 100 |
----- 100 - 119 reserved for mass recording of daily truck routes ------- | The short text describes the object sufficiently | |
| 102 | 101 |
To select an object, please position the cursor correctly | The short text describes the object sufficiently | |
| 103 | 102 |
Entry in this line is already selected | The short text describes the object sufficiently | |
| 104 | 103 |
Selected entries were updated | The short text describes the object sufficiently | |
| 105 | 104 |
Selected entry was updated | The short text describes the object sufficiently | |
| 106 | 105 |
If a different vehicle type is used you must also specify a reason | The short text describes the object sufficiently | |
| 107 | 106 |
Screen was updated | The short text describes the object sufficiently | |
| 108 | 107 |
Error while calculating duration: Start time must be before end time | ||
| 109 | 108 |
Function only possible one day before or after or on the planning date | ||
| 110 | 109 |
'Truck departs' can only be executed if return time is initial | ||
| 111 | 110 |
Actual availability time is in the future | ||
| 112 | 111 |
No daily truck routes found for these selection criteria | ||
| 113 | 112 |
Delivery round &2 is already assigned to truck route &1 | Space: object requires documentation | |
| 114 | 120 |
Production sequence type & does not exist | ||
| 115 | 121 |
Please enter an allowed value for start and target CODE-PAGE | The short text describes the object sufficiently | |
| 116 | 122 |
Truck route & does not exist | The short text describes the object sufficiently | |
| 117 | 123 |
Truck route & does not contain daily truck routes for year & | The short text describes the object sufficiently | |
| 118 | 124 |
Truck route & is a split route | The short text describes the object sufficiently | |
| 119 | 125 |
Please choose a valid field | The short text describes the object sufficiently | |
| 120 | 126 |
No bus.partner found for carrier route &, delivery round &, period & - & | The short text describes the object sufficiently | |
| 121 | 141 |
Error in time specifications | ||
| 122 | 180 |
No production procedure found for plant & | ||
| 123 | 199 |
Validity period cannot be shortened | ||
| 124 | 200 |
--- 201 - 299 reserved for error handling in read routines -------------- | The short text describes the object sufficiently | |
| 125 | 201 |
Truck route type & not found | The short text describes the object sufficiently | |
| 126 | 202 |
No text found for truck route type & in language & | The short text describes the object sufficiently | |
| 127 | 203 |
Truck route hierarchy type & not found | The short text describes the object sufficiently | |
| 128 | 204 |
No text found for truck route hierarchy type & in language & | The short text describes the object sufficiently | |
| 129 | 205 |
Split type & not found | The short text describes the object sufficiently | |
| 130 | 206 |
No text found for split type & in language & | The short text describes the object sufficiently | |
| 131 | 207 |
Truck route category type 1 & not found | The short text describes the object sufficiently | |
| 132 | 208 |
No text found for truck route category type 1 & in language & | The short text describes the object sufficiently | |
| 133 | 209 |
Truck route category type 2 & not found | The short text describes the object sufficiently | |
| 134 | 210 |
No text found for truck route category type 2 & in language & | The short text describes the object sufficiently | |
| 135 | 211 |
Truck route category type 3 & not found | The short text describes the object sufficiently | |
| 136 | 212 |
No text found for truck route category type 3 & in language & | The short text describes the object sufficiently | |
| 137 | 213 |
Truck route category type 4 & not found | The short text describes the object sufficiently | |
| 138 | 214 |
No text found for truck route category type 4 & in language & | The short text describes the object sufficiently | |
| 139 | 215 |
Truck route category type 5 & not found | The short text describes the object sufficiently | |
| 140 | 216 |
No text found for truck route category type 5 in language & | The short text describes the object sufficiently | |
| 141 | 217 |
Truck route weight class & not found | The short text describes the object sufficiently | |
| 142 | 218 |
No text found for truck route weight class & in language & | The short text describes the object sufficiently | |
| 143 | 219 |
Distance category & not found | The short text describes the object sufficiently | |
| 144 | 220 |
No text found for distance category & in language & | The short text describes the object sufficiently | |
| 145 | 221 |
Key category & not found | The short text describes the object sufficiently | |
| 146 | 222 |
No text found for key category & in language & | The short text describes the object sufficiently | |
| 147 | 223 |
No text found for vehicle type & | The short text describes the object sufficiently | |
| 148 | 224 |
No text found for vehicle type & in language & | The short text describes the object sufficiently | |
| 149 | 225 |
Loading/unloading point type & not found | The short text describes the object sufficiently | |
| 150 | 226 |
No text found for loading/unloading point type & in language & | The short text describes the object sufficiently | |
| 151 | 227 |
Printing works & not found | The short text describes the object sufficiently | |
| 152 | 228 |
Area requirement & not found | The short text describes the object sufficiently | |
| 153 | 229 |
No text found for area requirement & in language & | The short text describes the object sufficiently | |
| 154 | 230 |
No text found for truck route type & in language & or & | The short text describes the object sufficiently | |
| 155 | 231 |
No text found for truck route hierarchy type & in language & or & | The short text describes the object sufficiently | |
| 156 | 232 |
No text found for split type & in language & or & | The short text describes the object sufficiently | |
| 157 | 233 |
No text found for truck route category type 1 & in language & or & | The short text describes the object sufficiently | |
| 158 | 234 |
No text found for truck route category type 2 in language & or & | The short text describes the object sufficiently | |
| 159 | 235 |
No text found for truck route category type 3 & in language & or & | The short text describes the object sufficiently | |
| 160 | 236 |
No text found for truck route category type 4 & in language & or & | The short text describes the object sufficiently | |
| 161 | 237 |
No text found for truck route category type 5 & in language & or & | The short text describes the object sufficiently | |
| 162 | 238 |
No text found for truck route weight class & in language & or & | The short text describes the object sufficiently | |
| 163 | 239 |
No text found for distance category & in language & or & | The short text describes the object sufficiently | |
| 164 | 240 |
No text found for key bonus category & in language & or & | The short text describes the object sufficiently | |
| 165 | 241 |
No text found for vehicle type & in language & or & | The short text describes the object sufficiently | |
| 166 | 242 |
No text found for loading/unloading point type & in language & or & | The short text describes the object sufficiently | |
| 167 | 243 |
No text found for area requirement & in language & or & | The short text describes the object sufficiently | |
| 168 | 244 |
Vehicle type not recorded in daily truck route & | The short text describes the object sufficiently | |
| 169 | 290 |
--- 290 - 299 reserved for report RJVVSAN0 ------------------------------ | The short text describes the object sufficiently | |
| 170 | 291 |
First level reached | ||
| 171 | 292 |
Last level reached | ||
| 172 | 293 |
No detail analysis for this selection | ||
| 173 | 300 |
--- 300 - 329 reserved for daily truck route generation ----------------- | The short text describes the object sufficiently | |
| 174 | 301 |
No basic truck routes match your truck route selection criteria | ||
| 175 | 302 |
Generation run not possible (daily truck routes locked by user &) | ||
| 176 | 303 |
Generation run not possible (trigger locked by user &) | ||
| 177 | 304 |
Generation run not possible (user & generating daily truck routes) | ||
| 178 | 305 |
System is currently unable to lock | ||
| 179 | 306 |
Enter a valid value | The short text describes the object sufficiently | |
| 180 | 307 |
Run date is in the past | The short text describes the object sufficiently | |
| 181 | 308 |
Please enter a run date | The short text describes the object sufficiently | |
| 182 | 309 |
Please specify reference date or truck route type or both | The short text describes the object sufficiently | |
| 183 | 310 |
Generation trigger does not exist for object & on & | The short text describes the object sufficiently | |
| 184 | 311 |
Several generation triggers for object & on & | The short text describes the object sufficiently | |
| 185 | 312 |
Daily truck route for truck route & on & cannot be created manually | The short text describes the object sufficiently | |
| 186 | 313 |
Prohibited program status - please notify your system administrator | ||
| 187 | 314 |
Prohibited program status (internal error) | ||
| 188 | 315 |
Prohibited program status (internal error) | ||
| 189 | 316 |
Prohibited program status (internal error) | ||
| 190 | 317 |
Prohibited program status (internal error) | The short text describes the object sufficiently | |
| 191 | 318 |
Error occurred while reading factory calendar & | ||
| 192 | 319 |
Error occurred while reading public holiday calendar for factory cal.& | ||
| 193 | 320 |
No public holiday calendar defined for factory calendar & | ||
| 194 | 321 |
Prohibited program status - please notify your system administrator | ||
| 195 | 322 |
There is more than 1 daily truck route for run date & for truck route & | ||
| 196 | 323 |
A change number is currently being released. | ||
| 197 | 324 |
Prohibited program status - please notify your system administrator | The short text describes the object sufficiently | |
| 198 | 330 |
--- 330 - 349 reserved for maintenance of gen.trigger for truck routes -- | The short text describes the object sufficiently | |
| 199 | 331 |
Truck route & is not a basic truck route - check your entry | ||
| 200 | 399 |
Prohibited program status - please notify your system administrator | ||
| 201 | 400 |
-- 400 - 499 reserved for unloading viability sets ---------------------- | The short text describes the object sufficiently | |
| 202 | 401 |
Unloading viability set & & & & does not exist | The short text describes the object sufficiently | |
| 203 | 402 |
Unloading viability sets may be deleted if changed | ||
| 204 | 403 |
No unloading viability sets found that correspond to selection criteria | The short text describes the object sufficiently | |
| 205 | 404 |
Unloading viability sets were changed | The short text describes the object sufficiently | |
| 206 | 405 |
You are in copy mode | ||
| 207 | 406 |
Unloading viability set locked by & (sales org. &, dist.channel &, DT &) | ||
| 208 | 407 |
Lock not possible - system problem with lock server | ||
| 209 | 408 |
Unloading viability set can only be deleted with change number & | The short text describes the object sufficiently | |
| 210 | 409 |
Active records can only be deleted if they have same period as unl.VSet | The short text describes the object sufficiently | |
| 211 | 410 |
You are deleting an active unloading viability set | The short text describes the object sufficiently | |
| 212 | 411 |
No delivery viability set of this kind exists | ||
| 213 | 412 |
Period for change number not completely within period for deliv.viability | ||
| 214 | 413 |
Unloading viability set already exists in maintenance table | ||
| 215 | 414 |
Unloading viability already exists in maintenance table | ||
| 216 | 415 |
Unloading viability set already exists (on database) | ||
| 217 | 416 |
Planned changes exist for the unloading viability set: deletion not poss. | ||
| 218 | 417 |
You are deleting an active unloading viability set | The short text describes the object sufficiently | |
| 219 | 418 |
Unloading viability set can only be deleted with change number & | ||
| 220 | 419 |
Active records can only be deleted if they have same period as unl.VSet | ||
| 221 | 420 |
The selected record is not a terminated record | ||
| 222 | 421 |
Please specify loading/unloading point | ||
| 223 | 422 |
Period for change number greater than validity period of load./unl.point | ||
| 224 | 423 |
Unloading viability set must be active before it can be terminated | ||
| 225 | 424 |
Record deleted - termination not possible | ||
| 226 | 425 |
Record already terminated - termination cannot be repeated | ||
| 227 | 426 |
Unloading viability set terminated on & | ||
| 228 | 427 |
'Cancel unloading viability set deletion' not possible for this record | ||
| 229 | 428 |
Cancelling unloading via.set deletion only possible with change number & | ||
| 230 | 429 |
Cancelling deletion not possible - related delivery viability completed | ||
| 231 | 430 |
Please make entries in all required fields | ||
| 232 | 431 |
Shipping already performed in period for change number | Space: object requires documentation | |
| 233 | 432 |
Function 'Substitute unloading point' was cancelled | The short text describes the object sufficiently | |
| 234 | 433 |
Unloading point & does not exist - please correct your entry | The short text describes the object sufficiently | |
| 235 | 434 |
Unloading point & was replaced & times by unloading point & | The short text describes the object sufficiently | |
| 236 | 435 |
Unloading point & was only replaced & times with unloading point & | ||
| 237 | 436 |
Unloading point could not be substituted | ||
| 238 | 437 |
All special rules will also be terminated | The short text describes the object sufficiently | |
| 239 | 438 |
& unloading viability sets created | The short text describes the object sufficiently | |
| 240 | 439 |
Unable to create unloading viability set | ||
| 241 | 440 |
No new unloading viability sets were created | ||
| 242 | 441 |
Please assign all unloading points a sequence number first | ||
| 243 | 442 |
Please assign all truck routes a sequence number first | ||
| 244 | 443 |
You do not have authorization for unloading points | Space: object requires documentation | |
| 245 | 444 |
Loading point & is not allowed. Please specify the unloading point | ||
| 246 | 445 |
Carrier route & does not have an unloading point for odd bundles | ||
| 247 | 450 |
--- reserved for unloading rules - 499 ---------------------------------- | The short text describes the object sufficiently | |
| 248 | 451 |
Access either via carrier route or unloading point | ||
| 249 | 452 |
Unloading rule not required for selected publication/edition | ||
| 250 | 453 |
No related unloading rules required for line selection | ||
| 251 | 454 |
Line selection invalid - please choose a publication edition | ||
| 252 | 455 |
Unloading rules were changed | ||
| 253 | 456 |
Not all unl.points in unloading viability set have truck route assignment | ||
| 254 | 457 |
You are deleting an active unloading rule: position cursor, press enter | The short text describes the object sufficiently | |
| 255 | 458 |
Delete unloading rule only with change number & | ||
| 256 | 459 |
You can only delete active recs that have same period as unloading rule | The short text describes the object sufficiently | |
| 257 | 460 |
Line selection invalid - please reposition the cursor | ||
| 258 | 461 |
Maintain requested quantity of odd bundles for unloading point | ||
| 259 | 462 |
There are unloading points with requested quantity 0 from & to & | ||
| 260 | 463 |
Indicator missing for odd bundle from & to & | ||
| 261 | 464 |
'Unloading point' indicator should only be selected once for odd bundle | ||
| 262 | 465 |
Unloading rule must be active for completion | ||
| 263 | 466 |
All related unloading rules completed on & | ||
| 264 | 467 |
Unable to delete termination of unloading rule- record was not terminated | The short text describes the object sufficiently | |
| 265 | 468 |
Termination of unloading rule can only be deleted using change number & | The short text describes the object sufficiently | |
| 266 | 469 |
Selected record is new (not yet saved) - no 'created by' data | The short text describes the object sufficiently | |
| 267 | 470 |
Unloading rule with number & does not exist - internal error | ||
| 268 | 471 |
Maintenance of unloading rules not necessary for the selected object | ||
| 269 | 472 |
Function not possible - first reset or delete 'Odd bundle' indicator | ||
| 270 | 473 |
It is not possible to finish with the current change number & | ||
| 271 | 474 |
Unloading point & is not a business partner unloading point | ||
| 272 | 475 |
Unloading rules locked by user & | ||
| 273 | 476 |
Rules for business partner unloading point never have unloading via.sets | ||
| 274 | 477 |
Check of rules for selected publication/edition was successful | ||
| 275 | 478 |
Record only displayed for information purposes - deletion not possible | ||
| 276 | 479 |
Release procedure in process - unloading rules cannot be processed | ||
| 277 | 480 |
New records with indicator 'Rule required' cannot be deleted | The short text describes the object sufficiently | |
| 278 | 481 |
Function only poss. for ad pre-print del.type and ad pre-print publ.type | ||
| 279 | 482 |
Unable to create a new special rule | ||
| 280 | 483 |
Deletion not possible - special rules exist. DT & public./edition & & | ||
| 281 | 484 |
Deletion cannot be cancelled: please perform first for general rules | ||
| 282 | 485 |
No line selected in upper section - please select line(s) first | ||
| 283 | 486 |
No line selected in lower section - please select line(s) first | ||
| 284 | 487 |
Please enter unloading point or carrier route | ||
| 285 | 488 |
Invalid selection - please choose an unloading point that is not selected | ||
| 286 | 489 |
Invalid line selection | ||
| 287 | 490 |
Unloading rules were generated for carrier route & | Space: object requires documentation | |
| 288 | 491 |
No rule could be created for carrier route & for unloading point & | ||
| 289 | 492 |
& | ||
| 290 | 493 |
No rule could be created for unloading point & for truck route & | ||
| 291 | 494 |
Function modules missing for unloading rules in bundling | Space: object requires documentation | |
| 292 | 495 |
Please enter either the business partner or the plant, but not both | Space: object requires documentation | |
| 293 | 496 |
Too large number of objects - please restrict selection | Space: object requires documentation | |
| 294 | 500 |
-----500 to 700 reserved for packing etc. | The short text describes the object sufficiently | |
| 295 | 501 |
No bundling rule defined for edition &3 &1 with delivery type &2 | Space: object requires documentation | |
| 296 | 502 |
The system did not update all drop-offs | The short text describes the object sufficiently | |
| 297 | 503 |
Error occurred while updating drop-offs | The short text describes the object sufficiently | |
| 298 | 504 |
The system did not update all drop-off - delivery assignments | The short text describes the object sufficiently | |
| 299 | 505 |
Error occurred during update of drop-off-delivery assignment | The short text describes the object sufficiently | |
| 300 | 506 |
Production group & contains a number of elements | ||
| 301 | 507 |
No packing guideline for address postal code &, country & | ||
| 302 | 508 |
Update JVTZUOBUND, JVTBUND contains errors | The short text describes the object sufficiently | |
| 303 | 509 |
No unloading viability set created for carr.route/geo.unit &, publ. & | ||
| 304 | 510 |
No daily truck route found for unloading point & | The short text describes the object sufficiently | |
| 305 | 511 |
INSERT to JVTGEBINDE & contains errors | The short text describes the object sufficiently | |
| 306 | 512 |
No packing guideline for postal code &, country &, packing level & | ||
| 307 | 513 |
Edition & is not assigned to a truck route | The short text describes the object sufficiently | |
| 308 | 514 |
No function module exists for delivery type & | ||
| 309 | 515 |
Unloading rule missing for unloading pnt &, route & (publict.&/edition &) | Space: object requires documentation | |
| 310 | 516 |
Odd bundle not assigned to unloading point & route & (public. & / edit.&) | Space: object requires documentation | |
| 311 | 517 |
System error: Update JVTNUMBUND was not performed | The short text describes the object sufficiently | |
| 312 | 518 |
System error while saving container number for bundle | The short text describes the object sufficiently | |
| 313 | 519 |
No minimum quantities defined for delivery type & and shipp.network & | ||
| 314 | 520 |
No deliveries exist for shipping date & | The short text describes the object sufficiently | |
| 315 | 521 |
Insert JVTZUOGBND & & contains errors | The short text describes the object sufficiently | |
| 316 | 522 |
Update JVTNUMGBND contained errors for plant &, date & | The short text describes the object sufficiently | |
| 317 | 523 |
The system was not able to update all bundle-order assignments | The short text describes the object sufficiently | |
| 318 | 524 |
Several variants for edition & and delivery type & | ||
| 319 | 525 |
No variant created for edition & and delivery type & | ||
| 320 | 526 |
Several dispatch type sequences for shipp.schedule variant & and PCd & | ||
| 321 | 527 |
No dispatch type sequence for shipping schedule variant & and p.code & | The short text describes the object sufficiently | |
| 322 | 528 |
Containers already packed for geo.unit &, edition &, delivery type & | ||
| 323 | 529 |
The system was not able to update all containers | The short text describes the object sufficiently | |
| 324 | 530 |
Bundling not possible - daily truck routes are being processed | ||
| 325 | 531 |
Bundling not possible - shipping schedule is currently being edited | ||
| 326 | 532 |
Drop-offs are locked by user & | ||
| 327 | 533 |
No authorization for bundling in plant & | ||
| 328 | 534 |
Please either specify shipping date or have the system determine it | Space: object requires documentation | |
| 329 | 535 |
Minimum number of units in postal pack missing for packing rule & | ||
| 330 | 536 |
Please specify date | Space: object requires documentation | |
| 331 | 537 |
Packing can only be performed in the background | The short text describes the object sufficiently | |
| 332 | 538 |
Minimum number of units for bundle (rule type &) missing | ||
| 333 | 539 |
Shipping run cancelled - different shipping dates | ||
| 334 | 540 |
No planned weights maintained for issues & or their inserts | ||
| 335 | 541 |
No availability times maintained for issue & at plant & | ||
| 336 | 542 |
Internal error: Rule type missing | ||
| 337 | 543 |
No daily truck route found in unloading point & for variant & | ||
| 338 | 544 |
Shipping run cancelled - no valid shipping date | ||
| 339 | 545 |
Please specify shipping group | ||
| 340 | 546 |
Internal error: Drop-off with several rule types | ||
| 341 | 547 |
Internal error: Drop-offs with several networks | ||
| 342 | 548 |
Please specify either a copy number or a publication date | Space: object requires documentation | |
| 343 | 549 |
Copy & not found for this publication/edition | Space: object requires documentation | |
| 344 | 550 |
No postal packs or drop-offs found for selection criteria specified | ||
| 345 | 551 |
Deletion not possible - postal packs are still packed in containers | ||
| 346 | 552 |
Postal pack & is already packed in container & | ||
| 347 | 553 |
Deletion cancelled - no containers found | ||
| 348 | 554 |
Deletion cancelled - common odd bundle | ||
| 349 | 555 |
No container packing specified for delivery type & | ||
| 350 | 556 |
Unable to determine a unique next shipping date | Space: object requires documentation | |
| 351 | 557 |
Drop-off & not packed since network missing | ||
| 352 | 558 |
Deletion not possible - production data still exists | ||
| 353 | 559 |
Unable to determine an unambiguous next date | Space: object requires documentation | |
| 354 | 560 |
Assignment does not exist for delivery & and network & | ||
| 355 | 561 |
Shipping group only allowed with automatic date determination | The short text describes the object sufficiently | |
| 356 | 563 |
Rule missing for plant &, delivery type &, network &, container type & | ||
| 357 | 564 |
Internal error - system could not pack all packs on level & | ||
| 358 | 565 |
The system was unable to update all bundles | The short text describes the object sufficiently | |
| 359 | 566 |
Error during update of bundles | The short text describes the object sufficiently | |
| 360 | 567 |
Invalid publication | The short text describes the object sufficiently | |
| 361 | 570 |
Drop-offs exist that do not belong to the schema | Space: object requires documentation | |
| 362 | 580 |
Order deadline not reached for publication & deliv.type & | ||
| 363 | 590 |
Please enter rule type (bundling, container packing) | ||
| 364 | 591 |
Please specify plant, publication and date | ||
| 365 | 592 |
Please note access sequence | ||
| 366 | 600 |
Flow procedure not found for plant & and shipping date & | ||
| 367 | 601 |
Flow procedure for production missing for procedure & | ||
| 368 | 602 |
Function module for sort for repetition group & was not found | ||
| 369 | 650 |
--- 650 - 699 reserved for unloading rule ------------------------------- | ||
| 370 | 651 |
Error during '&' of & & & | ||
| 371 | 652 |
&: Invalid basic unit of measure (only ST, VP, %) | ||
| 372 | 653 |
Unloading rule not required for & | Space: object requires documentation | |
| 373 | 654 |
No entry in table JDTDRER for & | ||
| 374 | 655 |
No entry found in table JDTPVA for & and & | ||
| 375 | 656 |
No records selected according to the criteria specified | ||
| 376 | 657 |
& &: Total of quantities < 100% | ||
| 377 | 658 |
& &: Total of quantities > 100% | ||
| 378 | 659 |
Unloading rule saved | ||
| 379 | 660 |
& &: You did not specify a quantity for unloading point & | ||
| 380 | 661 |
&: No quantity specified for basic unit of measurement VP. | ||
| 381 | 662 |
&: You did not specify a quantity for truck route & | ||
| 382 | 663 |
No line selected | ||
| 383 | 664 |
Select only one line | ||
| 384 | 665 |
Invalid issue variant type | ||
| 385 | 666 |
Exception to issue variant type & already exists on & | ||
| 386 | 667 |
Special rule already exists for ad pre-print & | ||
| 387 | 668 |
Check performed - there are no errors or warnings | ||
| 388 | 669 |
No unloading rule found for the selection criteria specified | ||
| 389 | 670 |
Invalid line selection | ||
| 390 | 671 |
Invalid cursor position | ||
| 391 | 672 |
Entry is not an exception | ||
| 392 | 673 |
Entry is not a special rule | ||
| 393 | 674 |
Worklist has been processed | ||
| 394 | 675 |
No unloading point sequence found for the selection criteria specified | ||
| 395 | 676 |
Selection is restricted to one truck route | ||
| 396 | 677 |
No exceptions possible for ad pre-prints | Space: object requires documentation | |
| 397 | 701 |
---------701-730 reserved for problem route processing------------------- | The short text describes the object sufficiently | |
| 398 | 702 |
Truck route & already in list | The short text describes the object sufficiently | |
| 399 | 703 |
You can now only select & | The short text describes the object sufficiently | |
| 400 | 704 |
No unloading point marked to be moved | The short text describes the object sufficiently | |
| 401 | 705 |
Unloading point can only be moved to a truck route or unloading point | The short text describes the object sufficiently | |
| 402 | 706 |
Block already exists | The short text describes the object sufficiently | |
| 403 | 707 |
Drop-offs can only be moved to an unloading point | The short text describes the object sufficiently | |
| 404 | 708 |
Place cursor on basic truck route to perform split | The short text describes the object sufficiently | |
| 405 | 709 |
Splitting not possible when lines are still selected | The short text describes the object sufficiently | |
| 406 | 710 |
Truck route was already split | The short text describes the object sufficiently | |
| 407 | 711 |
Truck route cannot be split | The short text describes the object sufficiently | |
| 408 | 712 |
Only carrier drop-offs can be selected | The short text describes the object sufficiently | |
| 409 | 713 |
Number of packs to be moved is too large | The short text describes the object sufficiently | |
| 410 | 714 |
You can only select drop-offs for postal delivery | The short text describes the object sufficiently | |
| 411 | 715 |
You cannot select drop-offs for postal delivery | The short text describes the object sufficiently | |
| 412 | 716 |
You can now only select drop-offs for postal delivery | The short text describes the object sufficiently | |
| 413 | 717 |
You can now only select complete drop-offs for postal delivery | The short text describes the object sufficiently | |
| 414 | 718 |
You can only select bundles/containers | The short text describes the object sufficiently | |
| 415 | 719 |
Please select end of block first | The short text describes the object sufficiently | |
| 416 | 720 |
You can only move between drop-offs in one truck route | ||
| 417 | 721 |
Bundles and containers cannot be selected | The short text describes the object sufficiently | |
| 418 | 722 |
Blocks of drop-offs cannot be selected without truck route | The short text describes the object sufficiently | |
| 419 | 723 |
No problem routes | The short text describes the object sufficiently | |
| 420 | 724 |
Please position the cursor on a truck route to delete it | The short text describes the object sufficiently | |
| 421 | 725 |
All selected drop-offs for postal delivery use the same network | The short text describes the object sufficiently | |
| 422 | 726 |
Other problem routes exist (see problem indicator) | The short text describes the object sufficiently | |
| 423 | 727 |
Daily truck route does not exist | The short text describes the object sufficiently | |
| 424 | 728 |
Problem route processing not possible - release is running | The short text describes the object sufficiently | |
| 425 | 729 |
Problem route processing not possible - daily routes are in process | The short text describes the object sufficiently | |
| 426 | 730 |
Problem route processing not possible - shipping schedule being processed | The short text describes the object sufficiently | |
| 427 | 735 |
From-date is later than to-date - please check your entry | The short text describes the object sufficiently | |
| 428 | 736 |
Start of generation should be after lock date | The short text describes the object sufficiently | |
| 429 | 737 |
Processing terminated | The short text describes the object sufficiently | |
| 430 | 750 |
--- 750 - 770 reserved for shipping analyses ---------------------------- | The short text describes the object sufficiently | |
| 431 | 751 |
Please position the cursor on a valid line | The short text describes the object sufficiently | |
| 432 | 752 |
Program has reached prohibited status - please notify sys.administrator | The short text describes the object sufficiently | |
| 433 | 753 |
Drop-off & has no bundles (bundles only in postal shipping) | The short text describes the object sufficiently | |
| 434 | 800 |
Unloading point is used in carrier route & - deletion not possible | The short text describes the object sufficiently | |
| 435 | 801 |
Unloading point is used in unloading via.sets - deletion not possible | The short text describes the object sufficiently | |
| 436 | 802 |
Unloading point is used in shipping schedule - deletion not possible | The short text describes the object sufficiently | |
| 437 | 803 |
Unloading point is used in unloading rule. Deletion not possible | The short text describes the object sufficiently | |
| 438 | 804 |
Unloading point is used in unloading point seq. & - deletion not poss. | The short text describes the object sufficiently | |
| 439 | 805 |
Unloading point is used in order & - deletion not possible | The short text describes the object sufficiently |
History
| Last changed on/by | |
20130531 | SAP |
| SAP Release Created in |
