VTX - Nachrichten aus der Tracking-Meldungsverarbeitung
The following messages are stored in message class VTX: Nachrichten aus der Tracking-Meldungsverarbeitung.
It is part of development package VTRX in software component LE-TRA. This development package consists of objects that can be grouped under "Tracking".
It is part of development package VTRX in software component LE-TRA. This development package consists of objects that can be grouped under "Tracking".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Error from posting module - Rollback executed |
| 001 | Required segment & missing in IDoc |
| 002 | Unknown segment & found in IDoc |
| 003 | Segment & can only occur once per parent segment |
| 010 | No or invalid content in field & |
| 011 | Error checking fixed value & |
| 012 | Date/Time and time stamp for prefix & cannot both be empty |
| 013 | Date/Time and time stamp for prefix & are both entered |
| 014 | Date or time for prefix & is not entered |
| 015 | Location only partly entered (Code: &1, ID1: &2, ID2: &3) |
| 016 | Delay, date/time, or time stamp must be entered for prefix & |
| 017 | Only one time entry (delay, date/time, time stamp) possible for prefix & |
| 018 | Date or time is not entered (Prefix: &) |
| 030 | Error converting external timezone & |
| 031 | The timezone must be entered in this segment |
| 032 | Location does not exist either in this nor in the location segment |
| 500 | No route found for shipping notification (external number: &) |
| 501 | Several routes found for shipping notification (external number: &) |
| 502 | No internal shipping notification exists for external number & |
| 503 | Shipping notification & not found |
| 504 | No route found for shipping notification & |
| 505 | Shipping notificiation & is fixed, no schedule update possible |
| 506 | Shipping notification &, route &: This route in invalid |
| 507 | Shipping notification &: The location is not on route & |
| 508 | Shipping notification &, route &: Scheduling error |
| 509 | Shpg notification &: Conversion of event time in timestamp not possible |
| 510 | Shipping notification &: Node for event not transmitted |
| 511 | Date in shipping notification fixed using tracking |
| 512 | Shipping notification &: update of delivery date is not allowed |
| 513 | Shpg notif. &1, route &2: Connection point is not defined in the route |
| 514 | Shipping notification &: "Binding arrival" only allowed at last point |
| 515 | Shipping notification: Time estimate with highest priority is erroneous |
| 516 | Shipping notificaiton &: No update due to faulty time estimation |
| 517 | Shipping notification: Delivery date was not updated |
| 518 | Processing of the IDoc is not possible due to incorrect data |
| 519 | GR already posted for shipping notification &1; no tracking possible |
| 520 | IDoc partially processed |
| 521 | IDoc processed |
| 522 | Shipping notification &; error in binding time estimation |
| 523 | Shpg notification &1: GR already posted for corres. int. notification &2 |
| 524 | Shipping notification is not transferred for further processing |
| 800 | Segment &1 can only occur once with the combination of &2 and &3 |
| 801 | Qualifier &1 in field &2 cannot be processed in this release |
| 802 | Qualifier &1 in field &2 is ignored in this release |
| 810 | The tracking data entered is incomplete |
| 811 | The node entered (&1) does not exist on route &2 |
| 812 | Only departure is allowed for the first connection point of a route |
| 813 | Only "arrival" or "binding arrival" allowed at the last point of a route |
| 814 | No older tracking data exists, cancellation not possible |
| 815 | No delivery date exists in this entry; transfer not possible |
| 816 | No point in current entry |
| 817 | No IDoc data exist for a manual entry |
| 818 | This entry was not made manually or by using the Internet |
| 819 | No route entered in shipping notification |
| 820 | Error in IDoc display |
| 821 | Select a tracking entry |
| 822 | No route entered so no tracking entry possible |
| 823 | Delivery date was not transfered from the new tracking data |
| 824 | Time zone for the point could not be determined |
| 825 | Error reading route data |
| 826 | Delivery date is not reset |
| 827 | Point does not refer to a time zone; tracking not possible for this point |
| 828 | System time zone not set - tracking input not possible |
| 829 | Error reading route data - tracking input not possible |
| 830 | Error displaying list of values |
| 831 | Error displaying field help |
| 832 | Point no longer in the route - function not possible |
| 833 | Delivery date no longer matches the tracking data |
| 834 | "Arrival binding" only allowed at the last point of a route |
| 835 | Delivery date compatible with &1 at point &2 and time &3, &4 o'clock |
| 836 | Delivery date does not tally with the tracking data |
| 837 | New delivery date cannot be determined as tracking entry is inconsistent |
| 838 | Error saving; new delivery date cannot be determined |
| 839 | Manually created IDOC for inbound tracking history |
| 840 | Shipment &1 cannot be rescheduled |