SAP ABAP Message Class VTX (Messages from tracking notification processing)
Basic Data
Hierarchy
☛
ECC-DIMP (Software Component) DIMP
⤷ LE-TRA (Application Component) Transportation
⤷ VTRX (Package) Tracking
⤷ LE-TRA (Application Component) Transportation
⤷ VTRX (Package) Tracking
Attributes
Message class | VTX | |
Short Description | Messages from tracking notification processing | |
Changed On | 20050301 | |
Last Changed At | 120825 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 000 | Error from posting module - Rollback executed | Space: object requires documentation | |
2 | 001 | Required segment & missing in IDoc | Space: object requires documentation | |
3 | 002 | Unknown segment & found in IDoc | ||
4 | 003 | Segment & can only occur once per parent segment | ||
5 | 010 | No or invalid content in field & | Space: object requires documentation | |
6 | 011 | Error checking fixed value & | Space: object requires documentation | |
7 | 012 | Date/Time and time stamp for prefix & cannot both be empty | ||
8 | 013 | Date/Time and time stamp for prefix & are both entered | ||
9 | 014 | Date or time for prefix & is not entered | ||
10 | 015 | Location only partly entered (Code: &1, ID1: &2, ID2: &3) | ||
11 | 016 | Delay, date/time, or time stamp must be entered for prefix & | ||
12 | 017 | Only one time entry (delay, date/time, time stamp) possible for prefix & | ||
13 | 018 | Date or time is not entered (Prefix: &) | ||
14 | 030 | Error converting external timezone & | ||
15 | 031 | The timezone must be entered in this segment | ||
16 | 032 | Location does not exist either in this nor in the location segment | ||
17 | 500 | No route found for shipping notification (external number: &) | ||
18 | 501 | Several routes found for shipping notification (external number: &) | ||
19 | 502 | No internal shipping notification exists for external number & | ||
20 | 503 | Shipping notification & not found | ||
21 | 504 | No route found for shipping notification & | ||
22 | 505 | Shipping notificiation & is fixed, no schedule update possible | Space: object requires documentation | |
23 | 506 | Shipping notification &, route &: This route in invalid | ||
24 | 507 | Shipping notification &: The location is not on route & | Space: object requires documentation | |
25 | 508 | Shipping notification &, route &: Scheduling error | ||
26 | 509 | Shpg notification &: Conversion of event time in timestamp not possible | Space: object requires documentation | |
27 | 510 | Shipping notification &: Node for event not transmitted | Space: object requires documentation | |
28 | 511 | Date in shipping notification fixed using tracking | Space: object requires documentation | |
29 | 512 | Shipping notification &: update of delivery date is not allowed | Space: object requires documentation | |
30 | 513 | Shpg notif. &1, route &2: Connection point is not defined in the route | Space: object requires documentation | |
31 | 514 | Shipping notification &: "Binding arrival" only allowed at last point | Space: object requires documentation | |
32 | 515 | Shipping notification: Time estimate with highest priority is erroneous | Space: object requires documentation | |
33 | 516 | Shipping notificaiton &: No update due to faulty time estimation | Space: object requires documentation | |
34 | 517 | Shipping notification: Delivery date was not updated | Space: object requires documentation | |
35 | 518 | Processing of the IDoc is not possible due to incorrect data | Space: object requires documentation | |
36 | 519 | GR already posted for shipping notification &1; no tracking possible | Space: object requires documentation | |
37 | 520 | IDoc partially processed | Space: object requires documentation | |
38 | 521 | IDoc processed | Space: object requires documentation | |
39 | 522 | Shipping notification &; error in binding time estimation | Space: object requires documentation | |
40 | 523 | Shpg notification &1: GR already posted for corres. int. notification &2 | Space: object requires documentation | |
41 | 524 | Shipping notification is not transferred for further processing | Space: object requires documentation | |
42 | 800 | Segment &1 can only occur once with the combination of &2 and &3 | ||
43 | 801 | Qualifier &1 in field &2 cannot be processed in this release | ||
44 | 802 | Qualifier &1 in field &2 is ignored in this release | ||
45 | 810 | The tracking data entered is incomplete | Space: object requires documentation | |
46 | 811 | The node entered (&1) does not exist on route &2 | Space: object requires documentation | |
47 | 812 | Only departure is allowed for the first connection point of a route | Space: object requires documentation | |
48 | 813 | Only "arrival" or "binding arrival" allowed at the last point of a route | Space: object requires documentation | |
49 | 814 | No older tracking data exists, cancellation not possible | Space: object requires documentation | |
50 | 815 | No delivery date exists in this entry; transfer not possible | Space: object requires documentation | |
51 | 816 | No point in current entry | Space: object requires documentation | |
52 | 817 | No IDoc data exist for a manual entry | Space: object requires documentation | |
53 | 818 | This entry was not made manually or by using the Internet | Space: object requires documentation | |
54 | 819 | No route entered in shipping notification | Space: object requires documentation | |
55 | 820 | Error in IDoc display | Space: object requires documentation | |
56 | 821 | Select a tracking entry | Space: object requires documentation | |
57 | 822 | No route entered so no tracking entry possible | Space: object requires documentation | |
58 | 823 | Delivery date was not transfered from the new tracking data | Space: object requires documentation | |
59 | 824 | Time zone for the point could not be determined | Space: object requires documentation | |
60 | 825 | Error reading route data | Space: object requires documentation | |
61 | 826 | Delivery date is not reset | Space: object requires documentation | |
62 | 827 | Point does not refer to a time zone; tracking not possible for this point | Space: object requires documentation | |
63 | 828 | System time zone not set - tracking input not possible | Space: object requires documentation | |
64 | 829 | Error reading route data - tracking input not possible | Space: object requires documentation | |
65 | 830 | Error displaying list of values | Space: object requires documentation | |
66 | 831 | Error displaying field help | Space: object requires documentation | |
67 | 832 | Point no longer in the route - function not possible | Space: object requires documentation | |
68 | 833 | Delivery date no longer matches the tracking data | Space: object requires documentation | |
69 | 834 | "Arrival binding" only allowed at the last point of a route | Space: object requires documentation | |
70 | 835 | Delivery date compatible with &1 at point &2 and time &3, &4 o'clock | Space: object requires documentation | |
71 | 836 | Delivery date does not tally with the tracking data | Space: object requires documentation | |
72 | 837 | New delivery date cannot be determined as tracking entry is inconsistent | Space: object requires documentation | |
73 | 838 | Error saving; new delivery date cannot be determined | Space: object requires documentation | |
74 | 839 | Manually created IDOC for inbound tracking history | Space: object requires documentation | |
75 | 840 | Shipment &1 cannot be rescheduled | Space: object requires documentation |
History
Last changed on/by | 20050301 | SAP | |
SAP Release Created in |