/SCMTMS/TOR - Messages from Business Object TO
The following messages are stored in message class /SCMTMS/TOR: Messages from Business Object TO.
It is part of development package /SCMTMS/TOR in software component TM-FRM-FRO. This development package consists of objects that can be grouped under "BO TOR".
It is part of development package /SCMTMS/TOR in software component TM-FRM-FRO. This development package consists of objects that can be grouped under "BO TOR".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Business document with temporary number &1 saved as business doc. &2 |
| 001 | Business document type &1 is defined for the cat &2, the doc. has cat &3 |
| 002 | Define business document category |
| 003 | Business document type &1 does not exist |
| 004 | & processed |
| 005 | & skipped |
| 006 | Define business document type |
| 007 | Cannot create inbound and outbound stops for stop seq. type "Undefined" |
| 008 | No freight order (&1) to process found |
| 009 | Transportation orders not relevant for sending |
| 010 | &1 was deleted |
| 011 | &1 was canceled |
| 012 | &1 has manually created items and cannot be changed by automatic planning |
| 013 | Carrier ranking has been deleted for &1 business documents |
| 014 | &1 (MTr &2) was removed from &3 |
| 015 | Carrier &1 has been replaced by &2 for &3 |
| 016 | Manual adding of FUs is only possible for FUs with only one stage |
| 017 | Business document does not have an ID |
| 018 | Cannot remove vehicle from business document; document is fixed |
| 019 | Creation of settlement document not allowed; document blocked for invoice |
| 020 | No matching transportation activity found for value &1 |
| 021 | No matching event in SAP TM maintained for event code &1 |
| 022 | &1 is not ready for execution according to check condition &2 |
| 023 | Carrier is missing |
| 024 | Purchasing organisation is missing |
| 025 | Document currency is missing |
| 026 | Locations do not match anymore |
| 027 | Scheduling not possible; no planning profile defined |
| 028 | Allocation and business share update postponed for &1 documents |
| 029 | &1: &2 before &3 |
| 030 | Deletion not allowed; document already completed |
| 031 | Deletion not allowed; document already in execution |
| 032 | Deletion not allowed; customs declaration active |
| 033 | No Customizing found for &1 |
| 034 | Freight order or freight booking not sent to ERP |
| 035 | Location sequence contains cycles |
| 036 | No detailed distance calculation possible for stage &1 |
| 037 | No distance and duration calculation possible for stage &1 |
| 038 | &1 stops have been removed from &2 |
| 039 | Define default FSD type if type is relevant for settlement |
| 040 | No matching stop found for location &1 |
| 041 | Location cannot be added because document is fixed |
| 042 | Cannot add freight unit because document is fixed |
| 043 | &1 not defined |
| 044 | &1 must be later than &2; perform scheduling to solve the problem |
| 045 | Multiple stages assigned to the same resource |
| 046 | Freight unit &1 does not exist |
| 047 | Forwarding order &1 does not exist |
| 048 | FU &1 contains container items; no containers allowed (shipping type LCL) |
| 049 | Forwarding order &1; freight unit &2 already planned |
| 050 | &1 manually entered shipper or ship-to party; no automatic determination |
| 051 | FU &1 is already planned |
| 052 | Freight unit &1; source and destination location do not match |
| 053 | FWO &1; source and destination location of freight unit &2 do not match |
| 054 | Goods value of item &1 converted from currency &2 to &3 |
| 055 | Goods value for customs of item &1 converted from currency &2 to &3 |
| 056 | Insurance value of item &1 converted from currency &2 to &3 |
| 057 | Goods value of item &1; currency conversion from &2 to &3 failed |
| 058 | Goods value for customs of item &1; crcy conversion from &2 to &3 failed |
| 059 | Insurance value of item &1; currency conversion from &2 to &3 failed |
| 060 | Freight order is not completely invoiced |
| 061 | Freight order &1 is blocked for invoicing |
| 062 | Subcontracting status cannot be set for &1 |
| 063 | Confirmation status cannot be set for &1 |
| 064 | Shipping types of freight unit (&1) and booking (&2) are incompatible |
| 065 | Movement types of freight unit (&1) and booking (&2) are incompatible |
| 066 | Movement type of FU (&1) and service level of FB (&2,&3) are incompatible |
| 067 | &1: Select only one ranking entry; cannot assign multiple carriers |
| 068 | Cannot change shipping type to LCL; container is assigned |
| 069 | Cannot assign LCL freight unit to booking with service levels &1/&2 |
| 070 | Transportation mode &1 not valid for means of transport &2 |
| 071 | Transportation mode not defined for means of transport &1 |
| 072 | Cannot move item &1; item is subitem of predecessor document |
| 073 | Item &1 cannot be used to assign items within execution documents |
| 074 | Item &1 is already loaded; reassignment not possible |
| 075 | Item &1 is already unloaded; reassignment not possible |
| 076 | No stage with mandatory stage type &1 exists |
| 077 | No container specified for buyer's consolidation in freight booking |
| 078 | Container &1 has FWO items with different bill-to parties |
| 079 | No FWO items assigned to container &1 |
| 080 | Cannot create FWSD; purchasing org. &1 is not a forwarding house |
| 081 | Status cannot be set to "In Execution"; document is blocked for execution |
| 082 | Selected freight units cannot be inserted |
| 083 | Transportation mode &1 is not allowed for stage type &2 |
| 084 | Stage type &1 is not allowed for movement type &2 |
| 085 | Deletion not allowed; document has been sent to external partners |
| 086 | Stage &1: &2 (source) should be earlier than &3 (source) |
| 087 | Stage &1: &2 (destination) should be earlier than &3 (destination) |
| 088 | Stage &1: &2 (source) should be earlier than &3 (destination) |
| 089 | Incomplete stage chain in assignment of stage &1 to freight document &2 |
| 090 | Define a stage ID |
| 091 | Enter a source location for stage &1 |
| 092 | Enter a destination location for stage &1 |
| 093 | Source and destination of stage &1 must not be identical |
| 094 | Departure of stage &1 must not be after arrival |
| 095 | User &1 is not assigned to planning and execution org &2 of stage &3 |
| 096 | Stage &1 is defined multiple times for the same document |
| 097 | FOs with star-shaped topology must have identical start location |
| 098 | Organization interaction status changed to &1 for stage &2 |
| 099 | Cannot change organization interaction status from &1 to &2 for stage &3 |
| 100 | Stage &1 is delayed; new expected arrival time is &2 |
| 101 | Check tracking information for &1 |
| 102 | Cannot remove stops from &1 |
| 103 | Changing location &1 is not possible; propagation of change failed |
| 104 | Stop at location &1 in &2 has time conflict |
| 105 | &1 has conflict at location &2: Unloading time is earlier than loading |
| 106 | &1: Conflict at location &2, load constraint before unload time |
| 107 | Stop & 1 at location &2 has been identified as first relevant stop |
| 108 | Selected event does not match event code &1 |
| 109 | &1: Time conflict at location &2 |
| 110 | Event &1 has already been reported for stop &2 at location &3 |
| 111 | Freight order sent to carrier |
| 112 | Departure from location &1 of &2 is planned before arrival |
| 113 | Define pick-up location when creating freight order for pick-up |
| 114 | Define port of loading when creating freight order for pick-up |
| 115 | You cannot assign items to new HBL; items are already assigned |
| 116 | Freight order for pick-up/delivery already exists for FB &1 item &2 |
| 117 | Date is not within time frame of assigned booking |
| 118 | Freight order for pick-up created |
| 119 | Freight order for delivery created |
| 120 | You cannot create freight orders for pick-up/delivery with transit stops |
| 121 | &1 has been changed |
| 122 | Date has been changed by &1 days, &2 hours, and &3 minutes |
| 123 | Quantity has been changed by &1 |
| 124 | Source location has changed |
| 125 | Destination location has changed |
| 126 | Define master bill of lading ID first |
| 127 | Location &1 changed to &2 in &3 based on location change in &4 |
| 128 | New source location &1 added to &2; cannot change source location &3 |
| 129 | New destination location &1 added to &2; cannot change dest. location &3 |
| 130 | Destination location &1 changed to &2 in &3 |
| 131 | Split of item &1 not possible; only cargo items can be split |
| 132 | Split of item &1 not possible; new item must be assigned to capacity item |
| 133 | Item split failed for item &1; split quantity exceeds available quantity |
| 134 | Merge of items &1 and &2 not possible; only allowed for cargo items |
| 135 | Merge of items &1 and &2 not possible; only allowed for split items |
| 136 | Merge of items &1 and &2 not possible; item origin differs |
| 137 | Item &1 has been merged with item &2 and was then deleted |
| 138 | Container &1 cannot be used for buyer's consolidation; several consignees |
| 139 | Not all requirements have the same air waybill type |
| 140 | AWB type &1 (&2) does not allow multiple order or delivery documents |
| 141 | Item &1 cannot be reassigned |
| 142 | Agreement party should be the same for main carriage and on-carriage |
| 143 | Consolidation not allowed |
| 144 | Source locations are not unique; no freight order created |
| 145 | Destination locations are not unique; no freight order created |
| 146 | Locations are not unique; freight booking items cannot be inserted |
| 147 | Transportation mode in FU stage and freight document must be the same |
| 148 | Handling code &1 does not exist |
| 149 | Arrival at location &1 of &2 is planned after departure from the location |
| 150 | *****************Misc******************************* |
| 151 | Action cannot be performed for documents with life cycle status "&1" |
| 152 | Event "&1" reported |
| 153 | Life cycle status set manually from "&1" to "&2" |
| 154 | Carrier taken over from predecessor document |
| 155 | Carrier of predecessor documents is different from carrier of document |
| 156 | Predecessor documents have different carriers |
| 157 | Execution tracking relevance changed to "&1" |
| 158 | Input field &1 is mandatory when reporting an event |
| 159 | Cannot copy item &1 of booking &2; item is not a container |
| 160 | You can create freight orders for pick-up for containers only |
| 161 | Enter seal number (for container item &1) |
| 162 | Before executing transportation, set the execution status to "&1" |
| 163 | Date, time, or time zone contains invalid or inconsistent values |
| 164 | Setting of execution status not possible for some items |
| 165 | Sealing party &1 does not exist |
| 166 | Unsealing party &1 does not exist |
| 167 | Shipped-on-board date must not be in the future |
| 168 | Enter values in all required entry fields (missing field: &1) |
| 169 | Cannot copy |
| 170 | &1 is not a valid SCAC for the related business partner |
| 171 | Carrier &1 is blocked; you selected the "Posting Block" checkbox |
| 172 | &1 is not a valid communication party of carrier &2 |
| 173 | Only one business partner of partner function &1 allowed |
| 174 | Discrepancy type &1 does not exist or is not valid for document type &2 |
| 175 | Discrepancy type &1 is not permitted; use quantity discrepancy |
| 176 | Discrepancy type &1 is not permitted; use general discrepancy |
| 177 | Party &1 must not be used for the same partner function &2 twice |
| 178 | MBL or MAWB number &1 determined |
| 179 | HBL or HAWB number could not be determined |
| 180 | House bill of lading/house air waybill &1 does not exist |
| 181 | MBL or MAWB number &1 returned to stock |
| 182 | MBL or MAWB number already drawn |
| 183 | MBL or MAWB number not yet drawn |
| 184 | Customer pick-up/self-delivery freight order is not assigned to stage |
| 185 | Customer pick-up/self-delivery freight order is already assigned to stage |
| 186 | Selected stage is not a stage for customer self-delivery/customer pick-up |
| 187 | &1 is not a valid airline code for the related business partner |
| 188 | &1 is not a valid master air waybill prefix for the assigned carrier |
| 189 | &1 is not a valid airline code for the first carrier |
| 190 | Self-delivery/customer pick-up FOs must not be subcontracting-relevant |
| 191 | Self-delivery/customer pick-up FOs must not have shipper/cons. determ. |
| 192 | Self-delivery/customer pick-up FOs must not be relevant for charges/inv. |
| 193 | Self-delivery/customer pick-up FOs must not require a compliance check |
| 194 | Self-delivery/customer pick-up FOs must not be relevant for ERP shipment |
| 195 | Number range for MBL or MAWB not found |
| 196 | Multiple MBL or MAWB number ranges found |
| 197 | Define number of pieces to be split |
| 198 | Multiple number ranges found for house air waybills |
| 199 | Number range for HBL or HAWB not found |
| 200 | ***** Document type (BO Transportation Order) Customizing messages |
| 201 | Only one default type is allowed; currently checked types are &1 (&2) |
| 202 | Type &1 already defined as &2 type |
| 203 | No default type defined (&1) |
| 204 | Only one default freight order type allowed for ERP shipment integration |
| 205 | HBL or HAWB number &1 drawn |
| 206 | For customer self-delivery/pick-up, select stop sequence type "Undefined" |
| 207 | Freight order type '&1' does not exist |
| 208 | Strategy &1 does not exist with the requested service type |
| 209 | MBL or MAWB number &1 not returned to stock |
| 210 | HBL or HAWB number &1 not returned to stock |
| 211 | HBL or HAWB number &1 returned to stock |
| 212 | You cannot use sold-to party for &1 as agreement pty; Incoterms defined |
| 213 | &1 is not a valid communication party of issuing carrier &2 |
| 214 | Master air waybill number &1 is invalid |
| 215 | House air waybill number &1 is invalid |
| 216 | Stage type &1 is not allowed for stage profile &2 |
| 217 | Define auto-confirmation profile if organization interaction is mandatory |
| 218 | Freight unit with house air waybill &1 cannot be inserted |
| 219 | Cannot change shipping type from &1 to &2 |
| 220 | Cannot change loading type from &1 to &2 |
| 221 | AWB type does not allow assignment of selected freight unit stages |
| 222 | "Doc. Must be Published for Planning" only allowed for transp. mode "Air" |
| 223 | Document cut-off changed with ETD offset &1 hours of business partner &2 |
| 224 | Document cut-off changed with factory calendar &1 of business partner &2 |
| 225 | Document cut-off changed to calling hours of business partner &1 |
| 226 | Document cut-off not changed; no appointment for business partner &1 |
| 227 | Type could not be determined for stage &1 |
| 228 | Cannot build HBL for &1; items have different groupings |
| 229 | Cannot build HBL for item &1; freight unit not found |
| 230 | Purchasing organization missing in order &1 |
| 231 | Cannot build HBL/HAWB; no building strategy found for document type |
| 232 | Status has been set to "&1" although document is blocked for execution |
| 233 | Traffic directions of order doc. or delivery document and FB do not match |
| 234 | For type &1 and item category &2, only one default item type is allowed |
| 235 | Specify a default item type for type &1 and item category &2 |
| 236 | Subitem type &1 of item type &2 is not of multi-item type 'C' |
| 237 | Wrong document type determined for TU; default type has been applied |
| 238 | Item type &1 is of multi-item type 'E'; specify a subitem type |
| 239 | Cannot create FWSD from import booking; create from import FWO |
| 240 | Buyer's consolidation not possible for container &1; main stages differ |
| 241 | Item weights and volume split in proportion to the pieces to be split |
| 242 | Item number &1: Incorrect use of item type &2 as multi-item child |
| 243 | Item type &1 is a child item type, cannot be used as default item type |
| 244 | Cannot insert item type &1 (child item type) below this item |
| 245 | Transportation mode not defined for &1 |
| 246 | For item type &1, only one default service type is allowed |
| 247 | Cannot build HBL; different HBL numbers for items available |
| 248 | Navigation not possible; &1 is not of category 'Service' |
| 249 | Type &1: Item type &2 is not of category 'Service' |
| 250 | Define target business document type or category |
| 251 | Changing the type is not supported for &1, only FUs can be changed |
| 252 | Type &1 does not exist |
| 253 | Type of &1 cannot be changed since life cycle status is not "New" |
| 254 | Type of &1 cannot be changed since it is currently being planned |
| 255 | Number range has been changed, new ID for &1 is &2 |
| 256 | Calculation profile for purchasing organization &1 not found |
| 257 | Set "Shipment Creation Relevance" to "F" |
| 258 | No default type defined |
| 259 | Only one default type is allowed; currently checked types are &1 |
| 260 | Unspecified error when changing a movement type |
| 261 | Movement type &1 does not exist |
| 262 | Planned stage is not suitable for stage type seq. of movement type &1 |
| 263 | Stage type seq. of mvt type &1 is not suitable for all exist. stages |
| 264 | Stage &1 has no stage type; change from &2 to &3 is not possible |
| 265 | Movement type cannot be changed to &1; all stages would be deleted |
| 266 | Internal identification number is &1; numbers < 900 are not allowed |
| 267 | Select one or two matching transportation units to create triangulation |
| 268 | Transportation unit &1 and &2 are empty return TUs |
| 269 | Transportation unit &1 and &2 are empty provisioning TUs |
| 270 | Transportation unit for empty provisioning already exists for item &1 |
| 271 | Transportation unit for empty return already exists for item &1 |
| 272 | Empty provisioning TU &1 is already planned; triangulation not possible |
| 273 | Triangulation for transportation unit &1 has been revoked |
| 274 | TU &1 is neither an empty return TU nor an empty provisioning TU |
| 275 | Transportation unit &1 is not an empty return transportation unit |
| 276 | Transportation unit &1 is not an empty provisioning transportation unit |
| 277 | Transportation unit &1 is not triangulated |
| 278 | Transportation units &1 and &2 have been triangulated |
| 279 | Return TU &1 and provisioning TU &2 do not have the same equipment type |
| 280 | Last main item &1 must not be deleted |
| 281 | Define loading start and end date |
| 282 | Transportation unit &1 does not exist |
| 283 | Item type &1 is still used in type &2 of transportation mode &3 |
| 284 | Resource information propagated to successor transportation unit |
| 285 | Stage sequence is incorrect |
| 286 | Child item type &1 must be of same item category as item type &2 |
| 287 | ***** Messages Related to Triangulation in Addition to 267:279 ****** |
| 288 | Transportation unit &1 must have the quantity "1" for triangulation |
| 289 | Requested return of TU &1 needs to be earlier than provisioning of TU &2 |
| 290 | &1 is not ready for execution; load plan status "finalized" is required |
| 291 | Reassignment of multi-item child only allowed to other multi-item parent |
| 292 | As a multi-item, &2 cannot be used as default for document type &1 |
| 293 | Transportation mode category &1 not valid for document category &2 |
| 294 | Actual quantities of &1 not split automatically |
| 295 | Split of item &1 within referenced item hierarchy not possible |
| 296 | Split of item &1 not possible; customs group already exists |
| 297 | You can only manually add transportation units with one stage |
| 298 | Selected transportation unit cannot be inserted |
| 299 | Actual quantities of &1 not merged automatically |
| 300 | ***Check messages from readiness status/SCMTMS/CL_TOR_DET_EXEC_READY |
| 301 | &1 is not ready for execution according to condition &2 |
| 302 | &1 is not ready for execution; it has status "Blocked for Exec." |
| 303 | &1 is not ready for execution; confirmation required from carrier |
| 304 | &1 not ready for execution; tendering is in process |
| 305 | &1 not ready for execution; subcontracting-relev. but no carrier assigned |
| 306 | &1 not ready for execution; carrier did not confirm but conf. is required |
| 307 | &1 not ready for execution; cargo is not assigned to a container |
| 308 | &1 not ready for execution; no cargo assigned |
| 309 | Document is relevant for subcontracting but a carrier is not assigned |
| 310 | Freight unit &1 is not ready for planning |
| 311 | Forwarding order &1; freight unit &2 is not ready for planning |
| 312 | &1 not ready for execution; driver assignments are incorrect |
| 313 | Discrepancies of &1 not split automatically |
| 314 | Discrepancies of &1 not merged automatically |
| 315 | &1 could not be inserted |
| 316 | Split items will be merged as quantities differ from predecessor item |
| 317 | Consignment order with external ID &1 could not be inserted |
| 318 | Incorrect data entered for the whse loading stop or whse unloading stop |
| 319 | Execution status cannot be changed; document is already invoiced |
| 320 | *****************Misc******************************* |
| 321 | Sealing date of seal &1 must not be later than unsealing date |
| 322 | Check complete; master air waybill can be closed |
| 323 | It is not possible to finalize MAWB &1; MAWB is blocked for execution |
| 324 | It is not possible to finalize MAWB &1; tendering is in process |
| 325 | Cannot finalize MAWB &1; subcontracting-relevant but no carrier assigned |
| 326 | Cannot finalize MAWB &1; confirmation has not been received from carrier |
| 327 | It is not possible to finalize MAWB &1; cargo not assigned to container |
| 328 | It is not possible to finalize MAWB &1; no cargo assigned |
| 329 | Freight orders for pick-up &1 to &2 created |
| 330 | Freight orders for delivery &1 to &2 created |
| 331 | Uplift date must not be in the future |
| 332 | Master air waybill closed |
| 333 | Execution status of doc. &2 set to "&1" |
| 334 | Execution status cannot be changed (current status &1) |
| 335 | Execution status already set to "&1" |
| 336 | Master air waybill not closed |
| 337 | Air waybill finalized |
| 338 | Air waybill not finalized |
| 339 | MAWB prefix &2 unknown or does not match airline code &1 |
| 340 | No ACS-relevant FU's selected |
| 341 | Error in linear stage sequence because locations do not match |
| 342 | Save canceled |
| 343 | Run in simulation mode; action not performed |
| 344 | &1 documents selected for processing |
| 345 | &1 documents processed |
| 346 | &1 locked documents will not be taken into account |
| 347 | &1 cannot be copied to document type with different transportation mode |
| 348 | &1 cannot be copied to document type with different multi-PU/DL settings |
| 349 | Air-specific data will be reset due to the change of transportation mode |
| 350 | ******* ITEM messages ******** |
| 351 | Creation of subitems without category is not allowed |
| 352 | Creation of subitems with category &1 is not allowed |
| 353 | Subitem creation failed; parent item could not be determined |
| 354 | Items with category &1 cannot have any subitems |
| 355 | Item with category &1 cannot be subitem of item with category &2 |
| 356 | Hierarchy of items with category &1 cannot be changed |
| 357 | Items of category &1 must not be deleted |
| 358 | &1 still planned on item &2; item cannot be deleted |
| 359 | Locations cannot be changed; at least one location must be given |
| 360 | Item &1 with category &2 must not be a main item |
| 361 | Item &1 has no category |
| 362 | Item &1 has no source stop |
| 363 | Source stop of item &1 does not exist |
| 364 | Item &1 has no destination stop |
| 365 | Destination stop of item &1 does not exist |
| 366 | Quantity value is missing for &1 |
| 367 | Unit of measure is missing for &1 |
| 368 | Wrong unit of measure &1 for &2 |
| 369 | &1 cannot have local items |
| 370 | Creation of items is not allowed in freight units |
| 371 | Cannot create items of category &1 |
| 372 | Locally changed item &1 overwritten after update of referenced item |
| 373 | Gross weight must be higher than net weight |
| 374 | Number of container must be maintained in pieces, not in TEU |
| 375 | No charge-relevant item available; cannot create settlement document |
| 376 | Specify the equipment group for equipment type &1 |
| 377 | Equipment type &1 of group &2 is not defined in Customizing |
| 378 | Specify an equipment type for equipment group &1 |
| 379 | Specify the container count |
| 380 | Number of cont. is initial, no container items can be created |
| 381 | &1 container items of &2 confirmed cont. created, &3 already exist |
| 382 | &1 container items of &2 requested cont. created, &3 already exist |
| 383 | Qty reduction for booking capa. requirements &1 not completely possible |
| 384 | Cannot assign &1 to referenced item &2 |
| 385 | Cannot delete &1; requirement is assigned to &2 |
| 386 | Cannot delete item &1 |
| 387 | Cannot delete item &1; only main cargo items can be deleted |
| 388 | Item is not assigned to a container |
| 389 | Only container items can be assigned to booking capacity reservation |
| 390 | Equip. type or group of BCR does not match container item type and group |
| 391 | Number of containers for item &1 based on subitems adapted to &2 |
| 392 | Discrepancy already exists; no default discrepancy created |
| 393 | No default discrepancy type available; set discrepancy type manually |
| 394 | Item quantity is only changed locally; predecessor documents not updated |
| 395 | Cannot set status &1 for item &2 |
| 396 | Freight booking &1 contains no items for FO for pick-up/delivery |
| 397 | Commodity type &1 and commodity code &2 are not a valid combination |
| 398 | Cannot move unconfirmed items |
| 399 | Subitems used or resources assigned; multi-item quantity changed to &1 |
| 400 | **********Messages Used during Change Controller Processing********* |
| 401 | Processing of change strategy "&1" started |
| 402 | Strategy "&1" processed successfully by change controller |
| 403 | Planning removed for "&1" from "&2" |
| 404 | Change strategy "&1" registered for asynchronous processing |
| 405 | Trigger "&1" set for later processing of strategy "&2" |
| 406 | Processing of deletion strategy "&1" started |
| 407 | Processing of save strategy "&1" started |
| 408 | Save strategy "&1" registered for asynchronous processing |
| 409 | Trigger "&1" could not be set for later processing of strategy "&2" |
| 410 | Creation strategy "&1" registered for asynchronous processing |
| 411 | Strategy "&1" could not be processed successfully |
| 412 | Processing of creation strategy "&1" started |
| 413 | Evaluation of date tolerance condition "&1" resulted in a change |
| 414 | Evaluation of quantity tolerance condition "&1" resulted in a change |
| 415 | Carrier selection not possible due to missing carrier selection settings |
| 416 | Save strategy "&1" is processed synchronously |
| 417 | Creation strategy "&1" is processed synchronously |
| 418 | Change strategy "&1" is processed synchronously |
| 419 | Equipment group &1 is not allowed for transportation mode &2 |
| 420 | Change-strategy determination condition &1 does not exist |
| 421 | Quantity tolerance condition &1 does not exist |
| 422 | Date tolerance condition &1 does not exist |
| 423 | Check condition "Ready for execution" &1 does not exist |
| 424 | Condition for default means of transport &1 does not exist |
| 425 | Service level condition &1 does not exist |
| 426 | Determination rule condition &1 does not exist |
| 427 | Planning and execution organization &1 does not exist |
| 428 | Purchasing organization &1 does not exist |
| 429 | Planning and execution group &1 does not exist |
| 430 | Purchasing group &1 does not exist |
| 431 | Pick-up freight order type &1 does not exist |
| 432 | Delivery freight order type &1 does not exist |
| 433 | Service order type &1 does not exist |
| 434 | Means of transport &1 does not exist |
| 435 | Dangerous goods profile &1 does not exist |
| 436 | Web dynpro application configuration &1 does not exist |
| 437 | Shipping type &1 is not compatible with current tranportation mode |
| 438 | Import booking type &1 does not exist |
| 439 | Movement type &1 does not exist |
| 440 | Condition for carrier selection &1 does not exist |
| 441 | Customs profile &1 does not exist |
| 442 | Condition &1 for PU/DLV window determination does not exist |
| 443 | Freight order type condition &1 does not exist |
| 444 | Cannot create settlement for FO &1; settlement not specified for stages |
| 445 | Specify an equipment type for ULD &1 |
| 446 | Change controller: &1 not in IT_KEY but in TOR_KEY_ACTIVE |
| 447 | Action is not allowed for discrepancy type &1 |
| 448 | Marked entry with discrepancy type &1 is already resolved |
| 449 | Discrepancy of item &1 can only be resolved at parent item level |
| 450 | *** Transportation order confirmation messages *** |
| 451 | Mandatory stop &1 was not confirmed by carrier |
| 452 | Error in message: First stop must not be of role "MT" |
| 453 | Error in message: Unknown location &1 |
| 454 | Error in message: No outbound stop defined for location &1 |
| 455 | Container count of booking confirmed |
| 456 | Cargo items of booking confirmed |
| 457 | Error in message; invalid executing carrier &1 |
| 458 | Confirmed actual transportation date must be in the past |
| 459 | A confirmation must not change party &1 with part. func. &2 into party &3 |
| 460 | Unexpected local cargo must be resolved by assigning order/del. doc. item |
| 461 | A confirmation must not unassign party &1 with partner function &2 |
| 462 | Driver &1 does not exist |
| 463 | &1: Business document is not relevant for driver planning |
| 464 | You cannot change number of required drivers; document &1 is fixed |
| 465 | You cannot change number of required drivers; invalid action parameters |
| 466 | You cannot change the document settings; invalid action parameters |
| 467 | You cannot change driver assignment type for business document &1 |
| 468 | You cannot change driver assignment type; document &1 is fixed |
| 469 | You cannot change number of required drivers for business document &1 |
| 470 | *** Inbound Service for ERP Shipment Messages *** |
| 471 | Delivery &2, item &3: Product &1 unknown |
| 472 | Business document ID &1 exceeds 20 characters |
| 473 | Quantity and unit must be filled: Delivery &1, item &2, package &3 |
| 474 | No ERP shipment number or system number provided |
| 475 | Corresponding stop is missing in the stop successor |
| 476 | Active freight order for ERP shipment &1 is not unique |
| 477 | Location &1 (type code &2, system &3) not found |
| 478 | Product with product ID &1 (from partner system &2) not found |
| 479 | Stages missing in stop sequence; stops must be connected by stages |
| 480 | Conversion of sending business system &1 failed |
| 481 | Cancellation of shipment failed (shipment ID &1) |
| 482 | Active ERP shipment &1 not found |
| 483 | Partner &1 not found or conversion failed |
| 484 | Doc. &1 exists, but it was not updated; update is not supported yet |
| 485 | Queue for ERP document &1 is currently locked |
| 486 | Status update failed (shipment ID &1) |
| 487 | No product ID can be determined for vehicle in FO &1, item &2 |
| 488 | No product ID can be determined for container in FO &1, item &2 |
| 489 | No container found for ERP product &1 |
| 490 | Changing the number of containers or adding packaging is not permitted |
| 491 | Cannot determine addresses for ERP shipment &1 |
| 492 | Equipment group &1 is not defined in Customizing |
| 493 | Transportation unit &1 is already planned |
| 494 | Transportation unit &1 is not ready for planning |
| 495 | TU &1: Src and dest. locations of FU and capacity document do not match |
| 496 | Forwarding order &1: Transportation unit &2 already planned |
| 497 | Forwarding order &1: Transportation unit &2 is not ready for planning |
| 498 | Forw. order &1: Source and destination location of TU &2 do not match |
| 499 | Transportation unit with house air waybill &1 cannot be inserted |
| 500 | ***** technical consistency check messages ***** |
| 501 | Stop &1 of &2 has an invalid assignment |
| 502 | Stop &1 of &2 has an invalid stop assignment |
| 503 | Stop &1 of &2 has an invalid item assignment |
| 504 | Assignments of stop &1 of &2 point to different instances |
| 505 | Sequence must not be already defined |
| 506 | Combination of country &1 and region &2 must not be already defined |
| 507 | Sequence must be specified for country/region &1 |
| 508 | Means of transport &2 is not valid for transportation mode &1 |
| 509 | Transportation mode &1 is invalid |
| 510 | There is an archived forwarding order related to this freight booking |
| 511 | First transit country/region is the same as the source location (&1) |
| 512 | Last transit country/region is the same as the destination location (&1) |
| 513 | Successive transit ctry/reg are identical; specify a different ctry/reg |
| 514 | Transit ctry/reg sequence number already in use; specify a unique number |
| 515 | Screening Method &1 requires a text |
| 516 | Specify screening method |
| 517 | FU &1 with ACS-Status &2 requires more than one Screening Method |
| 518 | "Copy with new document type" is only supported for freight booking |
| 519 | Company codes of item &2 and the header level of document &1 don�t match |
| 520 | Generic security code is initial |
| 521 | Master air waybill number must not be initial |
| 522 | Carrier must not be initial |
| 523 | IATA airport code must not be initial |
| 524 | Flight number must not be initial |
| 525 | ETA must not be initial |
| 526 | ETD must not be initial |
| 527 | Shipping type must not be initial |
| 528 | Capacity (weight) must not be initial |
| 529 | Capacity (volume) must not be initial |
| 530 | Capacity (pieces) must not be initial |
| 531 | Service level must not be initial |
| 532 | Origin organization must not be initial |
| 533 | Contract basis must not be initial |
| 534 | Mandatory service type &1 missing |
| 535 | Package unit cannot be created; no default PU type defined for FO type &1 |
| 536 | Package unit cannot be created; default PU type &1 has wrong settings |
| 537 | Package unit cannot be created; execution started for &1 |
| 538 | &1 cannot be canceled; execution already started |
| 539 | &1 cannot be canceled; doc. type does not fit to default PU type of &2 |
| 540 | Provisioning location or time of transportation unit &1 has changed |
| 541 | Return location or time of transportation unit &1 has changed |
| 542 | Cannot split; stage is assigned to default route |
| 543 | Cannot convert &1 to freight order; business document is blocked |
| 544 | Cannot assign &1 to freight order; business document is blocked |
| 545 | Cannot remove stops from &1 &2; a default route is assigned |
| 546 | Cannot merge; stage is assigned to default route |
| 547 | &1 &2 has been unassigned from default route |
| 548 | Default route cannot be unassigned; no default route applied |
| 549 | Business partner &1: One-time account not supported |
| 550 | ***Consistency check message used in /SCMTMS/CL_TOR_HELPER_VALIDATE |
| 551 | &1 has an invalid value in field &2 |
| 552 | Execution organization defined for &1 does not exist |
| 553 | Execution group defined for &1 does not exist |
| 554 | Purchasing organization defined for &1 does not exist |
| 555 | Purchasing group defined for &1 does not exist |
| 556 | Person responsible defined for &1 does not exist |
| 557 | Printing profile defined for &1 does not exist |
| 558 | Sequence of assigned stops of &1 is incorrect |
| 559 | &1 and &2 of &3 not specified |
| 560 | &1: &2 must be specified |
| 561 | &1: &2 must not be earlier than &3 |
| 562 | Movement type for &1 does not exist |
| 563 | Shipping type for &1 does not exist |
| 564 | Service level &1 is not defined for carrier &2 |
| 565 | Ctry/region-specific security status &1 incompatible with ACS status &2 |
| 566 | &1 has handling code &2; this code is excluded from &3 |
| 567 | &1 does not have handling code &2; this code is required for &3 |
| 568 | FU &1 incompatible with booking &2 with ACS Status 'Not Checked' |
| 569 | FU &1 with ACS status 'Not Checked' incompatible with booking &2 |
| 570 | Freight term defined for &1 does not exist |
| 571 | Only one stop (stop &2) of &1 is assigned to freight document |
| 572 | There are no inbound stops in &1 |
| 573 | There are no outbound stops in &1 |
| 574 | There are more inbound stops (&1) than outbound stops (&2) in &3 |
| 575 | There are more outbound stops (&1) than inbound stops(&2) in &3 |
| 576 | Only one unloading stop allowed in &1, but there are &2 unloading stops |
| 577 | Only one loading stop allowed in &1, but there are &2 loading stops |
| 578 | Stop &1: Stop sequence not unique |
| 579 | Stage type &1 not valid for stage category &2 |
| 580 | FO/FB &1: Inbound stop &2 and outbound stop &3 have different locations |
| 581 | Location sequence not consistent |
| 582 | ACS status &1 not allowed for freight bookings |
| 583 | ULD number &1 does not comply with the standard format |
| 584 | &1 cannot be canceled; PU creation rule in doc. type of &2 doesn't fit |
| 585 | &1 cannot be canceled; &2 is not assigned to the delivery stage |
| 586 | Forwarding orders cannot be created for service items |
| 587 | Cannot delete assignment; internal settlement document exists |
| 588 | &1 must be later than &2 |
| 589 | Time conflict in &1 in &2 |
| 590 | Late arrival at location &2 in predecessor &1 causes time conflict |
| 591 | Late arrival at location &2 causes time conflict in successor &1 |
| 592 | Time constraints in &1 are not consistent with time defined in &2 |
| 593 | Time conflict in &1 accord. to rule for PU/DLV window defined in Cust. |
| 594 | Check for cross-document time-conflicts completed without errors |
| 595 | Ready for execution check completed without errors |
| 596 | Capacity check completed without errors |
| 597 | Incompatibility check completed without errors |
| 598 | Dangerous goods check completed without errors |
| 599 | Checks completed without errors |
| 600 | **** Stop consistency ***** |
| 601 | Stop &1 has no logistical location assigned |
| 602 | Source location is missing |
| 603 | Destination location is missing |
| 604 | Source location is missing for &1 |
| 605 | Destination location is missing for &1 |
| 606 | Action not possible on stop; execution has started |
| 607 | Stage &1 is not compatible with document stop sequence type |
| 608 | Deletion failed; none of the stages were inherited from a default route |
| 609 | Stage &1 must not be deleted due to org. interact. status &2 of stage &3 |
| 610 | Multiple &1 locations exist with IATA code &2 |
| 611 | A &1 location with IATA code &2 does not exist |
| 612 | IATA airport code &1 is not defined in Customizing |
| 613 | Times of stop at &1 are before pick-up time of document |
| 614 | Times of stop at &1 are after delivery time of document |
| 615 | Container &1 is &2 and cannot be changed |
| 616 | Action not possible because of status &1 |
| 617 | Cannot remove assignment because document is fixed |
| 618 | Define IATA aircraft type code &1 in Customizing |
| 619 | &1 must not be later than &2 at location &3 |
| 620 | &1 must not be earlier than &2 at location &3 |
| 621 | &1 at location &2 must not be earlier than &3 at location &4 |
| 622 | Location &1: &2 (arrival) should be earlier than &3 (departure) |
| 623 | At location &1, pick-up time is before delivery time |
| 624 | Loading point or unloading point &1 does not exist in warehouse &2 |
| 625 | *****************Misc******************************* |
| 626 | Quantity conversion from &1 to &2 failed |
| 627 | Status unchanged; document contains items that are not delivery-based |
| 628 | Execution document has references that do not point to delivery document |
| 629 | Arrival date at final destination must not be in the future |
| 630 | Undo resolve discrepancy is not possible for child item (&1) |
| 631 | Save canceled for some documents |
| 632 | Some errors occurred |
| 633 | &1 &2 was sent to carrier |
| 634 | &1 &2 was not sent out due to incompleteness |
| 635 | Cargo receipt status of item &1 cannot be changed; delivery not processed |
| 636 | No valid default route found |
| 637 | Only one valid default route found and applied |
| 638 | Default route &1 not applied because of invalid rate |
| 639 | Document &1 is incomplete; equipment group of item &2 is missing |
| 640 | Document is incomplete; equipment type of item &2 is missing |
| 641 | Document is incomplete; equipment group of item &2 is missing |
| 642 | Local cargo item &1 cannot be assigned to forwarding order &2 |
| 643 | Freight unit item &1 is already assigned to another item |
| 644 | Route of local cargo item &1 does not match route of forwarding order &2 |
| 645 | Item &1 is not a local cargo item |
| 646 | Item category of freight unit item and local item must be the same |
| 647 | Gross weight of forwarding order item &1 must not be zero |
| 648 | Lifecycle status of forwarding order &1 is Draft, Canceled, or Completed |
| 649 | All items of freight unit &1 must be assigned together |
| 650 | ***** OVERVIEW ***** |
| 651 | Changing items and locations at the same time is not permitted |
| 652 | Cannnot insert location; invalid stop index |
| 653 | Location sequence of &1 changed |
| 654 | Cannot move the first location prior the first location |
| 655 | Cannot move the last location beyond the last location |
| 656 | Location sequence of &1 was not changed |
| 657 | Cannot remove &1 (&2) of &3; requirements still assigned to this location |
| 658 | Location &1 (&2) was removed from location sequence of &3 |
| 659 | Cannot assign requirements to elements of category &1 |
| 660 | Cannot assign requirements to referenced elements |
| 661 | You are only allowed to insert transshipment locations into a booking |
| 662 | Cannot assign &1 to &2; locations do not match |
| 663 | Only loading or unloading activity of &1 can be changed |
| 664 | Cannot change assignment of &1: only &2 possible at location &3 |
| 665 | Cannot archive; tendering of FO &1 is incomplete |
| 666 | Split is only supported for unplanned stages |
| 667 | No successor exists for the selected stage &1 |
| 668 | No predecessor exists for selected stage &1 |
| 669 | Cannot merge planned stage &1 |
| 670 | Cannot change location &1; requirements assigned to this location |
| 671 | Cannot change location &1 since it has already been planned |
| 672 | Cannot change location &1; location originates from forwarding order |
| 673 | Cannot change location &1; requirements assigned to predecessor |
| 674 | Cannot change location &1; predecessor already planned |
| 675 | Cannot change location &1; successor already planned |
| 676 | Cannot change location &1; requirements assigned to successor |
| 677 | Split is not permitted for stage &1; only for main carriage |
| 678 | Item from predecessor document cannot be used to create forwarding order |
| 679 | Cannot be deleted; preceding or follow-on stage is planned |
| 680 | Driver description is missing |
| 681 | Carrier dates: End date/time cannot be earlier than start date/time |
| 682 | Appointment dates: End date/time cannot be earlier than start date/time |
| 683 | Driver ID is missing |
| 684 | Default driver &1 of vehicle is already assigned to business document |
| 685 | Duplicate driver assignment on stage from &1 to &2 |
| 686 | Driver &1 is assigned multiple times to stage from &2 to &3 |
| 687 | Driver assignment to stage from &1 to &2 is incomplete |
| 688 | ***** RESOURCE CHECK ***** |
| 689 | Resource &1 has a downtime defined within this time frame |
| 690 | Resource &1 is already used by &2 within this time frame |
| 691 | Resource check failed for resource &1 |
| 692 | Resource &1 is used by &2 and &3 within the same time frame |
| 693 | Resource &1 is used by &2 during a defined downtime |
| 694 | Maximum number of individual resources is exceeded for multiresource &1 |
| 695 | Resource &1 with planning block "&2" is used by &3 |
| 696 | Resource &1 has planning block "&2" |
| 697 | &1 uses resource &2 outside of the resource's validity |
| 698 | Resource &1 is used outside its validity |
| 699 | Resource usage check completed without errors |
| 700 | PPF action &1 unknown within &2 |
| 701 | Too many drivers are assigned to stage from &1 to &2 |
| 702 | No house bill of lading number range maintained for type &1 |
| 703 | BP &1 is relevant for invoicing; additional charge calculation started |
| 704 | You cannot use external number range &1 to create HBL numbers |
| 705 | Both inbound and outbound deliveries are related to FO/FB &1 |
| 706 | FO/FB &1 has a freight unit which is still assigned to an OTR (&2) |
| 707 | The assignment between FO/FB &1 and its freight units is inconsistent |
| 708 | Not every freight unit of DTR &1 is assigned to FO/FB &2 |
| 709 | FO/FB &1 is linked to DTRs of different ERP systems &2 and &3 |
| 710 | FO/FB &1 has not been changed since last update in ERP; no update needed |
| 711 | FO/FB &1 of type &2 is not relevant for ERP |
| 712 | Planning block is set for FO/FB &1 |
| 713 | Execution block is set for FO/FB &1 |
| 714 | Lifecycle status of FO/FB &1 has to be 'In Process' |
| 715 | No logical ERP system found for FO/FB &1 |
| 716 | Too many drivers are assigned |
| 717 | Driver assignment is incomplete |
| 718 | You cannot assign drivers per stage for stop sequence type of document |
| 719 | &1: Duplicate driver assignment |
| 720 | Driver &1 is not available during this time frame |
| 721 | Cannot select direct shipment option; carrier does not match |
| 722 | Cannot select direct shipment option; date or time does not match |
| 723 | DSO conversion failed; type &1 not valid for this process |
| 724 | DSO assignment failed; type &1 not valid for this process |
| 725 | Freight unit &1 is already assigned to fixed manifest &2 |
| 726 | &1 uses driver &2 outside of the driver's availability |
| 727 | Another railcar has already been assigned to position &1 |
| 728 | Resource &1 is already assigned and is not a multi-resource |
| 729 | Transportation unit &1 created in shortcut scenario cannot be copied |
| 730 | Default route successfully assigned to &1 |
| 731 | Driver &1 is already assigned to &2 within this time frame |
| 732 | Stage on resource &1 between &2 and &3 missing |
| 733 | Stage on resource &1 between &2 and downtime at location &3 missing |
| 734 | Stage on resource &1 between downtime at location &2 and &3 missing |
| 735 | Stage between downtime at location &1 and downtime at location &2 missing |
| 736 | Stage for driver &1 between &2 and &3 missing |
| 737 | Stage for driver &1 between &2 and downtime at location &3 missing |
| 738 | Stage for driver &1 between downtime at location &2 and &3 missing |
| 739 | Driver &1 is used by &2 and &3 during the same time frame |
| 740 | ******* Booking Confirmation Related Messages (Detailed Check) ******* |
| 741 | TypeCode and Category must be unique among BookingCapacity instances |
| 742 | Adding BookingCapacity is not supported (CategoryCode &1, TypeCode &2) |
| 743 | Invalid assignment FU &1 booking &2: Shipper &3 not known long enough |
| 744 | Invalid stage type code &1; cannot confirm stage &2 |
| 745 | Stage &1: Specified location &2 does not match specified &3 &4 |
| 746 | Stage &1: No location found matching specified &2 &3 |
| 747 | Stage &1; Code list of agency &2 is not supported for element &3 |
| 748 | Invalid assignment FU &1 to booking &2 due to org. unit restriction |
| 749 | BookingCapacity and Item instances must not occur in the same message |
| 750 | Shipping type &1 does not allow multiple BookingCapacity instances |
| 751 | Validity of driver &1 is not within this time frame |
| 752 | Driver &1 is used by &2 during a defined absence |
| 753 | Assignment not possible; item &1 of &2 not maintained |
| 754 | &1 not directly assigned to &2; unassign directly from predecessor doc. |
| 755 | Unassign all items of &1 |
| 756 | VGM data is not complete or has not been recorded for item &1 |
| 757 | Duplicate stage assignments of driver "&1" were automatically merged |
| 758 | Discrepancy report for item &1 on document &2 |
| 759 | Missing cargo discrepancy reported for item &1 on document &2 |
| 760 | Package ID can only be used once |
| 761 | Cannot use schedule &1; referenced departure location does not exist |
| 762 | Update from schedule performed for &1 |
| 763 | Action not possible; no schedule assigned to &1 |
| 764 | Referenced schedule departure does not exist; assign another departure |
| 765 | Cannot use schedule &1; referenced schedule departure is invalid |
| 766 | Cannot use schedule &1; referenced schedule departure does not exist |
| 767 | Service stop at location &1 cannot be used as destination stop |
| 768 | Location was changed; check if number of connection flight is still valid |
| 769 | Cannot use schedule &1; only schedules without gateways can be used |
| 770 | *******Booking related messages******* |
| 771 | Freight booking sent to carrier |
| 772 | Booking cancellation is sent to carrier after save |
| 773 | Shipping instruction cannot be sent |
| 774 | Booking &1 not found |
| 775 | Booking &1 cannot be confirmed |
| 776 | No need to send again |
| 777 | Item &1 to be confirmed not found |
| 778 | Incorrect category; cannot confirm item &1 |
| 779 | Carrier cannot be changed by confirmation |
| 780 | Ship-to party cannot be changed by confirmation |
| 781 | Shipper cannot be changed by confirmation |
| 782 | Party &1 unknown |
| 783 | Shipping instruction sent to carrier |
| 784 | & outbound messages generated |
| 785 | Booking cannot be sent |
| 786 | Shipment &1 is not fully assigned to booking &2 |
| 787 | Shipping instruction is sent to import house after saving |
| 788 | Cannot map responsibility |
| 789 | Cannot change text of type &1 |
| 790 | Schedule &1 has a transportation mode that cannot be used for booking &2 |
| 791 | Only schedules with gateways can be used for this booking |
| 792 | Cannot use schedule &2; booking &1 does not have pickup/delivery location |
| 793 | Only direct schedules with gateways can be used for freight orders |
| 794 | Cannot use schedule &2; booking &1 has pick-up and/or delivery location |
| 795 | Schedule &2 can only be assigned to one freight document |
| 796 | Indirect schedules with gateways cannot be used for freight orders |
| 797 | FU &1 &2 incompatible with booking &3 &4 |
| 798 | No service order type assigned to freight booking type &1 |
| 799 | Service order type &1 that is assigned to freight booking does not exist |
| 800 | ****** House Bill of Lading Processing |
| 801 | TO item referenced in B/L item &1 no longer exists |
| 802 | Schedule assignment for freight document &1 cannot be changed |
| 803 | Can�t copy normalized quantity; UoM in schedule and FD are not identical |
| 804 | Freight document type &1 not allowed for customer pick-up stage |
| 805 | Freight document type &1 not allowed for customer self-delivery stage |
| 806 | FO for pick-up/delivery cannot be created for FB &1 with shipping type &2 |
| 807 | FO for pick-up cannot be created for FB &1 without pick-up location |
| 808 | FO for delivery cannot be created for FB &1 without delivery location |
| 809 | FO &1 is in tendering; cannot create settlement document |
| 810 | Flight number &1 was changed automatically |
| 811 | Airline code &1 was changed automatically |
| 812 | Local item cannot be inserted; parent item is referenced |
| 813 | Cancellation not allowed; &1 has already arrived at warehouse |
| 814 | Cancellation request sent to warehouse |
| 815 | Cancellation request for &1 has already been sent to warehouse |
| 816 | Service type &1 is not valid for the freight agreement item |
| 817 | Service type &1 does not exist |
| 818 | Service type &1 is not defined for carrier &2 |
| 819 | (Un)loading instruction will be sent when saved |
| 820 | ***** Messages Related to Loading Instructions ****** |
| 821 | Cannot determine message recipient from current stop &1 |
| 822 | Cannot determine recipient for loading or unloading instruction |
| 823 | Veh. resource &1 cannot be loaded directly but cargo items are assigned |
| 824 | MTr, equipment type, vehicle type, or pack. material expected for item &1 |
| 825 | (Un)loading instruction can be sent only manually |
| 826 | Cannot determine &1 date/time for current stop &2; check appointment |
| 827 | &1 not defined for current stop at &2 |
| 828 | &1 missing for item &2 |
| 829 | (Un)loading instruction cannot be sent multiple times |
| 830 | *******Archiving related messages******* |
| 831 | Selection with attribute "&1" is not allowed in archivability query |
| 832 | There are unprocessed triggers for the document |
| 833 | Action cannot be performed for documents with archiving status "&1" |
| 834 | Cannot archive; predecessor FO &1 to be archived first |
| 835 | Local items cannot be created for doc. that are created by FU building |
| 836 | Doc. &1: "Exclusive Package for Customer" set to "Standard Consolidation" |
| 837 | Doc. &1: "Exclusive Package for Customer" set to "Excl. Pkg. for Cust." |
| 838 | Door &1 does not exist at loading point or unloading point &2 |
| 839 | The total quantity of split item &1 is different to that of FU item &2 |
| 840 | Client &1; no relevant data found for migration of assignment categories |
| 841 | Client &1; no relevant data found for migration of dates and times |
| 842 | Client &1; &2 records updated for stop assignment categories |
| 843 | Client &1; &2 records updated for stop dates and times |
| 844 | |
| 845 | Client &1, table &2; RES_ID of &3 TUR items were updated |
| 846 | Client &1, table &2; RES_ID of &3 PVR items were updated |
| 847 | Client &1, table &2; RES_ID of &3 AVR items were updated |
| 848 | Client &1, table &2; RES_KEY and RES_SEQ of &3 items were updated |
| 849 | Cannot cancel business document &1; document has status "Executed" |
| 850 | ****** Direct Shipment Options Strategy Processing |
| 851 | Determination of direct shipment options has been interrupted |
| 852 | Time determination for carrier &1 is not specified |
| 853 | Determination of direct shipment options with strategy "&1" started |
| 854 | Pick-up time for carrier &1 with service level &2 could not be determined |
| 855 | &1 is not a freight unit, conversion is not supported |
| 856 | &1 is already planned, only unplanned FUs can be converted |
| 857 | External scheduling strategy &1 could not be executed |
| 858 | Determination of direct shipment options for &1 freight units finished |
| 859 | Freight agreement for carrier &1 could not be determined |
| 860 | No direct shipment strategy assigned in Customizing for FU type "&1" |
| 861 | Direct shipment options can only be determined for freight units |
| 862 | No CS settings for direct shipment options determined for FU type "&1" |
| 863 | Freight unit type "&1" does not allow direct shipment options |
| 864 | Direct shipment options determined |
| 865 | &1 direct shipment options have been filtered out due to time constraints |
| 866 | Choose an option |
| 867 | Document &1 is not enabled for charge calculation |
| 868 | Document &1 is not enabled for freight settlement |
| 869 | Cannot convert freight unit &1; document type &2 is not FO type |
| 870 | Type &1 is not enabled for internal settlement |
| 871 | No direct shipment options determined or selected |
| 872 | Type &1 not defined for manifest creation or assignment |
| 873 | Freight agreement &1 not found |
| 874 | Item &1 of freight agreement &2 not found |
| 875 | Item &2 of freight agreement not found |
| 876 | FU &1 contains more than 1 stage; intermediate stops cannot be deleted |
| 877 | Cannot cancel document &1; document is already invoiced |
| 878 | Cannot set status &1 on document level |
| 879 | Cannot change carrier; business document has status "Manifest Created" |
| 880 | Service type &1 is not valid for item type &2 |
| 881 | Invalid forwarding order type &1 |
| 882 | Traffic direction is initial |
| 883 | Invalid movement type &1 |
| 884 | Invalid air waybill type &1 |
| 885 | Stage category &1 cannot be used for self-delivery freight orders |
| 886 | Stage category &1 cannot be used for freight bookings |
| 887 | Stage category &1 cannot be used for freight orders |
| 888 | No subsequent stop found for self-delivery |
| 889 | No subsequent stop found for booking |
| 890 | No subsequent stop found for freight order |
| 891 | Source location of item &1 cannot be identified |
| 892 | Final destination location of item &1 cannot be identified |
| 893 | FWO type &1 is "Same Loc. and BP" but item src. loc/shipper not identical |
| 894 | FWO type &1 is "Same Loc and BP" but item des. loc/SP not identical |
| 895 | Business documents fixed |
| 896 | Business documents unfixed |
| 897 | Package ID &1 not found; packaging update is not possible |
| 898 | Enter a master air waybill number with a correct check digit |
| 899 | Cannot change carrier, document is invoiced; cancel existing FSD first |
| 900 | Forwarding order creation only possible for local cargo items |