SAP ABAP Message Class BOR01 (Message class for ETA calculation and route simulation)
Basic Data
Hierarchy
☛
ECC-DIMP (Software Component) DIMP
⤷ IS-A-GR (Application Component) Goods Receipt Process
⤷ ISAUTO_BOR (Package) Cargo manifest
⤷ IS-A-GR (Application Component) Goods Receipt Process
⤷ ISAUTO_BOR (Package) Cargo manifest
Attributes
Message class | BOR01 | |
Short Description | Message class for ETA calculation and route simulation | |
Changed On | 20050301 | |
Last Changed At | 120808 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 000 | Route '&' is invalid | Space: object requires documentation | |
2 | 001 | The combination of route '&1' and '&2' as start point is not possible | Space: object requires documentation | |
3 | 002 | The combination of route '&1' and '&2' as end point is not possible | Space: object requires documentation | |
4 | 003 | Connection point '&' is invalid | Space: object requires documentation | |
5 | 004 | Date '&1' and time stamp '&2' are invalid | Space: object requires documentation | |
6 | 005 | Connection points for route & are invalid; edit them | Space: object requires documentation | |
7 | 006 | Incomplete data for the determination of timezone for conn. point '&' | Space: object requires documentation | |
8 | 007 | Customer '&1' is invalid for connecting point '&2' | Space: object requires documentation | |
9 | 008 | Vendor '&1' is invalid for connecting point '&2' | Space: object requires documentation | |
10 | 009 | Shipping point '&1' is invalid for connecting point '&2' | Space: object requires documentation | |
11 | 010 | Plant '&1' is invalid for connecting point '&2' | Space: object requires documentation | |
12 | 011 | Connecting point '&' contains several address references | Space: object requires documentation | |
13 | 012 | The information to display address references is insufficient | Space: object requires documentation | |
14 | 013 | First select a connection point | Space: object requires documentation | |
15 | 100 | Shipment &1 does not contain inbound deliveries | Space: object requires documentation | |
16 | 101 | No confimration control key maintained in purchasing document &1 &2 | Space: object requires documentation | |
17 | 102 | Transportation planning point &1 does not exist | Space: object requires documentation | |
18 | 103 | Shipment & was planned in APO | Space: object requires documentation | |
19 | 200 | The tracking data you entered is incomplete | Space: object requires documentation | |
20 | 201 | According to check routine tracking is not allowed | Space: object requires documentation | |
21 | 202 | Error reading route data - tracking input not possible | Space: object requires documentation | |
22 | 203 | The connection point & you entered is not trackable | Space: object requires documentation | |
23 | 204 | Point does not refer to a time zone; tracking not possible for this point | Space: object requires documentation | |
24 | 205 | Only departure is allowed for the first connection point of a route | Space: object requires documentation | |
25 | 206 | Only "arrival" or "binding arrival" allowed at the last point of a route | Space: object requires documentation | |
26 | 207 | Shipment & is not trackable | Space: object requires documentation | |
27 | 208 | Not all of the inbound deliveries are trackable | Space: object requires documentation | |
28 | 209 | Number range interval with number &1 does not exist | Space: object requires documentation | |
29 | 210 | Number range object &1 does not exist | Space: object requires documentation | |
30 | 211 | Error in function module 'NUMBER_GET_INFO' | Space: object requires documentation | |
31 | 212 | Inbound delivery &1: Delivery date and time have been changed | Space: object requires documentation | |
32 | 213 | Shipment &1 does not contain inbound deliveries | Space: object requires documentation | |
33 | 214 | Shipment &1 was not planned by an external system | Space: object requires documentation | |
34 | 215 | Shipment &1 was planned in APO (no scheduling) | Space: object requires documentation | |
35 | 216 | Not all of the inbound deliveries are trackable | Space: object requires documentation | |
36 | 217 | There is no confirmation control key in at least one inbound delivery | Space: object requires documentation | |
37 | 218 | No tracking data have been entered; saving not necessary | Space: object requires documentation | |
38 | 219 | Non-numeric number range | Space: object requires documentation | |
39 | 220 | No delivery exists for shipment &1 | Space: object requires documentation | |
40 | 221 | Error in Customizing for the routes | Space: object requires documentation | |
41 | 222 | Tracking IDoc could not be created | Space: object requires documentation | |
42 | 223 | Not all inbound deliveries contain a route | Space: object requires documentation | |
43 | 224 | IDoc &1 cannot be displayed | Space: object requires documentation | |
44 | 225 | Enter one number only (shipment or delivery number) | Space: object requires documentation | |
45 | 226 | Error occurred when reading screen fields | Space: object requires documentation | |
46 | 227 | Inbound deliveries of shipment already put away or GR has been posted | Space: object requires documentation | |
47 | 228 | Scheduling impossible: error in module 'BORRS_ROUTE_SCHEDULING' | Space: object requires documentation | |
48 | 229 | No data found for the shipment | Space: object requires documentation | |
49 | 230 | Rescheduling is not possible | Space: object requires documentation | |
50 | 231 | No freight forwarder maintained; tracking impossible | Space: object requires documentation | |
51 | 232 | No rescheduling (arrival is binding); IDOC is saved | Space: object requires documentation |
History
Last changed on/by | 20050301 | SAP | |
SAP Release Created in |