VII - Application Output Shipment Output Inbox
The following messages are stored in message class VII: Application Output Shipment Output Inbox.
It is part of development package VTRK in software component LE-TRA. This development package consists of objects that can be grouped under "Shipping communication (delivery/transport)".
It is part of development package VTRK in software component LE-TRA. This development package consists of objects that can be grouped under "Shipping communication (delivery/transport)".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Output type & cannot be processed using this function |
| 001 | No data records (IDoc &) exist for the current control record |
| 002 | Serialization error in IDoc & for shipment & |
| 003 | ISO conversion error for & in segment & (&), field & |
| 004 | Shipment document & & created successfully |
| 005 | Shipment document & & changed successfully |
| 006 | IDoc processed successfully |
| 007 | IDoc could not be processed without errors |
| 008 | Error status for IDoc & created in & |
| 009 | Processing interrupted upon request of a customer enhancement |
| 010 | Processing terminated because not required or possible |
| 011 | Error recorded in & for segment & (No. &) |
| 012 | Processing termination by & forced after segment & (No. &) |
| 013 | Error recorded in & for IDoc & |
| 014 | No shipment document number assigned for IDoc & |
| 015 | Delivery number not defined in segment & (No. &) |
| 016 | No current stage defined for segment & (No. &) |
| 017 | No current point defined for segment & (No. &) |
| 018 | No current shipping unit defined for segment & (number &) |
| 019 | Delivery number could not be assigned correctly in segment & (no. &) |
| 020 | Specified delivery & does not exist (segment & no. &) |
| 021 | Tender status & unknown (segment &) |
| 022 | Shipment & tendered to & and not & |
| 023 | Shipment & has not been tendered |
| 024 | Tendering offer has expired |
| 025 | Maximum price has been exceeded |
| 026 | Shipment document cannot be created using output type & |
| 027 | Actual carrier is missing |
| 028 | Actual price is missing |
| 029 | Delivery & distributed to EWM has not yet been posted for goods issue |
| 030 | Delivery & not found or not yet created |
| 100 | Delivery & cannot be assigned to any internal notification |
| 101 | Delivery &: Item & is not uniquely assigned to an internal item |
| 102 | Posting reset due to error in another IDoc in mass processing |
| 103 | Changes to shipping notifications are not possible at present |
| 104 | Unknown qualifier in segment & |
| 105 | Delivery &: Assignment to regular shipment is not unique |
| 106 | Delivery &1: Corresponding regular shipment &2 not found |
| 107 | Int. shipping notification &1: Time deviation shipment -> delivery |
| 108 | Creation of shipping notifications in shipment is not possible at present |
| 109 | Delivery &: Shipment type does not correspond to the delivery type |
| 110 | Partner identification is not filled in segment & (no. &) |
| 111 | Delivery &: No route schedule found |
| 112 | Delivery &: Route schedule could not be uniquely identified |
| 113 | Int. notification &: Route schedule in notification and shipment differ |
| 114 | Shipping notifications & - & created with warnings |
| 115 | Shippping notifications & - & created, & included in shipment |
| 116 | Shpg notifications &-& created with warnings, & included in shipment |
| 117 | IDoc &: No external identification in field & |
| 118 | IDOC &: Entry in field & is not unique (see shipment &) |
| 119 | IDoc &, Segment &:Dely qty is not equal to the total from summ. JIT calls |
| 120 | Segment &: Inconsistency in assignment of summarized JIT calls |