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

⤷

⤷

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 | ![]() |
Error from posting module - Rollback executed | Space: object requires documentation | |
2 | ![]() |
Required segment & missing in IDoc | Space: object requires documentation | |
3 | ![]() |
Unknown segment & found in IDoc | ||
4 | ![]() |
Segment & can only occur once per parent segment | ||
5 | ![]() |
No or invalid content in field & | Space: object requires documentation | |
6 | ![]() |
Error checking fixed value & | Space: object requires documentation | |
7 | ![]() |
Date/Time and time stamp for prefix & cannot both be empty | ||
8 | ![]() |
Date/Time and time stamp for prefix & are both entered | ||
9 | ![]() |
Date or time for prefix & is not entered | ||
10 | ![]() |
Location only partly entered (Code: &1, ID1: &2, ID2: &3) | ||
11 | ![]() |
Delay, date/time, or time stamp must be entered for prefix & | ||
12 | ![]() |
Only one time entry (delay, date/time, time stamp) possible for prefix & | ||
13 | ![]() |
Date or time is not entered (Prefix: &) | ||
14 | ![]() |
Error converting external timezone & | ||
15 | ![]() |
The timezone must be entered in this segment | ||
16 | ![]() |
Location does not exist either in this nor in the location segment | ||
17 | ![]() |
No route found for shipping notification (external number: &) | ||
18 | ![]() |
Several routes found for shipping notification (external number: &) | ||
19 | ![]() |
No internal shipping notification exists for external number & | ||
20 | ![]() |
Shipping notification & not found | ||
21 | ![]() |
No route found for shipping notification & | ||
22 | ![]() |
Shipping notificiation & is fixed, no schedule update possible | Space: object requires documentation | |
23 | ![]() |
Shipping notification &, route &: This route in invalid | ||
24 | ![]() |
Shipping notification &: The location is not on route & | Space: object requires documentation | |
25 | ![]() |
Shipping notification &, route &: Scheduling error | ||
26 | ![]() |
Shpg notification &: Conversion of event time in timestamp not possible | Space: object requires documentation | |
27 | ![]() |
Shipping notification &: Node for event not transmitted | Space: object requires documentation | |
28 | ![]() |
Date in shipping notification fixed using tracking | Space: object requires documentation | |
29 | ![]() |
Shipping notification &: update of delivery date is not allowed | Space: object requires documentation | |
30 | ![]() |
Shpg notif. &1, route &2: Connection point is not defined in the route | Space: object requires documentation | |
31 | ![]() |
Shipping notification &: "Binding arrival" only allowed at last point | Space: object requires documentation | |
32 | ![]() |
Shipping notification: Time estimate with highest priority is erroneous | Space: object requires documentation | |
33 | ![]() |
Shipping notificaiton &: No update due to faulty time estimation | Space: object requires documentation | |
34 | ![]() |
Shipping notification: Delivery date was not updated | Space: object requires documentation | |
35 | ![]() |
Processing of the IDoc is not possible due to incorrect data | Space: object requires documentation | |
36 | ![]() |
GR already posted for shipping notification &1; no tracking possible | Space: object requires documentation | |
37 | ![]() |
IDoc partially processed | Space: object requires documentation | |
38 | ![]() |
IDoc processed | Space: object requires documentation | |
39 | ![]() |
Shipping notification &; error in binding time estimation | Space: object requires documentation | |
40 | ![]() |
Shpg notification &1: GR already posted for corres. int. notification &2 | Space: object requires documentation | |
41 | ![]() |
Shipping notification is not transferred for further processing | Space: object requires documentation | |
42 | ![]() |
Segment &1 can only occur once with the combination of &2 and &3 | ||
43 | ![]() |
Qualifier &1 in field &2 cannot be processed in this release | ||
44 | ![]() |
Qualifier &1 in field &2 is ignored in this release | ||
45 | ![]() |
The tracking data entered is incomplete | Space: object requires documentation | |
46 | ![]() |
The node entered (&1) does not exist on route &2 | Space: object requires documentation | |
47 | ![]() |
Only departure is allowed for the first connection point of a route | Space: object requires documentation | |
48 | ![]() |
Only "arrival" or "binding arrival" allowed at the last point of a route | Space: object requires documentation | |
49 | ![]() |
No older tracking data exists, cancellation not possible | Space: object requires documentation | |
50 | ![]() |
No delivery date exists in this entry; transfer not possible | Space: object requires documentation | |
51 | ![]() |
No point in current entry | Space: object requires documentation | |
52 | ![]() |
No IDoc data exist for a manual entry | Space: object requires documentation | |
53 | ![]() |
This entry was not made manually or by using the Internet | Space: object requires documentation | |
54 | ![]() |
No route entered in shipping notification | Space: object requires documentation | |
55 | ![]() |
Error in IDoc display | Space: object requires documentation | |
56 | ![]() |
Select a tracking entry | Space: object requires documentation | |
57 | ![]() |
No route entered so no tracking entry possible | Space: object requires documentation | |
58 | ![]() |
Delivery date was not transfered from the new tracking data | Space: object requires documentation | |
59 | ![]() |
Time zone for the point could not be determined | Space: object requires documentation | |
60 | ![]() |
Error reading route data | Space: object requires documentation | |
61 | ![]() |
Delivery date is not reset | Space: object requires documentation | |
62 | ![]() |
Point does not refer to a time zone; tracking not possible for this point | Space: object requires documentation | |
63 | ![]() |
System time zone not set - tracking input not possible | Space: object requires documentation | |
64 | ![]() |
Error reading route data - tracking input not possible | Space: object requires documentation | |
65 | ![]() |
Error displaying list of values | Space: object requires documentation | |
66 | ![]() |
Error displaying field help | Space: object requires documentation | |
67 | ![]() |
Point no longer in the route - function not possible | Space: object requires documentation | |
68 | ![]() |
Delivery date no longer matches the tracking data | Space: object requires documentation | |
69 | ![]() |
"Arrival binding" only allowed at the last point of a route | Space: object requires documentation | |
70 | ![]() |
Delivery date compatible with &1 at point &2 and time &3, &4 o'clock | Space: object requires documentation | |
71 | ![]() |
Delivery date does not tally with the tracking data | Space: object requires documentation | |
72 | ![]() |
New delivery date cannot be determined as tracking entry is inconsistent | Space: object requires documentation | |
73 | ![]() |
Error saving; new delivery date cannot be determined | Space: object requires documentation | |
74 | ![]() |
Manually created IDOC for inbound tracking history | Space: object requires documentation | |
75 | ![]() |
Shipment &1 cannot be rescheduled | Space: object requires documentation |
History
Last changed on/by | ![]() |
20050301 | SAP |
SAP Release Created in |