/SCWM/SHP_RCV - Message for Loading/Unloading + Shipping/Receiving
The following messages are stored in message class /SCWM/SHP_RCV: Message for Loading/Unloading + Shipping/Receiving.
It is part of development package /SCWM/SHP_RCV_CORE in software component SCM-EWM-SR. This development package consists of objects that can be grouped under "backend functions of shipping & reciving".
It is part of development package /SCWM/SHP_RCV_CORE in software component SCM-EWM-SR. This development package consists of objects that can be grouped under "backend functions of shipping & reciving".
Message Nr ▲ | Message Text |
|---|---|
| 000 | &1 &2 &3 &4 |
| 001 | Access to master data layer (MDL) was unsuccessful |
| 002 | &1 is not a valid business partner |
| 003 | You are not allowed to change the fixed vehicle assignments for TU &1/&2 |
| 004 | Input data is incorrect |
| 005 | MTr of vehicle &1 is not compatible with pack. material of TU &2 |
| 006 | No. of obligatory packaging materials &1 in means of transp. &2 is zero |
| 007 | Delivery &1: warehouse &2, MTr &3, and transp. group &4 are incompatible |
| 008 | Product &1 does not exist |
| 009 | Enter at least one selection criterion. |
| 010 | HU data for transportation unit &1/&2 could not be changed |
| 011 | New TU activity &1 &2 included in processing |
| 012 | Customizing: packaging matl &1 is not compatible with means of transp. &2 |
| 013 | &1 new, &2 changed, and &3 deleted TU activities, &4 TUs deleted |
| 014 | Transportation unit &1/&2 is blocked by user &3 |
| 015 | No changes possible; transportation unit &1/&2 is not locked yet |
| 016 | &1 TU activities were read from database |
| 017 | &1 transportation units were locked |
| 018 | Transportation unit &1/&2 already exists |
| 019 | Selection of assignments between TU and doors was unsuccessful |
| 020 | New activity for vehicle &1 included in processing |
| 021 | &1 vehicle act. created, &2 changed, &3 deleted; &4 vehicles deleted |
| 022 | Vehicle &1 is blocked by user &2 |
| 023 | No changes possible; vehicle &1 is not yet locked |
| 024 | &1 vehicle activities were read from database |
| 025 | &1 vehicles were locked |
| 026 | Vehicle &1/&2 already exists |
| 027 | Selection of assignments between TUs and vehicles was unsuccessful |
| 028 | TU assignment &1/&2 lies below the lower time limit &3/&4 for assignments |
| 029 | TU assignment &1/&2 lies above the upper time limit &3/&4 for assignments |
| 030 | Vehicle/TU assignmnt &1 lies below the lower time limit &2 for assignmnts |
| 031 | Vehicle/TU assignmnt &1 lies above the upper time limit &2 for assignmnts |
| 032 | Vehicle &1 could not be unlocked |
| 033 | Transportation unit &1/&2 could not be unlocked |
| 034 | Assignment table (TU/door) contains more entries than TU table |
| 035 | Assignment table (TU/vehicle) contains more entries than TU table |
| 036 | Customizing for construct. rules for vehicles missing for &1 doc. type &2 |
| 037 | Action not possible; TU &1 is not docked at door |
| 038 | Status: Operation &1 is not possible for document &2 / &3 |
| 039 | Upper time limit less than lower time limit is not permitted |
| 040 | Planning-related TU/door assignment from &1/&2 to &3/&4 has overlaps |
| 041 | Door &1 / &2 could not be unlocked |
| 042 | No changes possible; door &1 / &2 is locked by &3 |
| 043 | No changes possible; delivery &1 / &2 is not yet locked |
| 044 | Status of delivery &1 / &2 could not be set |
| 045 | Action is only allowed for outbound deliveries; convert &1 |
| 046 | Goods issue posting was not successful; see the log for details |
| 047 | Goods receipt posting was not successful; see the log for details |
| 048 | Action is only allowed for inbound deliveries (&1 is not an inb. deliv.) |
| 049 | Door &1 does not exist in warehouse number &2 |
| 050 | Goods movement is not possible for HU &1; select delivery &2 |
| 051 | Door for storage bin &1 does not exist in warehouse number &2 |
| 052 | Predefined staging area data does not match the determination |
| 053 | Predefined staging area data does not match the process type |
| 054 | Goods movement is not possible for HUs; select HU &1 as well |
| 055 | Goods movement is not possible for deliveries; select &1 too |
| 056 | Error: storage bin for door &1/&2 is initial in the settings |
| 057 | No deliveries are selected therefore no message was sent to TMS |
| 058 | Entry &1 is not a valid supply chain unit |
| 059 | Door &1/&2 was not found in the database |
| 060 | Staging area &1/&2/&3 was not found in the database |
| 061 | Loading direction of door &1 does not match staging area (in: &2/out: &3) |
| 062 | No staging area data was found |
| 063 | WT with dest. storage bin TU is not possible; TU not yet arrived at door |
| 064 | Billing document has not been requested yet; action is not possible |
| 065 | Loading rule is only advisable for goods issue activities |
| 066 | For optional packaging materials, do not define either sequence or number |
| 067 | Only one pack. matl is permitted as a container for each means of transp. |
| 068 | Vehicle &1 does not exist |
| 069 | Storage type &1 does not have the role "staging area group" |
| 070 | User &1 is blocking assignments between delivery/HU and TU |
| 071 | Staging bay &2 was not found in warehouse number &1 |
| 072 | Staging area group &2 was not found in warehouse number &1 |
| 073 | No TU could be determined; either door or vehicle data is missing |
| 074 | No staging area was found for storage section &1 |
| 075 | Loading rule for HU &1 was not fulfilled at staging area &2 |
| 076 | Means of transport is not maintained for TUs (Customizing) |
| 077 | Document &1/&2 is not relevant (reason C:&3/G:&4) and was removed |
| 078 | Message with &1 entries was sent to &2 |
| 079 | &1 door activities were read from the database |
| 080 | Door &1 &2 is locked by user &3 |
| 081 | &1 doors were locked |
| 082 | TU &1/&2/&3 is not actively assigned to a door; no whse task creation |
| 083 | Creation of warehouse tasks was triggered |
| 084 | Goods movement not possible for HUs; del. &1, item &2 not compl. packed |
| 085 | Error occurred when reading delivery-HU assignments |
| 086 | Error occurred when reading Customizing (table &1) - key &2, &3 |
| 087 | Only logical assignments to TU &1 can be deleted (&2 &3 &4) |
| 088 | Storage bin for checkpoint &1 does not exist in warehouse number &2 |
| 089 | &1 new, &2 changed, and &3 deleted door activities were saved |
| 090 | Check against pattern &1 failed |
| 091 | &2 is not permitted with check against pattern &3 on position &1 |
| 092 | Delivery &1 could not be read |
| 093 | Delivery item &1-&2 could not be read |
| 094 | HU application &1 could not be set |
| 095 | HUs requested do not have the same warehouse number |
| 096 | Planned activity direction &1 does not agree with assignment |
| 097 | Lower-level assignment of TU &1/&2 to HU &3 was also deleted |
| 098 | Lower-level assignment of TU &1/&2 to del. item &3-&4 was also deleted |
| 099 | New door activity &1 &2 was included in processing |
| 100 | Error when creating/deleting a LIME location of the transportation unit |
| 101 | Update of HU data was not successful |
| 102 | Number range '&1' '&2' could not be read |
| 103 | Incorrect call type for the link between packaging matl and means of trsp |
| 104 | You cannot create the HU for a transportation unit |
| 105 | Saving new transportation units to the database failed |
| 106 | Changing transportation units on the database failed (&1) |
| 107 | Deleting transportation units from the database failed |
| 108 | Selection of transportation unit header data (from database) is faulty |
| 109 | Selection of HU data for transportation units is incorrect (&1/&2) |
| 110 | READ with key (&1 / &2) failed in internal table &3 |
| 111 | Input parameters for creating transportation unit are missing or faulty |
| 112 | Selection of vehicles from database is incorrect |
| 113 | Changing vehicles on the database failed (&1) |
| 114 | Input parameters for creating vehicle are faulty or missing |
| 115 | Selection of door data from the database was unsuccessful |
| 116 | Generation of BAdI instance &1 failed (&2) |
| 117 | Error reading means of transport &1 |
| 118 | PPF call failed |
| 119 | Incorrect entry for authorization check |
| 120 | BAdI for means-of-transport authoriz. check for &1 &2 &3 contains errors |
| 121 | Delivery query was unsuccessful |
| 122 | Writing delivery data was unsuccessful |
| 123 | No authorization to change the means of transport &1 (warehouse &2) |
| 124 | Sending & message failed for vehicle &1 |
| 125 | No authorization for activity &3 for means of transport &1 (warehouse &2) |
| 126 | No authorization to change door assignments &1 (warehouse &2) |
| 127 | No authorization to read door &1 (warehouse &2) |
| 128 | Inbound delivery/outbound delivery order &1 could not be locked |
| 129 | Outbound delivery &1 could not be locked |
| 130 | An external number is not supported for obligatory TUs for vehicles |
| 131 | System error: destination location &1 was not found in route &2 |
| 132 | System error: routing guide did not return any data for route &1 |
| 133 | Staging area determination collides with process type &1 (&2, &3, &4) |
| 134 | Documents for &1 &2: printer determination failed; data inconsistency |
| 135 | PPF action could not be executed; no assignment period |
| 136 | PPF action &1 failed; data is missing (&2) |
| 137 | PPF action: no docs were found for conversion from 'planned' to 'final' |
| 138 | Changing doors on database has failed (&1) |
| 139 | PPF action: No execution logic provided (&1) |
| 140 | Printer determination using Customizing failed |
| 141 | Delivery &1 cannot be added |
| 142 | An assignment already exists between TU &1 and delivery &2 |
| 143 | HU &1 cannot be added |
| 144 | An assignment already exists between TU &1 and HU &2 |
| 145 | HU &1 does not have a delivery reference |
| 146 | HU &1 could not be read |
| 147 | Selected packaging material & is not allowed for transportation units |
| 148 | Delivery item &1-&2 cannot be assigned |
| 149 | An assignment already exists between TU &1/&2 and delivery item &3 &4 |
| 150 | System error: Method &1 in class &2 was called with incorrect parameters |
| 151 | Action &1 could not be processed |
| 152 | Assignment already exists between TU &1/&2 and HU &3 (delivery ref. &4) |
| 153 | Action is not intended for operating mode (&1/&2) |
| 154 | Stock for TU &1 could not be read; See log for details |
| 155 | No authorization to change activity for door &1 (warehouse &2) |
| 156 | Door &1 in warehouse &2 is not assigned to a supply chain unit |
| 157 | Incorrect input parameters |
| 158 | Planning-related TU/vehicle assignment from &1/&2 to &3/&4 has overlaps |
| 159 | TU/vehicle assignment from &1/&2 to &3/&4 has overlaps |
| 160 | TU/door assignment from &1/&2 to &3/&4 has overlaps |
| 161 | Date &1 exists already in delivery &2 |
| 162 | Some of the warehouse tasks for TU could not be read |
| 163 | Assign vehicle &1 from delivery &2 to TU &3/&4 |
| 164 | Check warehouse task &1 for DTU_NUM or STU_NUM. Any inconsistencies? |
| 165 | Vehicle &1 from delivery &2: inconsistency with TU &3 with vehicle &4 |
| 166 | Assign door &1 from delivery &2-&3 to TU &4 |
| 167 | Door &1 from delivery &2-&3: inconsistency with door &4 |
| 168 | "Multiple Means of Transport" ind. in del. &1: inconsistent with TU &2/&3 |
| 169 | Delivery &1 is updated with vehicle '&2' |
| 170 | Delivery &1 was updated with door &2 |
| 171 | Multiple doors are assigned to TU &1/&2 |
| 172 | SCAC code &1 with partner &2 does not match carrier &3 |
| 173 | Delivery &1 does not have a transportation segment |
| 174 | Activity &1 cannot be changed from state &2 to state &3 |
| 175 | Printing not possible; billing document creation not finished yet |
| 176 | Selection for HU &1 returns more than one TU |
| 177 | Delivery assignment to TU &1/&2 is inconsistent |
| 178 | System error: module &1 called with incorrect parameters |
| 179 | Define goods mov. ctrl for whse no. &1, whse proc. type &2, TM &3, car.&4 |
| 180 | Current TU direction (&1) does not match requested action (&2) |
| 181 | Incorrect input parameters |
| 182 | TU activity &1/&2/&3 not found in database |
| 183 | Vehicle activity &1/&2/&3 not found in database |
| 184 | Door activity &1/&2/&3 not found in database |
| 185 | System error: do not use (redefined) method &1 in class &2 |
| 186 | Action &1 not possible; open warehouse task exists for yard movement |
| 187 | Action &1 is not possible; TU was already moved in yard |
| 188 | Error: method &1 is to be executed unchecked; see log for details |
| 189 | Action &1 was prepared successfully; save document |
| 190 | Action &1 not possible; whse &2, storage type &3 not maintained as yard |
| 191 | Checkpoint &1 in warehouse &2 not found |
| 192 | Assignments: status &1 is &2 for TU and &3 for vehicle |
| 193 | SC unit &1 for door &2 (warehouse number &3) does not exist |
| 194 | Action &1 is not permitted for object and state &2 &3 &4 |
| 195 | "Multiple Means of Transport" indicator was set in delivery &1 |
| 196 | Action &1 not completed successfully; for details, see log &2 &3 |
| 197 | Action &1 executed successfully; &2 &3 |
| 198 | >>>>>>>>>> Start of action &1 at &2 &3 >>>>>>>>>> |
| 199 | Deliveries with different warehouse numbers cannot be processed |
| 200 | &1 errors in data for arrival and departure times (see log) |
| 201 | TU &1/&2 does not exist |
| 202 | Arrival time specified lies in the past |
| 203 | Vehicle with fixed transportation unit: delivery assignments |
| 204 | Only freight document number was copied from transportation management |
| 205 | More than one vehicle activity found for bill of lading |
| 206 | No information specified for vehicle number or license plate |
| 207 | Warning: &1 vehicles exist with external vehicle number &2/&3 |
| 208 | Warning: &1 vehicles exist with license plate number &2 |
| 209 | When creating a vehicle you must specify a means of transport |
| 210 | Arrival and departure times lie in different vehicle activities |
| 211 | No specification of unique external TU number found (TU no. &1) |
| 212 | Warning: &1 transportation units exist with external TU number &2/&3 |
| 213 | Warning: &1 transportation units exist with license plate number &2 |
| 214 | Capacity check failed for TU &1/&2 |
| 215 | Not possible to save changed shipping and receiving data using BOM |
| 216 | Duplicate external numbers for transportation units are not permitted |
| 217 | Start of arrival period is later than its end |
| 218 | Start of departure period is later than its end |
| 219 | Planned arrival time lies after planned departure time |
| 220 | Missing data; define a number range per door |
| 221 | Specify a means of transport (MTR_EXT) when creating a TU |
| 222 | Transportation unit on vehicle has already arrived in the yard |
| 223 | Vehicle <&1>: start of processing |
| 224 | Vehicle <&1>: processing terminated due to error |
| 225 | Transportation unit <&1/&2>: start of processing (data record no. &3) |
| 226 | TU <&1>: processing terminated due to error (data record no. &2) |
| 227 | Specified means of transport &1 (import field MTR_EXT) is unknown |
| 228 | No packaging material found for means of transport &1 (MTR field) |
| 229 | No HU found for TU &1/&2; no warehouse task was created |
| 230 | No HU intended for storage control; no warehouse task was created |
| 231 | &1 vehicle activities exist with freight document number &2 |
| 232 | TU activity &1 is missing in imported freight document data; delete |
| 233 | Transportation unit <&1/&2> (data record no. &3) not assigned to vehicle |
| 234 | Transportation unit <&1/&2> is not assigned to vehicle |
| 235 | Transportation unit <&1/&2> for freight document is listed twice |
| 236 | &1 HU/delivery assignments to TU activities were read from database |
| 237 | Vehicle <&1> not found; create new vehicle and TU data |
| 238 | Vehicle <&1> found; create new vehicle activities and TU activities only |
| 239 | Activities found; update vehicle and TU data |
| 240 | External TU number &1 no longer found in transfer table |
| 241 | Seal ID &1 cannot be converted to a seal number |
| 242 | No vehicle activities or TU activities found to be canceled |
| 243 | &1 vehicle number(s) locked; cancelation is not possible |
| 244 | Vehicle number(s): &1 |
| 245 | &1 transportation unit(s) locked; cancelation is not possible |
| 246 | TU number(s): &1 |
| 247 | &1 vehicle activity (activities) locked; cancelation is not possible |
| 248 | Vehicle activity (activities): &1 |
| 249 | &1 TU activity (activities) locked; cancelation is not possible |
| 250 | TU activity (activities): &1 |
| 251 | &1 deliveries could not be assigned to TU activity |
| 252 | Transportation unit <&1/&2>: delivery assignments and seal entry |
| 253 | Route in delivery &1/&2 does not agree with TU &3/&4 |
| 254 | Departure date/time for route &1 is not same for delivery &2/&3 and TU &4 |
| 255 | Specify a means of transport for the vehicle (MTR) |
| 256 | Means of transport for TU (&1) does not match MTr for vehicle (&2) |
| 257 | &1 of the transportation units could not be found |
| 258 | Yard management is not active in warehouse &1 |
| 259 | ***&1: Log: Message/Action Determination: Post Processing Framework*** |
| 260 | Transportation unit &1/&2/&3: status operation &4 executed |
| 261 | Vehicle &2/&3: status operation &1 executed |
| 262 | Outbound delivery &1 is distributed on multiple TUs; action not possible |
| 263 | TU &1 not assigned to a door; arrival at door not possible |
| 264 | No suitable yard bin assigned to door &1/&2 |
| 265 | Yard bin assigned to door &1/&2; arrival/departure only possible with YM |
| 266 | Vehicle &1 and &2 TU(s) were created |
| 267 | New activities were created for vehicle &1 and &2 TU(s) |
| 268 | Activities were changed for vehicle &1 and &2 TU(s) |
| 269 | Error occurred during saving and subsequent processing |
| 270 | Termination: freight document data could not be imported |
| 271 | Freight document <&1>: deletion of imported freight document data |
| 272 | Freight doc. <&1>: deletion of imported freight document data completed |
| 273 | Termination: freight document data could not be deleted |
| 274 | Internal activity number: TU (&1/&2)/activity &3 |
| 275 | Transportation unit &1/&2 is not currently at a door |
| 276 | No carrier found for transportation unit &1/&2 |
| 277 | Transportation unit &1/&2 is not currently at a checkpoint |
| 278 | Error: freight document with references to activities was changed |
| 279 | You must assign TU to create vehicle from delivery |
| 280 | No transportation unit is currently at door &1 |
| 281 | Vehicle &1 or its TUs are not currently at a door |
| 282 | No Smart Form found in Customizing; default &1 is triggered |
| 283 | Route default value &1 for door &2 does not agree with route &3 for TU &4 |
| 284 | Route default value &1 for door &2 is copied to TU &3/&4 |
| 285 | Next route departure date for route &1 determined and copied to TU &2/&3 |
| 286 | Vehicle activity &1 was not found in the data |
| 287 | External changes to vehicle activity &1 are not allowed |
| 288 | External changes to TU activity &1 are not allowed |
| 289 | Freight document data contains neither vehicle data nor TU data |
| 290 | Vehicle <&1> not found; create new vehicle data |
| 291 | Vehicle <&1> found; create a new vehicle activity only |
| 292 | Vehicle activity found; update data |
| 293 | The Transportation Unit &1 and the TU Activity will be created |
| 294 | TU activity/activities found; update data |
| 295 | Vehicle &1 was created with a new activity |
| 296 | New activity was created for vehicle &1 |
| 297 | Activity was changed for vehicle &1 |
| 298 | &1 new activities were created for transportation units |
| 299 | &1 activities were changed for transportation units |
| 300 | Error: instance could not be generated in BOM for activities |
| 301 | References to activities not found |
| 302 | Door &1 does not exist |
| 303 | Door &1 exists in multiple warehouses; specify warehouse number |
| 304 | Delivery &1 is not fully picked; only partial loading possible |
| 305 | Loading not possible for delivery item &1-&2; not fully picked |
| 306 | Transportation unit &1/&2 could not be loaded/unloaded |
| 307 | Direction is not defined for transportation unit &1/&2 |
| 308 | Action is not possible for TU; execute action for vehicle |
| 309 | Exception "Additional HU" could not be processed |
| 310 | Selection of door is not possible for outbound direction |
| 311 | Combination in the access sequence is not possible for inbound |
| 312 | TU activity &1 can be activated / deactivated via vehicle only |
| 313 | Arrival at checkpoint for vehicle &1 outside of expected arrival time |
| 314 | Arrival at checkpoint for TU &1/&2 outside of expected arrival time |
| 315 | Departure from checkpoint for vehicle &1 outside of expected dep. time |
| 316 | Departure from checkpoint for TU &1/&2 outside of expected departure time |
| 317 | WPT for arrival at/dep. from checkpt &1 is missing in customizing |
| 318 | Arrvl at chkpt status of TU &1/&2 does not match transit stat. of del. &3 |
| 319 | Delivery assignment cannot be changed for completed or invalid TUs |
| 320 | &1 status is not modeled in delivery &2 |
| 321 | Action 'Generate Bill of Lading' is not possible for inb. del./inb. TU |
| 322 | No vehicle is assigned to TU &1/&2; check the bill of lading, as required |
| 323 | Restrict the selection to one yard |
| 324 | Action &1 is not possible; additional active activity exists |
| 325 | Loading date could not be written to the delivery for TU &1/&2 |
| 326 | TU &1/&2 cannot be activated (TU is not in yard) |
| 327 | Freight document number is missing; not possible to process data |
| 328 | TU activity &1 not found in data |
| 329 | Vehicle activity found; enter freight document number |
| 330 | Vehicle activity &1: no update since status is 'Sent to TMS' |
| 331 | TU activity &1: no update since status is 'Sent to TMS' |
| 332 | TU activity &1: deletion is not possible since status is 'Sent to TMS' |
| 333 | Check 1: does /SCWM/VEHICLE exist in all vehicle activities found? |
| 334 | Entry in /SCWM/VEHICLE is missing for vehicle &1 |
| 335 | Check 2: 'vehicle/TU' assignment exists. Does TU activity still exist? |
| 336 | TU/vehicle assignment (/SCWM/TU_VEH) &1 &2 - &3 &4. TU activity missing |
| 337 | Assignment in /SCWM/TU_VEH will be deleted |
| 338 | Check 3: Does /SCWM/TUNIT exist in all TU activities found? |
| 339 | Entry in /SCWM/TUNIT is missing for transportation unit &1/&2 |
| 340 | Check 4: 'vehicle/TU' assignment exists. Does vehicle acty still exist? |
| 341 | TU/vehicle assignment (/SCWM/TU_VEH) &1 &2 - &3 &4: vehicle acty missing |
| 342 | Check 5: 'TU/door' assignment exists. Does door activity still exist? |
| 343 | TU/door assignment (/SCWM/TU_DOOR) &1 &2 - &3 &4: door activity missing |
| 344 | Assignment in /SCWM/TU_DOOR will be deleted |
| 345 | Check 6: Does handling unit for the transportation unit exist? |
| 346 | Handling unit for transportation unit &1/&2 is missing |
| 347 | /SCWM/TUNIT, /TU_SR_ACT, /TU_VEH, /TU_DOOR for TU &1/&2 were deleted |
| 348 | - |
| 349 | No business partner found with SCAC &1 |
| 350 | No statuses were created for &1 (status profile &2) |
| 351 | Deletion not possible for TU &1 due to fixed assignment to vehicle |
| 352 | Partner &1 in role &2 not found |
| 353 | Door &1 &2 is already occupied by transportation unit &3 |
| 354 | Action not possible; transportation unit &1/&2 has not been activated |
| 355 | HU is to be loaded on TU &1/&2, but is already planned for TU &3/&4 |
| 356 | Action not possible; door &1/&2 is not yet actively occupied |
| 357 | Invoice created in system &1 |
| 358 | Door assignment of door &1/&2 to TU &3/&4 lies outside of TU times |
| 359 | Open warehouse tasks still exist for HU &1 |
| 360 | HU &1 was already moved via a warehouse task, removal is not possible |
| 361 | In warehouse &1, staging area &2/&3 is not assigned to door &4 |
| 362 | In warehouse &1, door determination group &3 is not assigned to door &2 |
| 363 | Process code 'I002' does not exist; function not possible |
| 364 | TU still docked to door; deactivation not possible |
| 365 | TU still has stock; deactivation not possible |
| 366 | Update of vehicle data to delivery &1 failed |
| 367 | Storage bin &1 is already used in door &2/&3; choose another one |
| 368 | Maintain a unique storage bin for door &2 in warehouse &1 |
| 369 | Deactivation of TU not possible; loading is not completed |
| 370 | Status: operation &1 with warning is possible for document &2/&3 |
| 371 | Define sequence and number for fixed packaging material |
| 372 | For containers, only one packaging material is permitted in first place |
| 373 | Action stopped artificially due to SET/GET parameter &1 |
| 374 | TU &1 is currently docked at door &2 &3; deletion not possible |
| 375 | Direction of assigned delivery (&1) does not match requested action (&2) |
| 376 | Synchronization with TMS only possible for completely assigned deliveries |
| 377 | Selection of delivery data for transportation unit is faulty |
| 378 | Warehouse number could not be determined |
| 379 | Staging area bin &1 does not exist in staging area &2 |
| 380 | Staging area bin &1 does not exist in staging area group &2 |
| 381 | TU &1 is already assigned to vehicle &2 |
| 382 | Unloading not possible for delivery item &1-&2; not relevant to unloading |
| 383 | &1 TU activities read from archive |
| 384 | &1 vehicle activities read from archive |
| 385 | &1 door activities read from archive |
| 386 | HU &1 is cross-delivery HU |
| 387 | HU &1 is cross-delivery-item HU |
| 388 | Status of delivery &1 was updated |
| 389 | Deactivation of TU not possible; unloading is not completed |
| 390 | Delivery item &1-&2 blocked |
| 391 | Handling unit &1 cannot be processed due to blocked delivery item |
| 392 | Door could not be updated for exception 'additional HU' |
| 393 | HU &1 could not be locked |
| 394 | Wait &1 seconds to lock object '&2' again |
| 395 | HU &1 with reference to inactive deliv. is not included in capacity check |
| 396 | HU &1 with reference to inactive delivery cannot be processed |
| 397 | No suitable door was found for delivery &1 |
| 398 | HU &1 is no longer a top HU; delete HU &1 assignment |
| 399 | HU references to HU &1 were changed |
| 400 | Item &1 &2: GR to TU or Door - simple unloading not possible |
| 401 | Some HUs were unpacked; capacity check was deactivated |
| 402 | No external key was found for internal TU number(s) & |
| 403 | No internal TU number was found for external key &1 &2 &3 |
| 404 | No unique result was found for external key &1 &2 &3 |
| 405 | Status '&1' (&2) does not allow action &3 |
| 406 | Status '&1' (&2) allows action &3 |
| 407 | Departure from checkpoint not possible; goods movement not posted yet |
| 408 | No TUs found on database for selection criteria used |
| 409 | TU consistency check is being performed in the background |
| 410 | HU &1 was deleted |
| 411 | Not all items of HU &1 are selected - unload HU explicitly |
| 412 | Not all items of HU &1 are selected - load HU explicitly |
| 413 | Warehouse process type in the default values is not maintained |
| 414 | Delivery &1 is distributed across multiple TUs |
| 415 | TU &1/&2: assignment to delivery &3 cannot be deleted |
| 416 | Higher-level assignment to TU &1 exists. Item / HU assignment persists |
| 417 | Means of transport &1 not found in construction rules |
| 418 | Goods receipt was already posted for &1 &2 &3 |
| 419 | Goods issue was already posted for &1 &2 &3 |
| 420 | Goods receipt was not yet posted for &1 &2 &3 |
| 421 | Goods issue was not yet posted for &1 &2 &3 |
| 422 | Writing delivery data incorrect for delivery &1 |
| 423 | Staging areas not maintained for door &1 |
| 424 | Staging bay &1 does not exist in warehouse &2 |
| 425 | No door has been assigned to staging bay &1 in warehouse &2 |
| 426 | Staging bay &1 is not assigned to door &3 in warehouse &2 |
| 427 | Enter staging area group and staging area |
| 428 | Perform the action together with TU &1/&2/&3 |
| 429 | Perform the action together with vehicle &1/&2 (TU &3/&4) |
| 430 | No relevant HUs/delivery items found for action &1 |
| 431 | HU &1 is planned on a different TU and cannot be processed |
| 432 | You cannot change storage bin for door &1; still an active TU in bin |
| 433 | Loading not possible for delivery item &1-&2; not relevant for loading |
| 434 | TU &1 could not be updated with &2 &3 &4 |
| 435 | Delivery item &1-&2 is to be loaded on TU &3, but is planned for TU &4 |
| 436 | Delivery item &1-&2 is distributed across multiple TUs |
| 437 | TU is already actively assigned to a vehicle; assignment not possible |
| 438 | TU &1/&2 exists already in active state |
| 439 | A vehicle is already assigned to TU &1/&2/&3 |
| 440 | TU &1/&2/&3: header data of template TU must not be changed |
| 441 | TU &1/&2/&3: input data <> template data: template data being overwritten |
| 442 | TU &1/&2 is not docked at door |
| 443 | Activity &1 is invalid |
| 444 | No activity with the number &3 exists for TU &1/&2 |
| 445 | TU &1/&2 is already active |
| 446 | No activity is available for TU &1/&2 |
| 447 | Departure from checkpoint not possible; loading/unloading not completed |
| 448 | Capacity limit of TU &1 exceeded; status "Inconsistent" was set |
| 449 | Means of transport &1 is not defined in Customizing (/SAPAPO/TRTYPE) |
| 450 | Loading not possible for delivery &1 since not relevant to loading |
| 451 | Unloading not possible for delivery &1 since not relevant to unloading |
| 452 | Transportation unit &1 could not be unlocked |
| 453 | No carrier found for transportation unit &1 |
| 454 | Current direction of TU (&1/&2) does not match required action (&3) |
| 455 | No external key found for internal vehicle number & |
| 456 | No internal vehicle number found for external key &1 &2 &3 |
| 457 | Transportation unit <&1>: start of processing (data record no. &2) |
| 458 | TU <&1/&2>: processing terminated due to error (data record no. &3) |
| 459 | Route & does not exist |
| 460 | Whse task exists for HU &1. Action influences pot. target data determin. |
| 461 | Selection lower limit &1/&2 cannot be reduced to &3/&4 |
| 462 | Selection upper limit &1/&2 cannot be increased to &3/&4 |
| 463 | Product WT exists for HU &1; cancel it manually |
| 464 | Activate state for activity before moving transportation unit |
| 465 | Status "Loading Ended" of TU &1/&2 prevents loading/unloading |
| 466 | TU &1/&2/&3 cannot be moved directly to door; use yard movement |
| 467 | TU assignment to HU &1 cannot be changed |
| 468 | Error when reading delivery |
| 469 | TU/vehicle assignment does not have any overlappings |
| 470 | No checkpoint was found for yard bin &1 in warehouse &2 |
| 471 | TU &1/&2 has already been used again (activity number &3) |
| 472 | Action &1 is not possible; enter the yard warehouse number |
| 473 | TU activity &1 / &2 is already assigned to a vehicle |
| 474 | Select one planned TU activity only for a transportation unit |
| 475 | No staging areas found in warehouse number &1 |
| 476 | No staging areas found in warehouse number &1, storage type &2 |
| 477 | Checkpoint &1 is not defined in warehouse number &2 |
| 478 | No checkpoints found in warehouse number &1 |
| 479 | Number of seals (&1) exceeds maximum number (&2) |
| 480 | First delete freight document &1 |
| 481 | General PPF Customizing error occurred |
| 482 | Staging area &1 is not assigned to staging area group &2 |
| 483 | Active or completed &1 activity &2/&3 cannot be deleted |
| 484 | Time stamps of planned dates/times for activity are not filled |
| 485 | Departure from checkpoint is not possible; TU &1/&2 still at door &3 |
| 486 | Delivery &1 and TU/vehicle have different means of transport &2/&3 |
| 487 | Outbound delivery &1 is assigned to multiple TUs or vehicles |
| 488 | Transportation group &1 does not exist |
| 489 | Bill of lading can only be created using the assigned vehicle |
| 490 | No outbound delivery exists; bill of lading was not created |
| 491 | Multiple active assignments of door/warehouse number &1 &2 not allowed |
| 492 | Planned activity direction (doc. type assgd del.) is not unique |
| 493 | Action 'Extra HU' is possible for an external created HU only |
| 494 | HU &1 can not be assigned to the TU &2 |
| 495 | No Handling Unit specified |
| 496 | Delivery header/item assignments are already existing for TU &1/&2 |
| 497 | Current direction of TU (&1/&2) does not match to HU &3 |
| 498 | An active activity does already exist for the vehicle &1/&2 |
| 499 | Selection of TU activities from database is incorrect |
| 500 | Start of processing |
| 501 | End of processing |
| 502 | Warehouse order &1 for HU &2 has already been processed; action not poss. |
| 503 | No warehouse order exists for HU &1 |
| 504 | Application error: activity number &1 is not a unique ID |
| 505 | TU &1/&2/&3 does not have any deliv./HU refs; load optimiz. not possible |
| 506 | Action &1 is not possible; TU act. &2/&3/&4 is not managed in yard |
| 507 | ERP system &1 is not available |
| 508 | CRM system &1 is not available |
| 509 | Document &1/&2 removed; configuration to route not found |
| 510 | Document &1/&2 removed; not configured for group |
| 511 | Document &1/&2 removed; not configured for user request |
| 512 | Document &1/&2 removed; invoice not requested |
| 513 | Document &1/&2 removed; invoice was already requested |
| 514 | Vehicle activity &1 is locked by external system until &2 &3 (&4) |
| 515 | TU activity &1 is locked by external system until &2 &3 (&4) |
| 516 | Door activity &1 is locked by external system until &2 &3 (&4) |
| 517 | External change key must be provided |
| 518 | External lock cannot be set; vehicle activity &1/&2/&3 archived |
| 519 | External lock cannot be set; TU activity &1/&2/&3 archived |
| 520 | No load optimization created; no outbound delivery exists for &1/&2 |
| 521 | Route &1 for TU &2/&3 contradicts route for delivery &4 |
| 522 | Deliveries assigned to TU &1/&2 do not have a unique route |
| 523 | Action profile &1 not valid for type &2 and means of trans. &3 |
| 524 | Selection of TU data from database is incorrect |
| 525 | Means of Transport &1 is used in vehicle: deletion is not possible |
| 526 | Means of Transport &1 is used in TU: deletion is not possible |
| 527 | Only one activity of TU &1/&2 can be assigned to Vehicle activity &3/&4 |
| 528 | Loading-WT &1 must not be confirmed to the inbound TU &2/&3 |
| 529 | For active yard mgmnt in warehouse &1 enter a Checkpoint |
| 530 | TU &1 already exists - no changes on PM, MTR, Carrier or SCAC |
| 531 | Vehicle &1 has fixed TU assignment; construction rules cannot be skipped |
| 532 | Delivery assignment must not be deleted, TU &1 is already posted GI |
| 533 | Means of transport &1 type &2 not found in construction rules |
| 534 | Synchronization not possible for completed activites |
| 535 | TU with fixed assignment can only be copied using vehicle user interface |
| 536 | TU and Vehicle must be both planed or active - assignment not possible |
| 537 | Assignment of completed activities is not possible |
| 538 | Assignment of completed activity cannot be deleted |
| 539 | Action is not possible for vehicles with multiple fixed TU assignments |
| 540 | No order number for outbound delivery &1 can be determined |
| 541 | No items for outbound delivery order &1 can be determined |
| 542 | No ID number for outbound delivery &1 can be determined |
| 543 | No transportation unit created for vehicle &1 (construction rule?) |
| 544 | Action not possible; completed vehicle or door activities already exist |
| 545 | Transport planning data of TU &1 and delivery &2 do not match |
| 546 | Transport planning data of TU &1 and vehicle &2 do not match |
| 547 | External transport planning: Only delivery header assignments allowed |
| 548 | External transport planning: Delivery &1 is not planned for TU &2 |
| 549 | Invoice before goods issue status for ERP delivery &1 reset |
| 550 | MTr &1 is not defined within Customizing (/SAPAPO/TRTYPE) |
| 551 | Carrier &1 does not exist |
| 552 | Line &1: All key fields are empty |
| 553 | Line &1: Warehouse number not filled |
| 554 | Packaging material with container character has to be optional for MTr |
| 555 | Wave update failed for TU &1/&2 |
| 556 | Error during wave update |
| 557 | Multiple TUs cannot dock on door &1 / &2 in parallel |
| 558 | Action not possible; transportation unit &1/&2 has not been deactivated |
| 559 | Deletion not possible due to Vehicle or Door Activities |
| 560 | Entry already exists |
| 561 | Entry does not exist; error in program memory |
| 562 | Deletion not possible due to its Status |
| 563 | There are still assigned Deliveries / HU's. Deletion not possible |
| 564 | HU &1 not highest level - unloading / loading not possible |
| 565 | Empty HU &1 must not be loaded |
| 566 | Inbound HU without TU reference cannot be loaded (canceled unloading) |
| 567 | Loading direction of door &1 is not valid |
| 568 | Storage type of storage bin &1 does not have role "Staging Area Group" |
| 569 | Dummy |
| 570 | Storage type of storage bin &1 does not have role "Door" |
| 571 | Supply chain unit &1 does not have role "Door" |
| 572 | Supply chain unit &1 does not exist |
| 573 | Outbound activities are not permitted for the staging area &1/&2 |
| 574 | Inbound activities are not permitted for the staging area &1/&2 |
| 575 | Vehicle &1/&2 is already active |
| 576 | Active Activity is no Inbound Activity. Action not possible |
| 577 | more than 1 open door activity - TU activity cannot be completed |
| 578 | TU and Veh refer to different (Yard-)Warehouse - assignment not possible |
| 579 | Transport planning data must not be changed for TU or Vehicle |
| 580 | TU/VEH is planned for (yard-)warehouse &1 - CheckIn to WHS &2 not allowed |
| 581 | Supply chain unit &1 does not have the role Loading Point |
| 582 | Transportation planning systems different for delivery (&2) and TU (&1) |
| 583 | Printing for TU or vehicle failed - data inconsistency |
| 584 | TU and Vehicle are assigned to different FRD - delete FRD first |
| 585 | Deletion of assignement is only permitted to planned assignments |
| 586 | Assignment from external transportation planning must not be deleted |
| 587 | only planned door activities - continue? |
| 588 | Check-Out not permitted due to planned door activities |
| 589 | Warehouse number required for selection of unplanned deliveries |
| 590 | No synchronization required |
| 591 | Call SYNCH with &1 entries |
| 592 | Perform update of door in deliveries |
| 593 | Perform update of waves with TU information |
| 594 | Stop processing; settings defined for parallel processing |
| 595 | Delivery &1 item &2 determinded as unassigned to a TU |
| 596 | Delivery synchronization check called |
| 597 | Delivery item update is called for documents |
| 598 | HU &1 located on TU and determined for assignment |
| 599 | No relevant entries for delivery synchronization determined |
| 600 | Start log &1 |
| 601 | End log &1 |
| 602 | No assignment betw. HU &1 and TU &2 found; check DB for double assignment |
| 603 | Activity period of TU and VEH does not overlap - no assignment possible |
| 604 | New Cross HU &1 assigned |
| 605 | HU &1 determined as relevant but not found or assigned to another TU |
| 606 | New assignment for delivery &1 / &2, HU &3 created |
| 607 | Assignment on HU &1 delivery &2 / &3 deleted |
| 608 | TU from external transportation planning must not be deleted |
| 609 | Docking Location &1 not maintained |
| 610 | Assignment for warehouse number &1 does not exist |
| 611 | Warehouse for doors in loading point &1 is not unique |
| 612 | Yard warehouse for doors in loading point &1 is not unique |
| 613 | Checkpoint for loading point &1 is not unique |
| 614 | No checkpoint found for yard warehouse &1 |
| 615 | Checkpoint for yard warehouse &1 is not unique |
| 616 | No doors assigned to loading point &1 |
| 617 | Loading point &1 is already used for door &2 of warehouse &3 |
| 618 | Transportation unit for appointment &1 not found |
| 619 | Loading point &1 not found |
| 620 | Error reading supply chain unit |
| 621 | Only one planned door activity is allowed |
| 622 | Transportation unit &1 already active for appointment &2 |
| 623 | TU &1 gets processed |
| 624 | Step &1 executed successfully at &2 &3 |
| 625 | You can't make this change, there are other activities for TU &1 already. |
| 626 | No TU profile determined; planned arrival time set as end time |
| 627 | Planned arrival time set using TU profile &1 |
| 628 | Synchronization started at &1 &2 |
| 629 | Synchronization finished at &1 &2 |
| 630 | Goods issue posting started at &1 &2 |
| 631 | Goods issue posting finished at &1 &2 |
| 632 | Outbound delivery creation started at &1 &2 |
| 633 | Outbound delivery creation finished at &1 &2 |
| 634 | Undocking from door started at &1 &2 |
| 635 | Undocking from door finished at &1 &2 |
| 636 | Departure from checkpoint started at &1 &2 |
| 637 | Departure from checkpoint finished at &1 &2 |
| 638 | Update of deliveries started at &1 &2 |
| 639 | Update of deliveries finished at &1 &2 |
| 640 | Requesting invoice started at &1 &2 |
| 641 | Requesting invoice finished at &1 &2 |
| 642 | Action 'Departure from Checkpoint' for TU &1 is processed (or terminated) |
| 643 | Action 'Post GI' for TU &1 is processed (or terminated) |
| 644 | Action 'Request Invoice' for TU &1 is processed (or terminated) |
| 645 | Action 'Departure from Checkpoint' for TU &1 successful |
| 646 | Action 'Post GI' for TU &1 successful |
| 647 | Action 'Request Invoice' for TU &1 successful |
| 648 | Action 'Departure from Checkpoint' for TU &1 not successful |
| 649 | Action 'Post GI' for TU &1 not successful |
| 650 | Action 'Request Invoice' for TU &1 not successful |
| 651 | Loading point &1 is assigned to doors of more than one staging area group |
| 652 | Supply chain unit &1 does not have the role Docking Location |
| 653 | Reversal of departure from checkpoint not allowed for &1 |
| 654 | Arrival at checkpoint without carrier not allowed for &1 |
| 655 | Arrival at checkpoint not allowed for TU &1 with provisional appointment |
| 656 | Departure from checkpoint not allowed for TU &1 |
| 657 | No planned shipping HU exists for TU |
| 658 | More than one planned shipping HU exists for TU |
| 659 | HU &1 is not planned for TU &2 |
| 660 | Staging warehouse tasks created for &1 of &2 assigned HUs |
| 661 | TU &1 not assigned to a door; departure from door not possible |
| 662 | No active TU found |
| 663 | TU &1 is not a transit warehouse TU |
| 664 | Transit warehouse TU &1 cannot be processed by this transaction |
| 665 | Yard management active; use yard movement to move TU &1 to door |
| 666 | Loading not possible; loading is already completed for TU &1 |
| 667 | Loading not possible; goods issue is already posted for TU &1 |
| 668 | Receiving not possible; receiving is already completed for TU &1 |
| 669 | You can't change the carrier, the TU has a fixed vehicle assignment. |
| 670 | Action 'Create Outbound Delivery' for TU &1 is processed (or terminated) |
| 671 | Action 'Create Outbound Delivery' for TU &1 successful |
| 672 | Action 'Create Outbound Delivery' for TU &1 not successful |
| 673 | You can't make this change, there are other activities for vehicle &1. |
| 674 | You can't change the carrier, the vehicle has fixed TU assignments. |
| 675 | No unloading warehouse task for Advanced Shipping and Receiving |
| 676 | You can't assign delivery &1 to a transportation unit in Adv. SR. |
| 677 | Loading not allowed for HU &1. |
| 678 | Loading cannot begin until Shipping Readiness is set to Ready. |
| 679 | Loading cannot begin until freight order is assigned. |
| 700 | Select exactly one transportation unit |
| 701 | Select at least one transportation unit with assigned deliveries |
| 702 | Place &1 only once in the hierarchy |
| 703 | Delivery cannot be placed above TU, ship-to-party, or route |
| 704 | No delivery selected |
| 705 | Select at least one transportation unit |
| 706 | No "Date Type Selection" entered; dates ignored |
| 707 | Enter "Plng Start for/from" for selection with "Plng Start Time from" |
| 708 | Enter either "Plng Start for/from" or "Planning End Day on" for selection |
| 709 | Enter a valid "Date Type Selection" |
| 710 | Enter a "Plng Start for/from" before a "Planning End Day on" |
| 711 | Enter a "Plng Start Time from" before a "Planning End Time at" |
| 712 | Saved search &1 not found |
| 713 | Some deliveries could not be assigned |
| 714 | Deliveries could not be assigned |
| 715 | Some deliveries could not be unassigned |
| 716 | Deliveries could not be unassigned |
| 717 | - Warehouse &1 - Shipping Office &2 |
| 718 | - Warehouse &1 |
| 719 | Transportation unit must be part of (non-initial) hierarchy |
| 720 | Select a free door |
| 721 | Would you like to delete the selected &1 transportation units? |
| 722 | Caution: deliveries are assigned to &1 transportation units |
| 723 | Default search with ID &1 not found |
| 724 | Delivery &1 exceeds maximum capacity of packaging material for TU |
| 725 | &1 is not a valid shipping office for warehouse number &2 |
| 726 | Report for automatic planning cannot be started (program error) |
| 727 | Delivery &1 is not relevant for transportation planning in EWM |
| 728 | There are no relevant delivery items without wave assigment |
| 729 | Wave &1 created |
| 730 | Wave &1 changed |
| 731 | &1 waves created or changed |
| 732 | &1 transportation units assigned to vehicle with multiple TUs |
| 733 | Would you like to execute the action on all TUs involved? |
| 734 | No wave assignment made |
| 735 | Action not possible; TU &1 is currently docked at door |
| 736 | It is not possible to assign staging area, group, or bay to empty TU |
| 737 | Action not possible; TU &1 has already left the yard |
| 738 | No warehouse number found for shipping and receiving office &1 |
| 739 | Loading has not yet started |
| 740 | Loading data for staging area planning failed |
| 741 | Delivery items could not be assigned |
| 742 | Some delivery items could not be assigned |
| 743 | Invoice before goods issue could not be requested for TU &1 |
| 744 | Due to lock error, not all deliveries could be changed |
| 745 | Locking of deliveries for update failed |
| 746 | There are no deliveries assigned to TU &1 |
| 747 | Cancellation not possible; billing document creation has not yet finished |
| 748 | Staging area cannot be updated in deliveries of TU &1 |
| 749 | TU &1 excluded from staging area planning because times are not fixed |
| 750 | BAdI should propose TUs and delivery assignments |
| 751 | Delivery item &1 /&2 already has staging area; excluded from planning |
| 752 | No free time slot for TU &1 determined in staging area planning |
| 753 | Free time slot determined in staging bay &1 for TU &2 |
| 754 | Free time slot determined in staging area &1 for TU &2 |
| 755 | Delivery items of TU &1 already have staging area assigned |
| 756 | No planning for TU &1; WT creation on storage type only (stor.type &2) |
| 757 | Staging area planning ends because no TUs are left for planning |
| 758 | No TU profile for TU &1 - staging area block time = planned start to end |
| 759 | Invalid entry for filling level - filling level set to 100 |
| 760 | Staging bay &1 does not exist in staging area &2 |
| 761 | Staging area &1 does not exist |
| 762 | Staging bay &1 does not exist in staging area group &2 |
| 763 | Delivery assignments no longer up to date; refresh TU |
| 764 | Time specification not valid |
| 765 | Action is not allowed; deliveries exist without header assignment |
| 766 | This action is permitted only for the parent TU of the container |
| 767 | Transportation unit &1 is neither planned nor active |
| 768 | TU &1 and container &2 must either both be planned or both be active |
| 769 | Changing TU type is not permitted |
| 770 | TU and vehicle must belong to the same logistic process |
| 771 | Unloading not permitted for transportation unit &1 |
| 772 | TU container &1 is already loaded on TU &2 |
| 773 | TU &1 is not a TU container |
| 774 | Unloading of TU container &1 not possible; TUC is not loaded to a TU |
| 775 | Unload TU containers from TU &1 before docking at door |
| 776 | Unload TU container &1 from TU &2 before docking at door |
| 777 | TU &1 has not arrived yet |
| 778 | TU container &1 has not arrived yet |
| 779 | Unloading not allowed for HU &1; outbound delivery exists for ODO &2 &3 |
| 780 | Unloading not allowed for HU &1; ODO &2 &3 is contained in an item split |
| 781 | TU container &1 is planned for TU &2 but not loaded yet |
| 782 | Uncoupling an active vehicle resource (AVR) is not permitted |
| 783 | TU &1 has already departed |
| 784 | TU container &1 has already departed |
| 785 | &1 is not a valid goods receipt office for warehouse number &2 |
| 786 | TU container &1 has already been unloaded from TU &2 |
| 787 | TU &1 is blocked for loading |
| 788 | TU &1 is blocked for unloading |
| 789 | This action is not available for TUs in a transit warehouse process |
| 790 | This action is not available for vehicles in a transit warehouse process |
| 791 | TU &1 and vehicle &2 belong to different freight orders |
| 792 | Enter a seal number |
| 793 | Unsealing date for seal &1 cannot be before sealing date |
| 794 | Party role code &1 does not exist |
| 795 | Seal &1 already exists; enter a different seal number |
| 796 | Loading has not completed yet for &1 &2 |
| 797 | Posting started in the background |
| 798 | No door with assigned loading point &1 found |
| 799 | Loading point det. unsuccessful: door &1 not assigned to a loading point |
| 800 | Loading point det. successful: door &1 assigned to loading point &2 |
| 801 | Loading not possible for delivery item &1-&2 due to Transit Procedure. |