BOR01 - Message class for ETA calculation and Route simulation
The following messages are stored in message class BOR01: Message class for ETA calculation and Route simulation.
It is part of development package ISAUTO_BOR in software component IS-A-GR. This development package consists of objects that can be grouped under "Cargo manifest".
It is part of development package ISAUTO_BOR in software component IS-A-GR. This development package consists of objects that can be grouped under "Cargo manifest".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Route '&' is invalid |
| 001 | The combination of route '&1' and '&2' as start point is not possible |
| 002 | The combination of route '&1' and '&2' as end point is not possible |
| 003 | Connection point '&' is invalid |
| 004 | Date '&1' and time stamp '&2' are invalid |
| 005 | Connection points for route & are invalid; edit them |
| 006 | Incomplete data for the determination of timezone for conn. point '&' |
| 007 | Customer '&1' is invalid for connecting point '&2' |
| 008 | Vendor '&1' is invalid for connecting point '&2' |
| 009 | Shipping point '&1' is invalid for connecting point '&2' |
| 010 | Plant '&1' is invalid for connecting point '&2' |
| 011 | Connecting point '&' contains several address references |
| 012 | The information to display address references is insufficient |
| 013 | First select a connection point |
| 100 | Shipment &1 does not contain inbound deliveries |
| 101 | No confimration control key maintained in purchasing document &1 &2 |
| 102 | Transportation planning point &1 does not exist |
| 103 | Shipment & was planned in APO |
| 200 | The tracking data you entered is incomplete |
| 201 | According to check routine tracking is not allowed |
| 202 | Error reading route data - tracking input not possible |
| 203 | The connection point & you entered is not trackable |
| 204 | Point does not refer to a time zone; tracking not possible for this point |
| 205 | Only departure is allowed for the first connection point of a route |
| 206 | Only "arrival" or "binding arrival" allowed at the last point of a route |
| 207 | Shipment & is not trackable |
| 208 | Not all of the inbound deliveries are trackable |
| 209 | Number range interval with number &1 does not exist |
| 210 | Number range object &1 does not exist |
| 211 | Error in function module 'NUMBER_GET_INFO' |
| 212 | Inbound delivery &1: Delivery date and time have been changed |
| 213 | Shipment &1 does not contain inbound deliveries |
| 214 | Shipment &1 was not planned by an external system |
| 215 | Shipment &1 was planned in APO (no scheduling) |
| 216 | Not all of the inbound deliveries are trackable |
| 217 | There is no confirmation control key in at least one inbound delivery |
| 218 | No tracking data have been entered; saving not necessary |
| 219 | Non-numeric number range |
| 220 | No delivery exists for shipment &1 |
| 221 | Error in Customizing for the routes |
| 222 | Tracking IDoc could not be created |
| 223 | Not all inbound deliveries contain a route |
| 224 | IDoc &1 cannot be displayed |
| 225 | Enter one number only (shipment or delivery number) |
| 226 | Error occurred when reading screen fields |
| 227 | Inbound deliveries of shipment already put away or GR has been posted |
| 228 | Scheduling impossible: error in module 'BORRS_ROUTE_SCHEDULING' |
| 229 | No data found for the shipment |
| 230 | Rescheduling is not possible |
| 231 | No freight forwarder maintained; tracking impossible |
| 232 | No rescheduling (arrival is binding); IDOC is saved |