SAP ABAP Message Class VII (Application Output Shipment Output Inbox)
Basic Data
Hierarchy
☛
SAP_APPL (Software Component) Logistics and Accounting
⤷
LE-TRA (Application Component) Transportation
⤷
VTRK (Package) Shipping communication (delivery/transport)
SAP_APPL (Software Component) Logistics and Accounting⤷
LE-TRA (Application Component) Transportation⤷
VTRK (Package) Shipping communication (delivery/transport) 
Attributes
| Message class |  |
VII |
| Short Description |  |
Application Output Shipment Output Inbox |
| Changed On |  |
20130531 |
| Last Changed At |  |
100859 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 |  000 |
Output type & cannot be processed using this function | Space: object requires documentation | |
| 2 | 001 |
No data records (IDoc &) exist for the current control record | Space: object requires documentation | |
| 3 | 002 |
Serialization error in IDoc & for shipment & | Space: object requires documentation | |
| 4 | 003 |
ISO conversion error for & in segment & (&), field & | Space: object requires documentation | |
| 5 | 004 |
Shipment document & & created successfully | Space: object requires documentation | |
| 6 | 005 |
Shipment document & & changed successfully | Space: object requires documentation | |
| 7 | 006 |
IDoc processed successfully | Space: object requires documentation | |
| 8 | 007 |
IDoc could not be processed without errors | Space: object requires documentation | |
| 9 | 008 |
Error status for IDoc & created in & | Space: object requires documentation | |
| 10 | 009 |
Processing interrupted upon request of a customer enhancement | Space: object requires documentation | |
| 11 | 010 |
Processing terminated because not required or possible | Space: object requires documentation | |
| 12 | 011 |
Error recorded in & for segment & (No. &) | Space: object requires documentation | |
| 13 | 012 |
Processing termination by & forced after segment & (No. &) | Space: object requires documentation | |
| 14 | 013 |
Error recorded in & for IDoc & | Space: object requires documentation | |
| 15 | 014 |
No shipment document number assigned for IDoc & | Space: object requires documentation | |
| 16 | 015 |
Delivery number not defined in segment & (No. &) | Space: object requires documentation | |
| 17 | 016 |
No current stage defined for segment & (No. &) | Space: object requires documentation | |
| 18 | 017 |
No current point defined for segment & (No. &) | Space: object requires documentation | |
| 19 | 018 |
No current shipping unit defined for segment & (number &) | Space: object requires documentation | |
| 20 | 019 |
Delivery number could not be assigned correctly in segment & (no. &) | Space: object requires documentation | |
| 21 | 020 |
Specified delivery & does not exist (segment & no. &) | Space: object requires documentation | |
| 22 | 021 |
Tender status & unknown (segment &) | Space: object requires documentation | |
| 23 | 022 |
Shipment & tendered to & and not & | Space: object requires documentation | |
| 24 | 023 |
Shipment & has not been tendered | Space: object requires documentation | |
| 25 | 024 |
Tendering offer has expired | Space: object requires documentation | |
| 26 | 025 |
Maximum price has been exceeded | Space: object requires documentation | |
| 27 | 026 |
Shipment document cannot be created using output type & | Space: object requires documentation | |
| 28 | 027 |
Actual carrier is missing | Space: object requires documentation | |
| 29 | 028 |
Actual price is missing | Space: object requires documentation | |
| 30 | 029 |
Delivery & distributed to EWM has not yet been posted for goods issue | The short text describes the object sufficiently | |
| 31 | 030 |
Delivery & not found or not yet created | The short text describes the object sufficiently | |
| 32 | 100 |
Delivery & cannot be assigned to any internal notification | The short text describes the object sufficiently | |
| 33 | 101 |
Delivery &: Item & is not uniquely assigned to an internal item | The short text describes the object sufficiently | |
| 34 | 102 |
Posting reset due to error in another IDoc in mass processing | The short text describes the object sufficiently | |
| 35 | 103 |
Changes to shipping notifications are not possible at present | The short text describes the object sufficiently | |
| 36 | 104 |
Unknown qualifier in segment & | The short text describes the object sufficiently | |
| 37 | 105 |
Delivery &: Assignment to regular shipment is not unique | The short text describes the object sufficiently | |
| 38 | 106 |
Delivery &1: Corresponding regular shipment &2 not found | The short text describes the object sufficiently | |
| 39 | 107 |
Int. shipping notification &1: Time deviation shipment -> delivery | The short text describes the object sufficiently | |
| 40 | 108 |
Creation of shipping notifications in shipment is not possible at present | The short text describes the object sufficiently | |
| 41 | 109 |
Delivery &: Shipment type does not correspond to the delivery type | The short text describes the object sufficiently | |
| 42 | 110 |
Partner identification is not filled in segment & (no. &) | The short text describes the object sufficiently | |
| 43 | 111 |
Delivery &: No route schedule found | The short text describes the object sufficiently | |
| 44 | 112 |
Delivery &: Route schedule could not be uniquely identified | The short text describes the object sufficiently | |
| 45 | 113 |
Int. notification &: Route schedule in notification and shipment differ | The short text describes the object sufficiently | |
| 46 | 114 |
Shipping notifications & - & created with warnings | The short text describes the object sufficiently | |
| 47 | 115 |
Shippping notifications & - & created, & included in shipment | The short text describes the object sufficiently | |
| 48 | 116 |
Shpg notifications &-& created with warnings, & included in shipment | The short text describes the object sufficiently | |
| 49 | 117 |
IDoc &: No external identification in field & | The short text describes the object sufficiently | |
| 50 | 118 |
IDOC &: Entry in field & is not unique (see shipment &) | The short text describes the object sufficiently | |
| 51 | 119 |
IDoc &, Segment &:Dely qty is not equal to the total from summ. JIT calls | The short text describes the object sufficiently | |
| 52 | 120 |
Segment &: Inconsistency in assignment of summarized JIT calls | The short text describes the object sufficiently |
History
| Last changed on/by | |
20130531 | SAP |
| SAP Release Created in |
